πŸ”‘Account Management

Creating an Account

To create a new account, please contact Euno customer support, by emailing; support@getdelphi.io.

Add New Account Members

To add a new team member to your account, click on the user icons located in the top right corner of the screen. This action will prompt a dialogue box where new users can be added, and existing users can be managed.

Once a user's email has been added, the user will receive an email invitation, asking them to join Euno.

Users can log in via OAuth using either GitHub or Gmail, utilizing the email address associated with their account. Alternatively, users can log in via a magic link by clicking "Send me a magic link", which prompts them to enter their email. Upon submission, a link will be sent via email. These links expire 30 minutes after creation, requiring the generation of a new link in such cases.

User Permissions & Roles

Every account must have at least one user with administrative (β€œAccount Admin”) privileges. The initial user added to the account will be added by Euno staff and will be automatically assigned the role of "Account Admin." Unlike other user roles, which have permissions managed at the project and folder level, the role of administrator permissions is managed at the account level with access to all Euno functionality.

User Permissions

Permission

Description

manage_intergrations

Users with this permission level have the authority to handle integrations within the system. This includes setting up, configuring, and managing integrations with external tools and services to enhance the platform's functionality.

create_folder

Users with the "create_folder" permission can generate new folders within the system. This permission is essential for organizing and structuring content in a way that aligns with the organization’s workflow and preferences.

view_folder

This permission level allows users to view the contents of folders within the system without the ability to make modifications. It is useful for users who need access to organized information but do not need to make changes.

manage_members

Users with "manage_members" permission can control and administer members' access within the system. This includes, removing, and adjusting the roles and permissions of other users.

delete_folder

The "delete_folder" permission grants users the authority to remove folders from the system. This permission is crucial for maintaining a streamlined and clutter-free environment.

view_project

Users with "view_project" permission can access and view the content and details of specific projects within the system without the ability to make changes.

create_project

This permission level allows users to initiate and create new projects within the system. Users with this permission can contribute to the expansion and organization of projects.

edit_project_configuration

Users with "edit_project_configuration" permission can customize and modify project-specific settings, ensuring flexibility and optimization for performance and integration needs.

archive_project

The "archive_project" permission enables users to archive projects, providing a way to store projects that are not actively in use without permanently deleting them.

view_branch

Users with "view_branch" permission can access and view details related to branches within the system, facilitating collaboration and visibility into the project's version control.

create_branch

This permission level allows users to create new branches within the system.

archive_branch

The "archive_branch" permission allows users to archive branches that are no longer actively developed or needed, providing a way to organize and declutter the branch list.

view_resource

This permission allows users to access information from both the dbt build, and the integrated BI application within the Data Model screen.

view_changes

The "view_changes" permission grants users the ability to view and track changes. This is valuable for maintaining a history of modifications.

view_operations

Users with "view_operations" permission can access and view details related to ongoing operations within the system. This permission is useful for troubleshooting.

create_pull_request

The "create_pull_request" permission allows users to initiate the process of proposing changes to the codebase from the Change Screen.

propose_change

Users with "propose_change" permission can create a change draft from the list of auto-generated suggestions in the Proposal Screen.

get_data_application_usage

The "get_data_application_usage" permission enables users to view information related to the data application to gain insights into how the data application is being utilized.

User Roles

User Role

Description & Permissions

Account Admin

Description: An "Account Admin" holds control over the entire account, and is pivotal for account management. With the ability to manage integrations, create and delete folders, view and modify projects, administer members, and propose changes, an Account Admin plays a crucial role in maintaining the account's integrity. They can transfer ownership of folders or projects and exercise authority over permission levels.

Owner

Description: An "Owner" enjoys complete control over specific folders or projects, acting as the primary authority. Essential for each entity, an Owner can remove, modify permissions of entity members, transfer ownership, and archive the entity. Owners must have a GitHub account and are instrumental in ensuring the overall well-being and governance of the entity they oversee.

Developer

Description: A "Developer" possesses access to the create pull requests based from change drafts, allowing them to contribute to the data model upstream. They have the ability to create and view folders, projects, branches, and resources. Developers can push and pull changes, maintaining the integrity of the data model. Their role can be assigned at the account, folder, or project level, demonstrating flexibility in permission inheritance.

Contributor

Description: A "Contributor" holds the capability to modify folders and projects, contributing to the evolution of the shared data model. They can create change drafts of the shared data model, actively participating in the development and enhancement of the data model.

Viewer

Description: A "Viewer" is equipped with the ability to access project details without the authority to make changes. Viewers cannot contribute to the project directly, ensuring the integrity of the data.

User Roles with Associated Permissions

Permission

Account Admin

Owner

Developer

Contributor

Viewer

manage_intergrations

βœ“

βœ“

create_folder

βœ“

βœ“

βœ“

βœ“

view_folder

βœ“

βœ“

βœ“

βœ“

βœ“

manage_members

βœ“

βœ“

delete_folder

βœ“

βœ“

view_project

βœ“

βœ“

βœ“

βœ“

βœ“

create_project

βœ“

βœ“

βœ“

edit_project_configuration

βœ“

βœ“

archive_project

βœ“

βœ“

view_branch

βœ“

βœ“

βœ“

βœ“

βœ“

create_branch

βœ“

βœ“

βœ“

archive_branch

βœ“

βœ“

view_resource

βœ“

βœ“

βœ“

βœ“

βœ“

view_changes

βœ“

βœ“

βœ“

βœ“

βœ“

view_operations

βœ“

βœ“

βœ“

create_pull_request

βœ“

βœ“

βœ“

propose_change

βœ“

βœ“

βœ“

βœ“

get_data_application_usage

βœ“

βœ“

βœ“

βœ“

βœ“

Last updated