Users and roles
- Juan Tomás Alonso Nieto (Deactivated)
- Borja Moro Moreno
- Former user (Deleted)
About users and roles
Users are individuals who can access one or many Devo domains. A user is required to have an e-mail address and, when initially created, must validate the e-mail address and establish a password for logging into Devo. Once established, this password will be valid for logging into any additional domains the user may be invited to join.
Users are also associated with at least one or several roles. Roles allow administrators to control access to specific features of the Devo Platform.
When you are logged in, the type of role you have in the current domain is displayed in the header of the navigation pane.
Default roles
By default, every domain has two roles; Admin, and No Privileges. You can create additional, custom roles to grant access to specific features and applications with different granularity levels.
Role | Description | Icon | |
|---|---|---|---|
Admin | This is a role that grants full application permissions. There can be multiple Admin users in any domain. | Â  | |
Owner | This special type of Admin user is automatically assigned to the user who created the domain. There is only one Owner in a domain and their privileges cannot be revoked by any other domain user. You can transfer the Owner role to a different Admin user in the domain by accessing Administration → Users. Place the cursor on the required user and click the ellipsis icon that appears at the end of the row, next to the status icon. Then, select Set as Owner. | ||
No Privileges | This is the basic role for users with limited permissions. This role does not have access to the Activeboards, Data upload, Administration, Tools, and Flow editor areas of the web application. The No Privileges role includes permissions for modifying its own user settings but not for modifying other users' or domain settings. They can be configured to receive alerts but they do not have the ability to create them. No Privileges users can have one or more custom roles assigned in order to grant them additional privileges. The No Privileges role also has a Default finder setting. If you have created custom finders for the domain, you can select any of these to be the default finder for this role. |   | |
Default roles permissions
You cannot modify the default role permissions, but the No privileges role can be granted access to specific applications and alerts.
Custom roles
Administrators and users with the required permission can create an unlimited number of custom roles for a Devo domain. This can be useful, especially in large organizations, to limit each user to the specific features of the application relevant to their job. Users with a custom role assigned are represented with a key icon in the header of the navigation pane.
If a user has multiple roles, their permissions will be the sum of those roles. There is no need to switch between them. For example, if a user is assigned both the Marketing and DevOps roles, they will have the combined permissions of those two roles. Users with multiple custom roles will have the key icon in the Navigation pane, just like users with a single custom role.
Tip
Consider the specific application features each user profile needs and create custom roles accordingly. This granularity grants full control over the way users interact with the platform. Grant or revoke access by assigning or removing roles from users. See Managing roles for more info.