In this article we will discuss how you can manage roles and rights by making use of the combined functionality of subscription roles, project teams and modules.
Rights are assigned on two levels:
Subscription roles - This defines what rights you have within a subscription.
Project roles - This defines what you can see and edit within a project.
Note: Whenever a view contains data that the end user cannot see, the whole view is hidden.
Please watch the below instruction video to learn more.
Video content
0:00 Introduction
0:25 Steps to take
2:20 Why roles & rights?
3:54 Extensive answer
4:12 Roles & rights in levvr
6:57 Subscription roles
10:00 Modules
10:30 Project teams & roles
Interesting links
Subscription roles
After creating a new user account this account gets assigned the Project contributor role by default. This means that the user using that account can see and enter projects that this person has project roles for. For most users, this role will be enough. However, this can be changed into one or more of the other subscription roles to provide for additional subscription rights. Only a subscription administrator can change the subscription roles for an account. For an overview of the different subscription roles, have a look here.
Project roles
After creating a semantic model within the blueprint, you can assign parts of the model to modules. These modules form a base for setting the rights a role within a project team has. Rights can be set to per module. These are one of the following:
None - The role is not allowed to see or edit the module. As soon as a view contains information that is part of a module for which the rights are set to none, the whole view will be hidden for a user.
View - The role is allowed to view, but not edit a module
Edit - The role is allowed to edit the par of the model that is contained by the module.
When desired, rights can be set on the level of node and relation.
Example: