Users and roles
- Juan Tomás Alonso Nieto (Deactivated)
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
You cannot modify the default role permissions, but you can grant or remove access to applications, alerts, lookups, and Activeboards.
Custom roles
Administrators 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. A custom role can be assigned a default finder, but only if given View permissions on finders.
Users with a custom role assigned are represented with this icon  in the header of the navigation pane.
If a user is assigned multiple roles, their effective permissions will be the sum of all the permissions of those roles. The user has the ability to choose from the list of default finders associated with their roles. A user may be assigned the custom role Marketing and at the same time the custom role DevOps. This user will enjoy the sum of the permissions of those two roles seamlessly. There is no switching between custom roles in Devo. The user with multiple custom roles will have the wrench icon in the Navigation pane, the same as a user with a single custom role assigned.
Tip
Consider the specific application features that may be required for different user profiles. By creating granular custom roles that grant access to specific features, you can more easily control the permissions that each user possesses. You will be able to grant or rescind access to features as needed by assigning roles to or removing roles from application users. See Managing roles for more info.