Roles
Roles define what users can do in Flexera One SaaS Management only, not in other Flexera One capabilities. They are used to assign specific permissions or to give access to specific items or functionalities in Flexera One SaaS Management.
Roles and permissions
A role is a collection of permissions. The permissions give access to selected functionality and define what the users can do in Flexera One SaaS Management.
The permissions have different levels, for example, permission to create, read, update, and delete, or permission to read only.
Default roles
There are predefined default roles in Flexera One SaaS Management that you can use as they are. You cannot edit or delete the default roles.
To view all the permissions included in a default role, in Roles, select a role. In Permissions, you can expand the categories to view the permissions included in the selected role.
Role | Description | Required for access to |
---|---|---|
System administrator | System administrators have create, read, update, and delete access to Flexera One SaaS Management settings, with the exception of General SaaS settings, SaaS connectors, Token broker registrations, and Data imports. |
|
Administrator | Administrators have create, read, update, and delete access to Flexera One SaaS Management, General SaaS settings, SaaS connectors, Token broker registrations, and Data imports. Users who require access to make changes to Flexera One SaaS Management must have the permissions included in this role. |
|
Viewer | Viewers have read access to Flexera One SaaS Management, General SaaS settings, SaaS connectors, and Data imports. |
|
Custom roles
There are predefined default roles in Flexera One SaaS Management that you can use as they are. You can also create custom roles to give access to selected functionality in Flexera One SaaS Management only, not in other Flexera One capabilities. You can base custom roles on a default role or another custom role, or create a custom role without using a base role.
Note that, a custom role and its base role are not connected. Neither changes to the base role nor changes to the custom role affect one another.
Example
Role B is based on Role A so that the two roles include the same permissions. Role A is then updated with an additional permission. The additional permission does not automatically appear in Role B.
Limits
For information on the maximum number of custom roles and role permission assignments permitted in your Snow Atlas system, see Limits and constraints.