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 you to control access to specific features of the Devo web application.
When you are logged in, the type of role you have in the current domain is displayed in the header of the navigation pane.
By default, every domain has three roles; Owner, Admin, and No Privileges. You can create additional, custom roles to grant access to specific features and applications.
The user who created the domain is a special Admin user called Owner. There is only one Owner in a domain and their privileges cannot be revoked by any other domain user. To transfer the Owner role to a different Admin user in the domain, go to Administration → Users. Place the cursor on the required user to highlight the entire row and an ellipsis icon will appear at the end of the row, next to the status icon. Click it and select Set as Owner.
Like the Admin, the Owner role grants all the application permissions.
This is a role that grants full application permissions. There can be multiple Admin users in any domain.
This is the basic role for users with limited permissions. This role does not have access to the Panels, Data Upload, and Activeboards 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.
You cannot modify the permissions that the default roles have but you can grant or rescind access to applications, dashboards and panels.
Administrators can create an unlimited number of custom roles for a Devo domain. It 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 their permissions include View finders.
Users with a custom role assigned are represented with this iconin the header of the navigation pane.
If a user is assigned multiple roles, the effective permissions for that user will be the sum of the permissions of each role. Similarly, the user will have the ability to choose from the list of default finders associated with their roles.
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.