📖 Definition
On your dashboard, you may have multiple projects or feature teams working on different projects. To avoid configuration mistakes, you can allow specific rights to specific users on each project.
⚙️ Configuration
On the dashboard, from each project line, you can click the 3 dots to open the “Edit Rights” panel.
Edit Rights
When you open “edit rights”, there is an administration panel where you find every user who can see and interact with your project.
In this interface, you can add, delete, or modify users of the project and for each environment.
You can define in that one place which user role they should have in each environment.
|
⚡️ Heads Up When doing changes on project rights, don’t forget to save before closing the modal, otherwise, your changes will not be applied. |
User rights
You can choose between 4 different types of user rights on your project rights panel:
From left to right:
- Viewer: Can only have a look at what’s happening on the project
- User: Can create/pause/delete/archive use cases inside the project
- Admin: Same rights as user role, in addition to managing users inside the project
- Blocked: The member will not have access to the project in this environment
|
⭐ Warning A user can be added twice (either ad-hoc or through a team). The higher role of the user will be taken in priority. |
⚙️ Use case
“As a member of a Product-&-Tech team with several feature teams or squads, I deeply need to organize my dashboard to let these teams see only the projects in their scopes.
Thus, for our e-commerce platform, I can create a project for the Home page, another for Product Pages, and another one for the Paywall. But, my 3 feature teams working on those 3 different scopes will only see the project(s) they have been added to.
…of course, as a Project Manager or upper role, I can still have access to everything and control what’s happening on each project.”