Changes between Version 2 and Version 3 of TracPermissions


Ignore:
Timestamp:
07/07/13 01:26:40 (6 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracPermissions

    v2 v3  
    44Trac uses a simple, case sensitive, permission system to control what users can and can't access. 
    55 
    6 Permission privileges are managed using the [TracAdmin trac-admin] tool or the ''General / Permissions'' panel in the ''Admin'' web interface. 
     6Permission 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. 
    77 
    88In 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. 
     
    1010Non-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. 
    1111In 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 
     16To access this tab, a user must have one of the following permissions: `TRAC_ADMIN`, `PERMISSION_ADMIN`, `PERMISSION_ADD`, `PERMISSION_REMOVE`. The permissions can granted using the `trac-admin` command (more on `trac-admin` below): 
     17{{{ 
     18  $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN 
     19}}} 
     20 
     21Then, 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). '''Use at least one lowercase character in user names, as all-uppercase names are reserved for permissions.''' 
     22 
     23 1. [[Image(htdocs:../common/guide/admin.png)]] 
     24 1. [[Image(htdocs:../common/guide/admin-permissions.png)]] 
     25 1. [[Image(htdocs:../common/guide/admin-permissions-TICKET_ADMIN.png)]] 
     26 
     27An 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. 
    1228 
    1329== Available Privileges == 
     
    2945|| `TICKET_CREATE` || Create new [wiki:TracTickets tickets] || 
    3046|| `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 || 
    32 || `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets] || 
    33 || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the description field || 
     47|| `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 || 
     48|| `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. || 
     49|| `TICKET_EDIT_CC` || Full modify cc field || 
     50|| `TICKET_EDIT_DESCRIPTION` || Modify description field || 
     51|| `TICKET_EDIT_COMMENT` || Modify comments || 
     52|| `TICKET_BATCH_MODIFY` || [wiki:TracBatchModify Batch modify] tickets || 
     53|| `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. || 
    3454 
    3555Attention: the "view tickets" button appears with the `REPORT_VIEW` permission. 
     
    3757=== Roadmap === 
    3858 
    39 || `MILESTONE_VIEW` || View a milestone || 
     59|| `MILESTONE_VIEW` || View milestones and assign tickets to milestones. || 
    4060|| `MILESTONE_CREATE` || Create a new milestone || 
    4161|| `MILESTONE_MODIFY` || Modify existing milestones || 
    4262|| `MILESTONE_DELETE` || Delete milestones || 
    4363|| `MILESTONE_ADMIN` || All `MILESTONE_*` permissions || 
    44 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see #4292 || 
    45 || `ROADMAP_ADMIN` || to be removed with #3022, replaced by MILESTONE_ADMIN || 
     64|| `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see [trac:#4292 #4292] || 
     65|| `ROADMAP_ADMIN` || to be removed with [trac:#3022 #3022], replaced by MILESTONE_ADMIN || 
    4666 
    4767=== Reports === 
     
    5979|| `WIKI_CREATE` || Create new [wiki:TracWiki wiki] pages || 
    6080|| `WIKI_MODIFY` || Change [wiki:TracWiki wiki] pages || 
     81|| `WIKI_RENAME` || Rename [wiki:TracWiki wiki] pages || 
    6182|| `WIKI_DELETE` || Delete [wiki:TracWiki wiki] pages and attachments || 
    6283|| `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. || 
     
    6889|| `PERMISSION_ADMIN` || All `PERMISSION_*` permissions || 
    6990 
    70  
    7191=== Others === 
    7292 
     
    7494|| `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries || 
    7595|| `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins || 
    76 || `EMAIL_VIEW` || Shows email addresses even if [wiki:0.11/TracIni `trac show_email_addresses` configuration option is `false`] || 
     96|| `EMAIL_VIEW` || Shows email addresses even if [wiki:TracIni#trac-section trac show_email_addresses] configuration option is false || 
     97 
     98== Creating New Privileges == 
     99 
     100To 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 of the component in the admin panel. 
    77101 
    78102== Granting Privileges == 
     
    100124== Permission Groups == 
    101125 
    102 There are two built-in groups, "authenticated" and "anonymous".[[BR]] 
    103 Any user who has not logged in is automatically in the "anonymous" group.[[BR]] 
    104 Any user who has logged in is also in the "authenticated" group.[[BR]] 
    105 The "authenticated" group inherits permissions from the "anonymous" group.[[BR]] 
    106 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. 
     126There are two built-in groups, "authenticated" and "anonymous". 
     127Any user who has not logged in is automatically in the "anonymous" group. 
     128Any user who has logged in is also in the "authenticated" group. 
     129The "authenticated" group inherits permissions from the "anonymous" group. 
     130For example, if the "anonymous" group has permission WIKI_MODIFY,  
     131it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well. 
    107132 
    108133Custom groups may be defined that inherit permissions from the two built-in groups. 
     
    117142}}} 
    118143 
    119 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 is reserved for permissions'''. 
     144Group 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'''. 
    120145 
    121146== Adding a New Group and Permissions == 
     
    155180On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''. 
    156181 
    157  '''anonymous''':: 
     182'''anonymous''' 
     183{{{ 
    158184 BROWSER_VIEW  
    159185 CHANGESET_VIEW  
     
    167193 TICKET_VIEW  
    168194 TIMELINE_VIEW 
    169  WIKI_VIEW  
    170  
    171  '''authenticated''':: 
     195 WIKI_VIEW 
     196}}} 
     197 
     198'''authenticated''' 
     199{{{ 
    172200 TICKET_CREATE  
    173201 TICKET_MODIFY  
    174202 WIKI_CREATE  
    175203 WIKI_MODIFY   
    176  
     204}}} 
    177205---- 
    178206See also: TracAdmin, TracGuide and TracFineGrainedPermissions