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:35 Why roles & rights?
1:46 Extensive answer
2:00 Roles & rights in levvr
3:20 Subscription roles
5:20 Modules
5:55 Project teams & roles
Interesting links
Subscription rights
Subscription administrator
The ability to access the company subscription setting and invite new users.
Invite new users
Assign application roles to users
Template administrator
See and edit all blueprints
Create new blueprint(versions)
Project teams administrator
The ability to create and edit project teams.
Note: this is a seperate role since project teams can be reused across blueprints.
Project administrator
Create new projects
Manage settings of existing projects
Project data importer
Create import mappings
Import data
Integrations administrator
Create integrations
Manage existing integrations
Project contributer (Base role)
See projects for which you have access rights
Work within projects based on project roles. Project roles are set seperately
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: