Changes between Version 2 and Version 3 of TracPermissions
- Timestamp:
- Jun 8, 2011, 7:44:12 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracPermissions
v2 v3 19 19 }}} 20 20 21 Then, the user 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).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 22 23 23 … … 42 42 || `TICKET_CREATE` || Create new [wiki:TracTickets tickets] || 43 43 || `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] || 44 || `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 ||45 || `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. || 46 46 || `TICKET_EDIT_CC` || Full modify cc field || 47 47 || `TICKET_EDIT_DESCRIPTION` || Modify description field || 48 || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the 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 49 50 50 Attention: the "view tickets" button appears with the `REPORT_VIEW` permission. … … 52 52 === Roadmap === 53 53 54 || `MILESTONE_VIEW` || View a milestone||54 || `MILESTONE_VIEW` || View milestones and assign tickets to milestones. || 55 55 || `MILESTONE_CREATE` || Create a new milestone || 56 56 || `MILESTONE_MODIFY` || Modify existing milestones || 57 57 || `MILESTONE_DELETE` || Delete milestones || 58 58 || `MILESTONE_ADMIN` || All `MILESTONE_*` permissions || 59 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see #4292||60 || `ROADMAP_ADMIN` || to be removed with #3022, replaced by MILESTONE_ADMIN ||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 || 61 61 62 62 === Reports === … … 89 89 || `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries || 90 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 [ wiki:0.11/TracIni `trac show_email_addresses` configuration option is `false`] ||91 || `EMAIL_VIEW` || Shows email addresses even if [trac:wiki:0.11/TracIni trac show_email_addresses configuration option is false] || 92 92 93 93 == Granting Privileges == … … 115 115 == Permission Groups == 116 116 117 There are two built-in groups, "authenticated" and "anonymous".[[BR]] 118 Any user who has not logged in is automatically in the "anonymous" group.[[BR]] 119 Any user who has logged in is also in the "authenticated" group.[[BR]] 120 The "authenticated" group inherits permissions from the "anonymous" group.[[BR]] 121 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. 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. 122 123 123 124 Custom groups may be defined that inherit permissions from the two built-in groups. … … 170 171 On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''. 171 172 172 '''anonymous''':: 173 '''anonymous''' 174 {{{ 173 175 BROWSER_VIEW 174 176 CHANGESET_VIEW … … 182 184 TICKET_VIEW 183 185 TIMELINE_VIEW 184 WIKI_VIEW 186 WIKI_VIEW 187 }}} 185 188 186 '''authenticated''':: 189 '''authenticated''' 190 {{{ 187 191 TICKET_CREATE 188 192 TICKET_MODIFY 189 193 WIKI_CREATE 190 194 WIKI_MODIFY 191 195 }}} 192 196 ---- 193 197 See also: TracAdmin, TracGuide and TracFineGrainedPermissions