Changes between Version 1 and Version 2 of TracPermissions


Ignore:
Timestamp:
12/05/08 11:32:01 (5 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracPermissions

    v1 v2  
    22[[TracGuideToc]] 
    33 
    4 Trac uses a simple permission system to control what users can and can't access. 
     4Trac uses a simple, case sensitive, permission system to control what users can and can't access. 
    55 
    6 Permission privileges are managed using the [wiki:TracAdmin trac-admin] tool. 
     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. 
     7 
     8In 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. 
    79 
    810Non-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. 
     11In 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". 
    912 
    10 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". 
     13== Graphical Admin Tab == 
     14''This feature is new in version 0.11.'' 
     15 
     16To access this tab, a user must have `TRAC_ADMIN privileges`. This can be performed as follows (more on the trac-admin script below): 
     17{{{ 
     18  $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN 
     19}}} 
     20 
     21Then, 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). 
     22 
    1123 
    1224== Available Privileges == 
    1325 
    14 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 perform any operation. 
     26To 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. 
    1527 
    16 Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac (note that the privilege names are case-sensitive): 
     28Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac ('''note that the privilege names are case-sensitive'''): 
    1729 
    1830=== Repository Browser === 
     
    2840|| `TICKET_CREATE` || Create new [wiki:TracTickets tickets] || 
    2941|| `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] || 
    30 || `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties (priority, assignment, keywords, etc.) except description field || 
     42|| `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties (priority, assignment, keywords, etc.) except description field, cc field add/remove when logged in or set email to pref || 
    3143|| `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets] || 
     44|| `TICKET_EDIT_CC` || Full modify cc field || 
     45|| `TICKET_EDIT_DESCRIPTION` || Modify description field || 
    3246|| `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the description field || 
     47 
     48Attention: the "view tickets" button appears with the `REPORT_VIEW` permission. 
    3349 
    3450=== Roadmap === 
     
    3955|| `MILESTONE_DELETE` || Delete milestones || 
    4056|| `MILESTONE_ADMIN` || All `MILESTONE_*` permissions || 
    41 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page || 
     57|| `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see #4292 || 
     58|| `ROADMAP_ADMIN` || to be removed with #3022, replaced by MILESTONE_ADMIN || 
    4259 
    4360=== Reports === 
    4461 
    45 || `REPORT_VIEW` || View [wiki:TracReports reports] || 
     62|| `REPORT_VIEW` || View [wiki:TracReports reports], i.e. the "view tickets" link. || 
    4663|| `REPORT_SQL_VIEW` || View the underlying SQL query of a [wiki:TracReports report] || 
    4764|| `REPORT_CREATE` || Create new [wiki:TracReports reports] || 
     
    5875|| `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. || 
    5976 
     77=== Permissions === 
     78 
     79|| `PERMISSION_GRANT` || add/grant a permission || 
     80|| `PERMISSION_REVOKE` || remove/revoke a permission || 
     81|| `PERMISSION_ADMIN` || All `PERMISSION_*` permissions || 
     82 
     83 
    6084=== Others === 
    6185 
     
    6387|| `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries || 
    6488|| `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins || 
     89|| `EMAIL_VIEW` || Shows email addresses even if [wiki:0.11/TracIni `trac show_email_addresses` configuration option is `false`] || 
    6590 
    6691== Granting Privileges == 
     
    81106}}} 
    82107 
     108Or add all privileges: 
     109{{{ 
     110  $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN 
     111}}} 
     112 
    83113== Permission Groups == 
     114 
     115There are two built-in groups, "authenticated" and "anonymous".[[BR]] 
     116Any user who has not logged in is automatically in the "anonymous" group.[[BR]] 
     117Any user who has logged in is also in the "authenticated" group.[[BR]] 
     118The "authenticated" group inherits permissions from the "anonymous" group.[[BR]] 
     119eg. if the "anonymous" group has permission WIKI_MODIFY, it's not necessary to add the WIKI_MODIFY permisison to the "authenticated" group as well. 
     120 
     121Custom groups may be defined that inherit permissions from the two built-in groups. 
    84122 
    85123Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc. 
     
    92130}}} 
    93131 
    94 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. 
     132Group 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'''. 
     133 
     134== Adding a New Group and Permissions == 
     135Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group. 
     136 
     137The 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) 
     138{{{  
     139   $ trac-admin /path/to/projenv permission add bob beta_testers 
     140   $ trac-admin /path/to/projenv permission add beta_testers WIKI_ADMIN 
     141 
     142}}} 
    95143 
    96144== Removing Permissions == 
     
    107155You can also remove all privileges for a specific user: 
    108156{{{ 
    109   $ trac-admin /path/to/projenv permission remove bob * 
     157  $ trac-admin /path/to/projenv permission remove bob '*' 
    110158}}} 
    111159 
    112160Or one privilege for all users: 
    113161{{{ 
    114   $ trac-admin /path/to/projenv permission remove * REPORT_ADMIN 
     162  $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN 
    115163}}} 
    116164 
    117165== Default Permissions == 
    118166 
    119 Granting privileges to the special user ''anonymous'' can be used to control what an anonymous user can do before they have logged in. 
     167By 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. 
     168On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''. 
    120169 
    121 In the same way, privileges granted to the special user ''authenticated'' will apply to any authenticated (logged in) user. 
     170 '''anonymous''':: 
     171 BROWSER_VIEW  
     172 CHANGESET_VIEW  
     173 FILE_VIEW  
     174 LOG_VIEW  
     175 MILESTONE_VIEW  
     176 REPORT_SQL_VIEW  
     177 REPORT_VIEW  
     178 ROADMAP_VIEW  
     179 SEARCH_VIEW  
     180 TICKET_VIEW  
     181 TIMELINE_VIEW 
     182 WIKI_VIEW  
     183 
     184 '''authenticated''':: 
     185 TICKET_CREATE  
     186 TICKET_MODIFY  
     187 WIKI_CREATE  
     188 WIKI_MODIFY   
    122189 
    123190---- 
    124 See also: TracAdmin, TracGuide and [http://trac.edgewall.org/wiki/FineGrainedPermissions FineGrainedPermissions] 
     191See also: TracAdmin, TracGuide and TracFineGrainedPermissions