RedmineRoles » History » Version 1
Jean-Philippe Lang, 2007-10-12 21:05
| 1 | 1 | Jean-Philippe Lang | h1. Roles & permissions |
|---|---|---|---|
| 2 | |||
| 3 | Roles lets you define the permissions that the members have on a project. Each member of a project has a one Role for the project. A user can have different roles for different projects. |
||
| 4 | |||
| 5 | You can create new roles or edit existing ones. You can delete a role only if nobody has this role on a project. |
||
| 6 | |||
| 7 | h2. Roles properties |
||
| 8 | |||
| 9 | * *Name*: display name of the role |
||
| 10 | * *Issues can be assigned to this role*: if unchecked, issues can not be assigned to members who have this role on the project. |
||
| 11 | |||
| 12 | h2. Permission |
||
| 13 | |||
| 14 | When editing a role, you can define its permissions by checking/unchecking the different actions. |
||
| 15 | |||
| 16 | h2. System roles |
||
| 17 | |||
| 18 | There are 2 system roles in Redmine: 'Non member' and 'Anonymous'. They are internally used by Redmine and thus can not be deleted. |
||
| 19 | |||
| 20 | * *Non member*: this role lets you define the permissions that a registered user has on projects which he is not a member of. |
||
| 21 | * *Anonymous*: this role lets you define the permissions that anonymous users have on the projects. |
||
| 22 | |||
| 23 | Not that these permissions only apply to public projects since a user who is not a member of a private project can not even see it. |