Roles
A role defines what actions a user can perform within a project.
Redmine includes about 70 different permissions, such as “Edit project” and “Add issues.”
A role is essentially a set of these permissions combined into one definition.
Roles are also referenced in workflows, which define how issue statuses can transition from one state to another.
When adding a user as a member of a project, you must assign them a role.
This determines what actions the user can perform within that specific project.
Default Roles
Right after installation, Redmine provides three default roles: Manager, Developer, and Reporter.
Manager
Can perform nearly all operations within the project.
Developer
Cannot perform certain actions such as adding members or deleting issues,
but has sufficient permissions for general use.
Reporter
A role intended for testers, allowing only limited actions such as creating issues.
Being assigned the Manager role in a project does not necessarily grant access to Redmine’s global administration settings.
Built-in Roles
In addition to the default roles, Redmine has special built-in roles with specific meanings.
Non-member
Applied when a logged-in user accesses a public project they are not a member of.
Anonymous
Applied when a user who is not logged in accesses a public project.
Adding, Editing, and Deleting Roles
You can review or modify the permissions assigned to each role, or create new roles under Administration → Roles and Permissions.
When comparing permissions among roles or editing multiple roles at once, the Permissions report screen under Administration → Roles and Permissions → Permissions report is particularly useful.
