Changes between Version 1 and Version 2 of TracPermissions
- Timestamp:
- Apr 22, 2008, 10:09:23 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracPermissions
v1 v2 2 2 [[TracGuideToc]] 3 3 4 Trac uses a simple but flexiblepermission system to control what users can and can't access.4 Trac uses a simple permission system to control what users can and can't access. 5 5 6 6 Permission privileges are managed using the [wiki:TracAdmin trac-admin] tool. 7 7 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. 8 Non-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. 11 9 12 In addition to these privileges users can be granted additional individual 13 rights in effect when authenticated and logged into the system. 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". 14 11 15 12 == Available Privileges == 16 13 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.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. 18 15 19 Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac :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): 20 17 21 18 === Repository Browser === … … 31 28 || `TICKET_CREATE` || Create new [wiki:TracTickets tickets] || 32 29 || `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 || 34 31 || `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 || 36 33 37 34 === Roadmap === … … 43 40 || `MILESTONE_ADMIN` || All `MILESTONE_*` permissions || 44 41 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page || 45 || `ROADMAP_ADMIN` || Alias for `MILESTONE_ADMIN` (deprecated) ||46 42 47 43 === Reports === … … 70 66 == Granting Privileges == 71 67 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:68 You grant privileges to users using [wiki:TracAdmin trac-admin]. The current set of privileges can be listed with the following command: 73 69 {{{ 74 70 $ trac-admin /path/to/projenv permission list … … 78 74 {{{ 79 75 $ trac-admin /path/to/projenv permission add bob REPORT_DELETE 76 }}} 77 78 The `permission add` command also accepts multiple privilege names: 79 {{{ 80 $ trac-admin /path/to/projenv permission add bob REPORT_DELETE WIKI_CREATE 80 81 }}} 81 82 … … 91 92 }}} 92 93 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. 95 96 == Removing Permissions == 97 98 Permissions can be removed using the 'remove' command. For example: 99 100 This command will prevent the user ''bob'' from deleting reports: 101 {{{ 102 $ trac-admin /path/to/projenv permission remove bob REPORT_DELETE 103 }}} 104 105 Just like `permission add`, this command accepts multiple privilege names. 106 107 You can also remove all privileges for a specific user: 108 {{{ 109 $ trac-admin /path/to/projenv permission remove bob * 110 }}} 111 112 Or one privilege for all users: 113 {{{ 114 $ trac-admin /path/to/projenv permission remove * REPORT_ADMIN 115 }}} 116 93 117 == Default Permissions == 94 118 … … 98 122 99 123 ---- 100 See also: TracAdmin, TracGuide 124 See also: TracAdmin, TracGuide and [http://trac.edgewall.org/wiki/FineGrainedPermissions FineGrainedPermissions]
