Changes between Version 2 and Version 3 of TracPermissions
- Timestamp:
- 19/04/2022 13:22:06 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracPermissions
v2 v3 6 6 Permissions are managed using the [TracAdmin trac-admin] tool or the ''General / Permissions'' panel in the ''Admin'' tab of the web interface. 7 7 8 In addition to the default permission policy described in this page, it is possible to activate additional permission policies by enabling [TracPlugins plugins]and listing them in [TracIni#trac-permission_policies-option "[trac] permission_policies"]. See TracFineGrainedPermissions for more details.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 [TracIni#trac-permission_policies-option "[trac] permission_policies"]. See TracFineGrainedPermissions for more details. 9 9 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 privilege for will not be displayed in the navigation. … … 45 45 || `TICKET_VIEW` || View existing [TracTickets tickets] and perform [TracQuery ticket queries] || 46 46 || `TICKET_CREATE` || Create new [TracTickets tickets] || 47 || `TICKET_APPEND` || Add comments or attachments to [TracTickets tickets]||48 || `TICKET_CHGPROP` || Modify [TracTickets ticket] properties (priority, assignment, keywords, etc.) with the following exceptions: edit description field, add/remove other users from cc field when logged in ||47 || `TICKET_APPEND` || Add comments and attachments to [TracTickets tickets], and edit description of ticket the user created || 48 || `TICKET_CHGPROP` || Modify [TracTickets ticket] properties (priority, assignment, keywords, etc.) with the following exceptions: edit description of tickets created by others, add/remove other users from cc field when logged in || 49 49 || `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [TracTickets tickets] in the [TracWorkflow default workflow]. Tickets can be assigned to users through a [TracTickets#Assign-toasDrop-DownList drop-down list] when the list of possible owners has been restricted. || 50 50 || `TICKET_EDIT_CC` || Full modify cc field || 51 || `TICKET_EDIT_DESCRIPTION` || Modify description field ||51 || `TICKET_EDIT_DESCRIPTION` || Modify description field. User with `TICKET_APPEND` or `TICKET_CHGPROP` can modify description of ticket they created. || 52 52 || `TICKET_EDIT_COMMENT` || Modify another user's comments. Any user can modify their own comments by default. || 53 53 || `TICKET_BATCH_MODIFY` || [TracBatchModify Batch modify] tickets || … … 95 95 || `EMAIL_VIEW` || Shows email addresses even if [TracIni#trac-section trac show_email_addresses] configuration option is false || 96 96 97 == Attachment Permissions 98 99 Attachment permissions are handled by `LegacyAttachmentPolicy`, and unlike the permissions discussed so far, the permissions provided by `LegacyAttachmentPolicy` are not directly granted. Rather, the ability to create, view and delete attachments is determined by the attachment's parent realm and permissions the user possesses for that realm. 100 101 The attachment actions are determined by the following 102 permissions in the ticket, wiki and milestone realms: 103 {{{#!table class="listing" 104 ||= Granted By: =||= Ticket =||= Wiki =||= Milestone =|| 105 || `ATTACHMENT_CREATE` || `TICKET_APPEND` || `WIKI_MODIFY` || `MILESTONE_MODIFY` || 106 || `ATTACHMENT_VIEW` || `TICKET_VIEW` || `WIKI_VIEW` || `MILESTONE_VIEW` || 107 || `ATTACHMENT_DELETE` || `TICKET_ADMIN` || `WIKI_DELETE` || `MILESTONE_DELETE` || 108 }}} 109 110 An authenticated user can delete an attachment //they added// without possessing the permission 111 that grants `ATTACHMENT_DELETE`. 112 113 If explicit attachment permissions are preferred, `ATTACHMENT_CREATE`, `ATTACHMENT_DELETE` and `ATTACHMENT_VIEW` can be created using the [trac:ExtraPermissionsProvider]. The simplest implementation is to simply define the actions. 114 {{{#!ini 115 [extra-permissions] 116 _perms = ATTACHMENT_CREATE, ATTACHMENT_DELETE, ATTACHMENT_VIEW 117 }}} 118 119 An alternative configuration adds an `ATTACHMENT_ADMIN` meta-permission that grants the other 3 permission. 120 {{{#!ini 121 [extra-permissions] 122 ATTACHMENT_ADMIN = ATTACHMENT_CREATE, ATTACHMENT_DELETE, ATTACHMENT_VIEW 123 }}} 124 125 The explicit permissions can be used in concert with `LegacyAttachmentPolicy`, or `LegacyAttachmentPolicy` can be removed from `permission_policies`, in which case only users that have been explicitly granted the corresponding attachment actions will be able to create, delete and view attachments. 126 97 127 == Granting Privileges 98 128 … … 179 209 //**anonymous**// 180 210 {{{ 181 BROWSER_VIEW 182 CHANGESET_VIEW 183 FILE_VIEW 184 LOG_VIEW 185 MILESTONE_VIEW 186 REPORT_SQL_VIEW 187 REPORT_VIEW 188 ROADMAP_VIEW 189 SEARCH_VIEW 190 TICKET_VIEW 211 BROWSER_VIEW 212 CHANGESET_VIEW 213 FILE_VIEW 214 LOG_VIEW 215 MILESTONE_VIEW 216 REPORT_SQL_VIEW 217 REPORT_VIEW 218 ROADMAP_VIEW 219 SEARCH_VIEW 220 TICKET_VIEW 191 221 TIMELINE_VIEW 192 222 WIKI_VIEW … … 195 225 //**authenticated**// 196 226 {{{ 197 TICKET_CREATE 198 TICKET_MODIFY 199 WIKI_CREATE 200 WIKI_MODIFY 227 TICKET_CREATE 228 TICKET_MODIFY 229 WIKI_CREATE 230 WIKI_MODIFY 201 231 }}} 202 232 ----
