Changes between Version 2 and Version 3 of TracPermissions


Ignore:
Timestamp:
07/14/08 16:31:15 (6 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracPermissions

    v2 v3  
    22[[TracGuideToc]] 
    33 
    4 Trac uses a simple but flexible permission system to control what users can and can't access. 
     4Trac uses a simple permission system to control what users can and can't access. 
    55 
    66Permission privileges are managed using the [wiki:TracAdmin trac-admin] tool. 
    77 
    8 Regular visitors, non-authenticated users, accessing the system are assigned the default  
    9 role (''user'') named {{{anonymous}}}.  
    10 Assign permissions to the {{{anonymous}}} user to set privileges for non-authenticated/guest users. 
     8Non-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. 
    119 
    12 In addition to these privileges users can be granted additional individual  
    13 rights in effect when authenticated and logged into the system. 
     10In 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". 
    1411 
    1512== Available Privileges == 
    1613 
    17 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 let you do anything you want. 
     14To 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. 
    1815 
    19 Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac: 
     16Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac (note that the privilege names are case-sensitive): 
    2017 
    2118=== Repository Browser === 
     
    3128|| `TICKET_CREATE` || Create new [wiki:TracTickets tickets] || 
    3229|| `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] || 
    33 || `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties || 
     30|| `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties (priority, assignment, keywords, etc.) except description field || 
    3431|| `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets] || 
    35 || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments. || 
     32|| `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the description field || 
    3633 
    3734=== Roadmap === 
     
    4340|| `MILESTONE_ADMIN` || All `MILESTONE_*` permissions || 
    4441|| `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page || 
    45 || `ROADMAP_ADMIN` || Alias for `MILESTONE_ADMIN` (deprecated) || 
    4642 
    4743=== Reports === 
     
    7066== Granting Privileges == 
    7167 
    72 Currently the only way to grant privileges to users is by using the `trac-admin` script. The current set of privileges can be listed with the following command: 
     68You grant privileges to users using [wiki:TracAdmin trac-admin]. The current set of privileges can be listed with the following command: 
    7369{{{ 
    7470  $ trac-admin /path/to/projenv permission list 
     
    7874{{{ 
    7975  $ trac-admin /path/to/projenv permission add bob REPORT_DELETE 
     76}}} 
     77 
     78The `permission add` command also accepts multiple privilege names: 
     79{{{ 
     80  $ trac-admin /path/to/projenv permission add bob REPORT_DELETE WIKI_CREATE 
    8081}}} 
    8182 
     
    9192}}} 
    9293 
     94Group 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. 
     95 
     96== Removing Permissions == 
     97 
     98Permissions can be removed using the 'remove' command. For example: 
     99 
     100This command will prevent the user ''bob'' from deleting reports: 
     101{{{ 
     102  $ trac-admin /path/to/projenv permission remove bob REPORT_DELETE 
     103}}} 
     104 
     105Just like `permission add`, this command accepts multiple privilege names. 
     106 
     107You can also remove all privileges for a specific user: 
     108{{{ 
     109  $ trac-admin /path/to/projenv permission remove bob * 
     110}}} 
     111 
     112Or one privilege for all users: 
     113{{{ 
     114  $ trac-admin /path/to/projenv permission remove * REPORT_ADMIN 
     115}}} 
     116 
    93117== Default Permissions == 
    94118 
     
    98122 
    99123---- 
    100 See also: TracAdmin, TracGuide 
     124See also: TracAdmin, TracGuide and [http://trac.edgewall.org/wiki/FineGrainedPermissions FineGrainedPermissions]