Roles and permissions
Account, groups and permissionsThe video is narrated in German; you can switch on subtitles in the player. Playing the video connects to YouTube (Google). More in the privacy policy · Watch on YouTube
Access to projects depends on membership in a group. Each member has exactly one role in the group; it applies to all projects of this group. Non-members do not see the group's projects.
The four roles
The roles build on each other: each role may do everything the roles below it may do.
| Role | For whom | May additionally |
|---|---|---|
| READ (reader) | stakeholders who want to stay informed | read all content, baselines, reviews, metrics; export Excel, Word, ReqIF and backup |
| COMMENT (commenter) | customers, suppliers, quality assurance | comment and mention, take part in reviews and decide, approve baselines, submit change requests |
| EDIT (editor) | the project team | create, change, move, delete modules and artifacts; set and clear links; create baselines; start reviews; implement accepted requests; import Excel/CSV; create, copy and rename projects |
| ADMIN (group admin) | project management | change project properties (types, attributes, link types); import ReqIF; decide on change requests; delete baselines; archive and delete projects; manage members and roles |
The configuration of a project is deliberately reserved for group admins: a changed type or attribute definition affects all artifacts and exports.
Anyone can be an admin
You do not need a central administrator. Every registered user can found a group and is then its group admin. As admin you invite members and assign their roles.
Recommendations
- As few rights as necessary: customers and suppliers who review and approve receive COMMENT. They can then have their say and approve, but not change anything.
- Two admins: in important groups, appoint a second person as ADMIN so that the group remains able to act during absences.
- Separate groups for separate partners: roles apply group-wide. If you work with different customers, create one group per customer.
Access via the API
Access keys for the REST API act with the rights of their owner. Write access additionally requires a key with write permission. The API itself requires the ETRM API add-on to your own Single or Team subscription.