![(please configure the [header_logo] section in trac.ini)](/trac/debbuild/chrome/site/your_project_logo.png){kind=logo}
Changes between Version 2 and Version 3 of TracPermissions
- Timestamp:
- 03/14/20 12:12:44 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracPermissions
v2 v3 1 = Trac Permissions =1 = Trac Permissions 2 2 [[TracGuideToc]] 3 3 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 (new in version 0.11)the ''General / Permissions'' panel in the ''Admin'' tab of the web interface.6 Permission privileges are managed using the [TracAdmin trac-admin] tool or 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. … … 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 12 13 == Graphical Admin Tab == 14 ''This feature is new in version 0.11.'' 13 == Graphical Admin Tab 15 14 16 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): … … 29 28 From the graphical admin tab, users with `PERMISSION_GRANT` will only be allowed to grant permissions that they possess, and users with `PERMISSION_REVOKE` will only be allowed to revoke permissions that they possess. For example, a user cannot grant `MILESTONE_ADMIN` unless they have `PERMISSION_GRANT` and `MILESTONE_ADMIN`, and they cannot revoke `MILESTONE_ADMIN` unless they have `PERMISSION_REVOKE` and `MILESTONE_ADMIN`. `PERMISSION_ADMIN` just grants the user both `PERMISSION_GRANT` and `PERMISSION_REVOKE`, and users with `TRAC_ADMIN` can grant or revoke any permission. 30 29 31 == Available Privileges ==30 == Available Privileges 32 31 33 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. … … 35 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'''): 36 35 37 === Repository Browser ===36 === Repository Browser 38 37 39 38 || `BROWSER_VIEW` || View directory listings in the [wiki:TracBrowser repository browser] || … … 42 41 || `CHANGESET_VIEW` || View [wiki:TracChangeset repository check-ins] || 43 42 44 === Ticket System ===43 === Ticket System 45 44 46 45 || `TICKET_VIEW` || View existing [wiki:TracTickets tickets] and perform [wiki:TracQuery ticket queries] || … … 51 50 || `TICKET_EDIT_CC` || Full modify cc field || 52 51 || `TICKET_EDIT_DESCRIPTION` || Modify description field || 53 || `TICKET_EDIT_COMMENT` || Modify comments||52 || `TICKET_EDIT_COMMENT` || Modify another user's comments. Any user can modify their own comments by default. || 54 53 || `TICKET_BATCH_MODIFY` || [wiki:TracBatchModify Batch modify] tickets || 55 || `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. ||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. || 56 55 57 56 Attention: the "view tickets" button appears with the `REPORT_VIEW` permission. 58 57 59 === Roadmap ===58 === Roadmap 60 59 61 60 || `MILESTONE_VIEW` || View milestones and assign tickets to milestones. || … … 67 66 || `ROADMAP_ADMIN` || to be removed with [trac:#3022 #3022], replaced by MILESTONE_ADMIN || 68 67 69 === Reports ===68 === Reports 70 69 71 70 || `REPORT_VIEW` || View [wiki:TracReports reports], i.e. the "view tickets" link. || … … 76 75 || `REPORT_ADMIN` || All `REPORT_*` permissions || 77 76 78 === Wiki System ===77 === Wiki System 79 78 80 79 || `WIKI_VIEW` || View existing [wiki:TracWiki wiki] pages || … … 85 84 || `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. || 86 85 87 === Permissions ===86 === Permissions 88 87 89 88 || `PERMISSION_GRANT` || add/grant a permission || … … 91 90 || `PERMISSION_ADMIN` || All `PERMISSION_*` permissions || 92 91 93 === Others ===92 === Others 94 93 95 94 || `TIMELINE_VIEW` || View the [wiki:TracTimeline timeline] page || … … 98 97 || `EMAIL_VIEW` || Shows email addresses even if [wiki:TracIni#trac-section trac show_email_addresses] configuration option is false || 99 98 100 == Creating New Privileges ==99 == Creating New Privileges 101 100 102 101 To create custom permissions, for example to be used in a custom workflow, enable the optional [trac:ExtraPermissionsProvider tracopt.perm.config_perm_provider.ExtraPermissionsProvider] component in the "Plugins" admin panel, and add the desired permissions to the `[extra-permissions]` section in your [wiki:TracIni#extra-permissions-section trac.ini]. For more information, please refer to the documentation on the [wiki:TracIni#extra-permissions-section TracIni] page after enabling the component. 103 102 104 == Granting Privileges ==103 == Granting Privileges 105 104 106 105 You grant privileges to users using [wiki:TracAdmin trac-admin]. The current set of privileges can be listed with the following command: … … 124 123 }}} 125 124 126 == Permission Groups ==125 == Permission Groups 127 126 128 127 There are two built-in groups, "authenticated" and "anonymous". … … 146 145 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'''. 147 146 148 == Adding a New Group and Permissions ==147 == Adding a New Group and Permissions 149 148 Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group. 150 149 … … 156 155 }}} 157 156 158 == Removing Permissions ==157 == Removing Permissions 159 158 160 159 Permissions can be removed using the 'remove' command. For example: … … 177 176 }}} 178 177 179 == Default Permissions ==178 == Default Permissions 180 179 181 180 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.
