Changes between Version 1 and Version 2 of TracPermissions
- Timestamp:
- 05/09/10 05:59:49 (16 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.4 Trac uses a simple, case sensitive, permission system to control what users can and can't access. 5 5 6 Permission privileges are managed using the [wiki:TracAdmin trac-admin] tool. 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. 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". 9 12 10 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". 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). 22 23 24 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. 11 25 12 26 == Available Privileges == 13 27 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.28 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. 15 29 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):30 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 31 18 32 === Repository Browser === … … 28 42 || `TICKET_CREATE` || Create new [wiki:TracTickets tickets] || 29 43 || `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 || 44 || `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 || 45 || `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. || 46 || `TICKET_EDIT_CC` || Full modify cc field || 47 || `TICKET_EDIT_DESCRIPTION` || Modify description field || 48 || `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. || 49 50 Attention: the "view tickets" button appears with the `REPORT_VIEW` permission. 33 51 34 52 === Roadmap === 35 53 36 || `MILESTONE_VIEW` || View a milestone||54 || `MILESTONE_VIEW` || View milestones and assign tickets to milestones. || 37 55 || `MILESTONE_CREATE` || Create a new milestone || 38 56 || `MILESTONE_MODIFY` || Modify existing milestones || 39 57 || `MILESTONE_DELETE` || Delete milestones || 40 58 || `MILESTONE_ADMIN` || All `MILESTONE_*` permissions || 41 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page || 59 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see [trac:#4292 #4292] || 60 || `ROADMAP_ADMIN` || to be removed with [trac:#3022 #3022], replaced by MILESTONE_ADMIN || 42 61 43 62 === Reports === 44 63 45 || `REPORT_VIEW` || View [wiki:TracReports reports] ||64 || `REPORT_VIEW` || View [wiki:TracReports reports], i.e. the "view tickets" link. || 46 65 || `REPORT_SQL_VIEW` || View the underlying SQL query of a [wiki:TracReports report] || 47 66 || `REPORT_CREATE` || Create new [wiki:TracReports reports] || … … 58 77 || `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. || 59 78 79 === Permissions === 80 81 || `PERMISSION_GRANT` || add/grant a permission || 82 || `PERMISSION_REVOKE` || remove/revoke a permission || 83 || `PERMISSION_ADMIN` || All `PERMISSION_*` permissions || 84 85 60 86 === Others === 61 87 … … 63 89 || `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries || 64 90 || `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins || 91 || `EMAIL_VIEW` || Shows email addresses even if [trac:wiki:0.11/TracIni trac show_email_addresses configuration option is false] || 65 92 66 93 == Granting Privileges == … … 81 108 }}} 82 109 110 Or add all privileges: 111 {{{ 112 $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN 113 }}} 114 83 115 == Permission Groups == 116 117 There are two built-in groups, "authenticated" and "anonymous". 118 Any user who has not logged in is automatically in the "anonymous" group. 119 Any user who has logged in is also in the "authenticated" group. 120 The "authenticated" group inherits permissions from the "anonymous" group. 121 For example, if the "anonymous" group has permission WIKI_MODIFY, 122 it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well. 123 124 Custom groups may be defined that inherit permissions from the two built-in groups. 84 125 85 126 Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc. … … 92 133 }}} 93 134 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. 135 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'''. 136 137 == Adding a New Group and Permissions == 138 Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group. 139 140 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) 141 {{{ 142 $ trac-admin /path/to/projenv permission add bob beta_testers 143 $ trac-admin /path/to/projenv permission add beta_testers WIKI_ADMIN 144 145 }}} 95 146 96 147 == Removing Permissions == … … 107 158 You can also remove all privileges for a specific user: 108 159 {{{ 109 $ trac-admin /path/to/projenv permission remove bob *160 $ trac-admin /path/to/projenv permission remove bob '*' 110 161 }}} 111 162 112 163 Or one privilege for all users: 113 164 {{{ 114 $ trac-admin /path/to/projenv permission remove *REPORT_ADMIN165 $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN 115 166 }}} 116 167 117 168 == Default Permissions == 118 169 119 Granting privileges to the special user ''anonymous'' can be used to control what an anonymous user can do before they have logged in. 170 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. 171 On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''. 120 172 121 In the same way, privileges granted to the special user ''authenticated'' will apply to any authenticated (logged in) user. 173 '''anonymous''' 174 {{{ 175 BROWSER_VIEW 176 CHANGESET_VIEW 177 FILE_VIEW 178 LOG_VIEW 179 MILESTONE_VIEW 180 REPORT_SQL_VIEW 181 REPORT_VIEW 182 ROADMAP_VIEW 183 SEARCH_VIEW 184 TICKET_VIEW 185 TIMELINE_VIEW 186 WIKI_VIEW 187 }}} 122 188 189 '''authenticated''' 190 {{{ 191 TICKET_CREATE 192 TICKET_MODIFY 193 WIKI_CREATE 194 WIKI_MODIFY 195 }}} 123 196 ---- 124 See also: TracAdmin, TracGuide and [http://trac.edgewall.org/wiki/FineGrainedPermissions FineGrainedPermissions]197 See also: TracAdmin, TracGuide and TracFineGrainedPermissions
