| 4 | | Trac uses a simple but flexible permission system to control what users can and can't access. |
| 5 | | |
| 6 | | Permission privileges are managed using the [wiki:TracAdmin trac-admin] tool. |
| 7 | | |
| 8 | | Regular visitors, non-authenticated users, accessing the system are assigned the default |
| 9 | | role (''user'') named {{{anonymous}}}. |
| 10 | | Assign permissions to the {{{anonymous}}} user to set privileges for non-authenticated/guest users. |
| 11 | | |
| 12 | | In addition to these privileges users can be granted additional individual |
| 13 | | rights in effect when authenticated and logged into the system. |
| | 4 | Trac uses a simple, case sensitive, permission system to control what users can and can't access. |
| | 5 | |
| | 6 | Permission privileges are managed using the [TracAdmin trac-admin] tool or (new in version 0.11) the ''General / Permissions'' panel in the ''Admin'' tab of the web interface. |
| | 7 | |
| | 8 | In addition to the default permission policy described in this page, it is possible to activate additional permission policies by enabling plugins and listing them in the `[trac] permission_policies` configuration entry in the TracIni. See TracFineGrainedPermissions for more details. |
| | 9 | |
| | 10 | Non-authenticated users accessing the system are assigned the name "anonymous". Assign permissions to the "anonymous" user to set privileges for anonymous/guest users. The parts of Trac that a user does not have the privileges for will not be displayed in the navigation. |
| | 11 | In addition to these privileges, users can be granted additional individual rights in effect when authenticated and logged into the system. All logged in users belong to the virtual group "authenticated", which inherits permissions from "anonymous". |
| | 12 | |
| | 13 | == Graphical Admin Tab == |
| | 14 | ''This feature is new in version 0.11.'' |
| | 15 | |
| | 16 | To access this tab, a user must have `TRAC_ADMIN privileges`. This can be performed as follows (more on the trac-admin script below): |
| | 17 | {{{ |
| | 18 | $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN |
| | 19 | }}} |
| | 20 | |
| | 21 | Then, the user `bob` will be able to see the Admin tab, and can then access the permissions menu. This menu will allow you to perform all the following actions, but from the browser without requiring root access to the server (just the correct permissions for your user account). '''Use at least one lowercase character in user names, as all-uppercase names are reserved for permissions.''' |
| | 22 | |
| | 23 | 1. [[Image(htdocs:../common/guide/admin.png)]] |
| | 24 | 1. [[Image(htdocs:../common/guide/admin-permissions.png)]] |
| | 25 | 1. [[Image(htdocs:../common/guide/admin-permissions-TICKET_ADMIN.png)]] |
| | 26 | |
| | 27 | An easy way to quickly secure a new Trac install is to run the above command on the anonymous user, install the [http://trac-hacks.org/wiki/AccountManagerPlugin AccountManagerPlugin], create a new admin account graphically and then remove the TRAC_ADMIN permission from the anonymous user. |
| 33 | | || `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties || |
| 34 | | || `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets] || |
| 35 | | || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments. || |
| | 47 | || `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties (priority, assignment, keywords, etc.) with the following exceptions: edit description field, add/remove other users from cc field when logged in, and set email to pref || |
| | 48 | || `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets]. Tickets can be assigned to users through a [TracTickets#Assign-toasDrop-DownList drop-down list] when the list of possible owners has been restricted. || |
| | 49 | || `TICKET_EDIT_CC` || Full modify cc field || |
| | 50 | || `TICKET_EDIT_DESCRIPTION` || Modify description field || |
| | 51 | || `TICKET_EDIT_COMMENT` || Modify comments || |
| | 52 | || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the reporter and description fields. It also allows managing ticket properties in the WebAdmin panel. || |
| | 53 | |
| | 54 | Attention: the "view tickets" button appears with the `REPORT_VIEW` permission. |
| | 124 | |
| | 125 | There are two built-in groups, "authenticated" and "anonymous". |
| | 126 | Any user who has not logged in is automatically in the "anonymous" group. |
| | 127 | Any user who has logged in is also in the "authenticated" group. |
| | 128 | The "authenticated" group inherits permissions from the "anonymous" group. |
| | 129 | For example, if the "anonymous" group has permission WIKI_MODIFY, |
| | 130 | it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well. |
| | 131 | |
| | 132 | Custom groups may be defined that inherit permissions from the two built-in groups. |
| | 143 | Group membership can be checked by doing a {{{permission list}}} with no further arguments; the resulting output will include group memberships. '''Use at least one lowercase character in group names, as all-uppercase names are reserved for permissions'''. |
| | 144 | |
| | 145 | == Adding a New Group and Permissions == |
| | 146 | Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group. |
| | 147 | |
| | 148 | The following will add ''bob'' to the new group called ''beta_testers'' and then will assign WIKI_ADMIN permissions to that group. (Thus, ''bob'' will inherit the WIKI_ADMIN permission) |
| | 149 | {{{ |
| | 150 | $ trac-admin /path/to/projenv permission add bob beta_testers |
| | 151 | $ trac-admin /path/to/projenv permission add beta_testers WIKI_ADMIN |
| | 152 | |
| | 153 | }}} |
| | 154 | |
| | 155 | == Removing Permissions == |
| | 156 | |
| | 157 | Permissions can be removed using the 'remove' command. For example: |
| | 158 | |
| | 159 | This command will prevent the user ''bob'' from deleting reports: |
| | 160 | {{{ |
| | 161 | $ trac-admin /path/to/projenv permission remove bob REPORT_DELETE |
| | 162 | }}} |
| | 163 | |
| | 164 | Just like `permission add`, this command accepts multiple privilege names. |
| | 165 | |
| | 166 | You can also remove all privileges for a specific user: |
| | 167 | {{{ |
| | 168 | $ trac-admin /path/to/projenv permission remove bob '*' |
| | 169 | }}} |
| | 170 | |
| | 171 | Or one privilege for all users: |
| | 172 | {{{ |
| | 173 | $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN |
| | 174 | }}} |
| | 175 | |
