Skip to main content

How to use roles to manage permissions

M
Written by Martijn van Mechelen
Updated over a week ago

A role includes a set of permissions. The use of roles makes it easy to assign multiple users predefined sets of permissions simultaneously. Note that assigning access to sites is not included in roles; roles only include feature permissions. A role can be assigned at either the organizational level or the site level.

User and Application Roles

You can create roles for both users and applications. This is done in the same way.

Default and Custom Roles

You can make use of Priva's default roles, but you can also create custom roles via the Roles tab.

Default roles

A default role contains a set of permissions predefined by Priva. It is not possible to edit or delete a default role.

Currently, there are only two default user roles:

  • Administrator
    This role includes all permissions available for your organization (depending on the subscription).

  • Installation Partner
    This role includes the permissions required to install and maintain horticultural systems.

This may change the permissions available to your organization. For instance, if your organization changes the subscription or if Priva adds or removes permissions for new/old software features. The added or removed permissions will automatically be added to or removed from the relevant default role(s). There are no default application roles yet.

Custom roles

You can create custom roles via the Roles tab. In a custom role, you include a set of permissions that fit your organization. You can create roles that, for example, only contain view-only permissions or permissions to access specific applications.

When creating a role, consider that some permissions can only be assigned at the organizational level, while others can be assigned site-specifically (for more information, see Roles and site access).

Did this answer your question?