![(please configure the [header_logo] section in trac.ini)](/projects/oscar/chrome/site/your_project_logo.png){kind=logo}
Changes between Version 1 and Version 2 of TracPermissions
- Timestamp:
- Oct 23, 2010, 8:43:57 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracPermissions
v1 v2 4 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 [TracAdmin trac-admin] tool or the ''General / Permissions'' panel in the ''Admin''web interface.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 7 8 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. … … 10 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 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). 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. 12 25 13 26 == Available Privileges == … … 29 42 || `TICKET_CREATE` || Create new [wiki:TracTickets tickets] || 30 43 || `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] || 31 || `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties (priority, assignment, keywords, etc.) except description field, cc field add/remove when logged in orset email to pref ||32 || `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets] ||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. || 33 46 || `TICKET_EDIT_CC` || Full modify cc field || 34 47 || `TICKET_EDIT_DESCRIPTION` || Modify description field || 35 || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the description field || 48 || `TICKET_EDIT_COMMENT` || Modify comments || 49 || `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. || 36 50 37 51 Attention: the "view tickets" button appears with the `REPORT_VIEW` permission. … … 39 53 === Roadmap === 40 54 41 || `MILESTONE_VIEW` || View a milestone||55 || `MILESTONE_VIEW` || View milestones and assign tickets to milestones. || 42 56 || `MILESTONE_CREATE` || Create a new milestone || 43 57 || `MILESTONE_MODIFY` || Modify existing milestones || 44 58 || `MILESTONE_DELETE` || Delete milestones || 45 59 || `MILESTONE_ADMIN` || All `MILESTONE_*` permissions || 46 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see #4292||47 || `ROADMAP_ADMIN` || to be removed with #3022, replaced by MILESTONE_ADMIN ||60 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see [trac:#4292 #4292] || 61 || `ROADMAP_ADMIN` || to be removed with [trac:#3022 #3022], replaced by MILESTONE_ADMIN || 48 62 49 63 === Reports === … … 61 75 || `WIKI_CREATE` || Create new [wiki:TracWiki wiki] pages || 62 76 || `WIKI_MODIFY` || Change [wiki:TracWiki wiki] pages || 77 || `WIKI_RENAME` || Rename [wiki:TracWiki wiki] pages || 63 78 || `WIKI_DELETE` || Delete [wiki:TracWiki wiki] pages and attachments || 64 79 || `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. || … … 76 91 || `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries || 77 92 || `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins || 78 || `EMAIL_VIEW` || Shows email addresses even if [ wiki:0.11/TracIni `trac show_email_addresses` configuration option is `false`] ||93 || `EMAIL_VIEW` || Shows email addresses even if [trac:wiki:0.11/TracIni trac show_email_addresses configuration option is false] || 79 94 80 95 == Granting Privileges == … … 102 117 == Permission Groups == 103 118 104 There are two built-in groups, "authenticated" and "anonymous".[[BR]] 105 Any user who has not logged in is automatically in the "anonymous" group.[[BR]] 106 Any user who has logged in is also in the "authenticated" group.[[BR]] 107 The "authenticated" group inherits permissions from the "anonymous" group.[[BR]] 108 eg. if the "anonymous" group has permission WIKI_MODIFY, it's not necessary to add the WIKI_MODIFY permisison to the "authenticated" group as well. 119 There are two built-in groups, "authenticated" and "anonymous". 120 Any user who has not logged in is automatically in the "anonymous" group. 121 Any user who has logged in is also in the "authenticated" group. 122 The "authenticated" group inherits permissions from the "anonymous" group. 123 For example, if the "anonymous" group has permission WIKI_MODIFY, 124 it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well. 109 125 110 126 Custom groups may be defined that inherit permissions from the two built-in groups. … … 119 135 }}} 120 136 121 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 isreserved for permissions'''.137 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'''. 122 138 123 139 == Adding a New Group and Permissions == … … 157 173 On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''. 158 174 159 '''anonymous''':: 175 '''anonymous''' 176 {{{ 160 177 BROWSER_VIEW 161 178 CHANGESET_VIEW … … 169 186 TICKET_VIEW 170 187 TIMELINE_VIEW 171 WIKI_VIEW 188 WIKI_VIEW 189 }}} 172 190 173 '''authenticated''':: 191 '''authenticated''' 192 {{{ 174 193 TICKET_CREATE 175 194 TICKET_MODIFY 176 195 WIKI_CREATE 177 196 WIKI_MODIFY 178 197 }}} 179 198 ---- 180 199 See also: TracAdmin, TracGuide and TracFineGrainedPermissions
