![(please configure the [header_logo] section in trac.ini)](/pubtrac/GeniusWeb/chrome/site/your_project_logo.png){kind=logo}
Changes between Version 1 and Version 2 of TracPermissions
- Timestamp:
- 08/11/15 13:16:01 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracPermissions
v1 v2 2 2 [[TracGuideToc]] 3 3 4 Trac uses a simple permission system to control what users can and can't access. 5 6 Permission privileges are managed using the [wiki:TracAdmin trac-admin] tool. 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. 7 9 8 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. 9 10 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". 11 12 13 == Graphical Admin Tab == 14 ''This feature is new in version 0.11.'' 15 16 To access this tab, a user must have one of the following permissions: `TRAC_ADMIN`, `PERMISSION_ADMIN`, `PERMISSION_GRANT`, `PERMISSION_REVOKE`. The permissions can be granted using the `trac-admin` command (more on `trac-admin` 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. 28 29 From the graphical admin tab, users with `PERMISSION_GRANT` will only be allowed to grant permissions that they possess, and users with `PERMISSION_REVOKE` will only be allowed to revoke permissions that they possess. For example, a user cannot grant `MILESTONE_ADMIN` unless they have `PERMISSION_GRANT` and `MILESTONE_ADMIN`, and they cannot revoke `MILESTONE_ADMIN` unless they have `PERMISSION_REVOKE` and `MILESTONE_ADMIN`. `PERMISSION_ADMIN` just grants the user both `PERMISSION_GRANT` and `PERMISSION_REVOKE`, and users with `TRAC_ADMIN` can grant or revoke any permission. 30 12 31 == Available Privileges == 13 32 14 To enable all privileges for a user, use the `TRAC_ADMIN` permission. Having `TRAC_ADMIN` is like being `root` on a *NIX system , it will allow youperform any operation.15 16 Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac ( note that the privilege names are case-sensitive):33 To enable all privileges for a user, use the `TRAC_ADMIN` permission. Having `TRAC_ADMIN` is like being `root` on a *NIX system: it will allow you to perform any operation. 34 35 Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac ('''note that the privilege names are case-sensitive'''): 17 36 18 37 === Repository Browser === … … 28 47 || `TICKET_CREATE` || Create new [wiki:TracTickets tickets] || 29 48 || `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] || 30 || `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties (priority, assignment, keywords, etc.) except description field || 31 || `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets] || 32 || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the description field || 49 || `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 || 50 || `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. || 51 || `TICKET_EDIT_CC` || Full modify cc field || 52 || `TICKET_EDIT_DESCRIPTION` || Modify description field || 53 || `TICKET_EDIT_COMMENT` || Modify comments || 54 || `TICKET_BATCH_MODIFY` || [wiki:TracBatchModify Batch modify] tickets || 55 || `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. || 56 57 Attention: the "view tickets" button appears with the `REPORT_VIEW` permission. 33 58 34 59 === Roadmap === 35 60 36 || `MILESTONE_VIEW` || View a milestone||61 || `MILESTONE_VIEW` || View milestones and assign tickets to milestones. || 37 62 || `MILESTONE_CREATE` || Create a new milestone || 38 63 || `MILESTONE_MODIFY` || Modify existing milestones || 39 64 || `MILESTONE_DELETE` || Delete milestones || 40 65 || `MILESTONE_ADMIN` || All `MILESTONE_*` permissions || 41 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page || 66 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see [trac:#4292 #4292] || 67 || `ROADMAP_ADMIN` || to be removed with [trac:#3022 #3022], replaced by MILESTONE_ADMIN || 42 68 43 69 === Reports === 44 70 45 || `REPORT_VIEW` || View [wiki:TracReports reports] ||71 || `REPORT_VIEW` || View [wiki:TracReports reports], i.e. the "view tickets" link. || 46 72 || `REPORT_SQL_VIEW` || View the underlying SQL query of a [wiki:TracReports report] || 47 73 || `REPORT_CREATE` || Create new [wiki:TracReports reports] || … … 55 81 || `WIKI_CREATE` || Create new [wiki:TracWiki wiki] pages || 56 82 || `WIKI_MODIFY` || Change [wiki:TracWiki wiki] pages || 83 || `WIKI_RENAME` || Rename [wiki:TracWiki wiki] pages || 57 84 || `WIKI_DELETE` || Delete [wiki:TracWiki wiki] pages and attachments || 58 85 || `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. || 86 87 === Permissions === 88 89 || `PERMISSION_GRANT` || add/grant a permission || 90 || `PERMISSION_REVOKE` || remove/revoke a permission || 91 || `PERMISSION_ADMIN` || All `PERMISSION_*` permissions || 59 92 60 93 === Others === … … 63 96 || `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries || 64 97 || `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins || 98 || `EMAIL_VIEW` || Shows email addresses even if [wiki:TracIni#trac-section trac show_email_addresses] configuration option is false || 99 100 == Creating New Privileges == 101 102 To create custom permissions, for example to be used in a custom workflow, enable the optional [trac:ExtraPermissionsProvider tracopt.perm.config_perm_provider.ExtraPermissionsProvider] component in the "Plugins" admin panel, and add the desired permissions to the `[extra-permissions]` section in your [wiki:TracIni#extra-permissions-section trac.ini]. For more information, please refer to the documentation on the [wiki:TracIni#extra-permissions-section TracIni] page after enabling the component. 65 103 66 104 == Granting Privileges == … … 81 119 }}} 82 120 121 Or add all privileges: 122 {{{ 123 $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN 124 }}} 125 83 126 == Permission Groups == 127 128 There are two built-in groups, "authenticated" and "anonymous". 129 Any user who has not logged in is automatically in the "anonymous" group. 130 Any user who has logged in is also in the "authenticated" group. 131 The "authenticated" group inherits permissions from the "anonymous" group. 132 For example, if the "anonymous" group has permission WIKI_MODIFY, 133 it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well. 134 135 Custom groups may be defined that inherit permissions from the two built-in groups. 84 136 85 137 Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc. … … 92 144 }}} 93 145 94 Group membership can be checked by doing a {{{permission list}}} with no further arguments; the resulting output will include group memberships. Use lowercase for group names, as uppercase is reserved for permissions. 146 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'''. 147 148 == Adding a New Group and Permissions == 149 Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group. 150 151 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) 152 {{{ 153 $ trac-admin /path/to/projenv permission add bob beta_testers 154 $ trac-admin /path/to/projenv permission add beta_testers WIKI_ADMIN 155 156 }}} 95 157 96 158 == Removing Permissions == … … 107 169 You can also remove all privileges for a specific user: 108 170 {{{ 109 $ trac-admin /path/to/projenv permission remove bob *171 $ trac-admin /path/to/projenv permission remove bob '*' 110 172 }}} 111 173 112 174 Or one privilege for all users: 113 175 {{{ 114 $ trac-admin /path/to/projenv permission remove *REPORT_ADMIN176 $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN 115 177 }}} 116 178 117 179 == Default Permissions == 118 180 119 Granting privileges to the special user ''anonymous'' can be used to control what an anonymous user can do before they have logged in. 120 121 In the same way, privileges granted to the special user ''authenticated'' will apply to any authenticated (logged in) user. 122 181 By default on a new Trac installation, the `anonymous` user will have ''view'' access to everything in Trac, but will not be able to create or modify anything. 182 On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''. 183 184 '''anonymous''' 185 {{{ 186 BROWSER_VIEW 187 CHANGESET_VIEW 188 FILE_VIEW 189 LOG_VIEW 190 MILESTONE_VIEW 191 REPORT_SQL_VIEW 192 REPORT_VIEW 193 ROADMAP_VIEW 194 SEARCH_VIEW 195 TICKET_VIEW 196 TIMELINE_VIEW 197 WIKI_VIEW 198 }}} 199 200 '''authenticated''' 201 {{{ 202 TICKET_CREATE 203 TICKET_MODIFY 204 WIKI_CREATE 205 WIKI_MODIFY 206 }}} 123 207 ---- 124 See also: TracAdmin, TracGuide and [http://trac.edgewall.org/wiki/FineGrainedPermissions FineGrainedPermissions]208 See also: TracAdmin, TracGuide and TracFineGrainedPermissions
