Roles and Permissions
AdministrationIn ETRM, access to projects and requirements is controlled via a role-based system. These permissions are tied to membership in a Group. Only members of a group can see or edit the projects assigned to that group.
The Four Permission Levels
Each group member holds one of the following roles, which determine the scope of functions within projects:
| Role | Designation | Description |
|---|---|---|
| ADMIN | Administrator | Has full control over the group. Can manage members, change roles, delete/archive projects, and edit all content. |
| EDIT | Editor | Can create and edit requirements, manage tags, and write comments. Cannot delete projects or manage group members. |
| COMMENT | Commentator | Can read requirements and their details and write comments. Cannot change the text of requirements or create new ones. |
| READ | Reader | Has read-only access to all projects and requirements of the group. Ideal for stakeholders who only need to stay informed. |
Sovereignty: Anyone Can Be an Admin
A fundamental principle of ETRM is the decentralization of administration. You don't have to wait for a central IT administrator to start working:
- Create your own groups: Every registered user has the right to found their own group.
- Automatic Admin Status: By creating a group, you automatically become its Group Admin (ADMIN).
- Full Control: As the founder, you alone decide whom to invite to your group, which permission level they receive, and which projects you work on together.
Best Practices for Granting Rights
The Principle of Least Privilege: Assign rights as sparingly as possible. A stakeholder who only reads reports should receive the READ role to avoid accidental changes.
Two-Admin Rule: For important projects, appoint a second person as ADMIN. This ensures the group remains fully operational even if the founder is absent.