![(please configure the [header_logo] section in trac.ini)](/pubtrac/GeniusWebRunServer/chrome/site/your_project_logo.png){kind=logo}
Changes between Version 2 and Version 3 of TracPermissions
- Timestamp:
- 12/24/20 10:50:38 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracPermissions
v2 v3 13 13 == Graphical Admin Tab 14 14 15 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 with a more detailed description [#GrantingPrivileges below]:15 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): 16 16 {{{#!sh 17 17 $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN … … 30 30 == Available Privileges 31 31 32 To enable all privileges for a user, use the `TRAC_ADMIN` permission. This permissionis like being `root` on a *NIX system: it will allow you to perform any operation.33 34 Otherwise, individual privileges can be assigned to users for the different functional areas of Trac and '''note that the privilege names are uppercase''':32 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. 33 34 Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac ('''note that the privilege names are case-sensitive'''): 35 35 36 36 === Repository Browser … … 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 || 54 || `TICKET_ADMIN` || All `TICKET_*` permissions, deletion of ticket attachments and modification of the reporter field, which grants ability to create a ticket on behalf of another user and it will appear that another user created the ticket. It also allows managing ticket properties through the web administration module. ||54 || `TICKET_ADMIN` || All `TICKET_*` permissions, deletion of ticket attachments and modification of the reporter field, which grants ability to create a ticket on behalf of another user (it will appear that another user created the ticket). It also allows managing ticket properties through the web administration module. || 55 55 56 56 === Roadmap … … 108 108 }}} 109 109 110 An authenticated user can delete an attachment //they added// without possessing the permission111 that grants `ATTACHMENT_DELETE`.112 113 110 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 111 {{{#!ini … … 153 150 Any user who has logged in is also in the //authenticated// group. 154 151 The //authenticated// group inherits permissions from the //anonymous// group. 155 For example, if the //anonymous// group has permission WIKI_MODIFY, it is not necessary to add the WIKI_MODIFY permission to the //authenticated// group as well. 152 For example, if the //anonymous// group has permission WIKI_MODIFY, 153 it is not necessary to add the WIKI_MODIFY permission to the //authenticated// group as well. 156 154 157 155 Custom groups may be defined that inherit permissions from the two built-in groups. … … 171 169 Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group. 172 170 173 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.171 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) 174 172 {{{#!sh 175 173 $ trac-admin /path/to/projenv permission add bob beta_testers … … 179 177 == Removing Permissions 180 178 181 Permissions can be removed using the 'remove' command. 179 Permissions can be removed using the 'remove' command. For example: 182 180 183 181 This command will prevent the user ''bob'' from deleting reports: … … 209 207 //**anonymous**// 210 208 {{{ 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 209 BROWSER_VIEW 210 CHANGESET_VIEW 211 FILE_VIEW 212 LOG_VIEW 213 MILESTONE_VIEW 214 REPORT_SQL_VIEW 215 REPORT_VIEW 216 ROADMAP_VIEW 217 SEARCH_VIEW 218 TICKET_VIEW 221 219 TIMELINE_VIEW 222 220 WIKI_VIEW … … 225 223 //**authenticated**// 226 224 {{{ 227 TICKET_CREATE 228 TICKET_MODIFY 229 WIKI_CREATE 230 WIKI_MODIFY 225 TICKET_CREATE 226 TICKET_MODIFY 227 WIKI_CREATE 228 WIKI_MODIFY 231 229 }}} 232 230 ----
