Changes between Version 1 and Version 2 of TracPermissions
- Timestamp:
- 12/04/2008 10:19:05 PM (16 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, case sensitive, permission system to control what users can and can't access. 5 5 6 Permission privileges are managed using the [ wiki:TracAdmin trac-admin] tool.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. 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 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 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 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 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 13 == Graphical Admin Tab == 14 ''This feature is new in version 0.11.'' 15 16 To 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 21 Then, 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 14 23 15 24 == Available Privileges == 16 25 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.26 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. 18 27 19 Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac :28 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 29 21 30 === Repository Browser === … … 31 40 || `TICKET_CREATE` || Create new [wiki:TracTickets tickets] || 32 41 || `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] || 33 || `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties ||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 || 34 43 || `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. || 44 || `TICKET_EDIT_CC` || Full modify cc field || 45 || `TICKET_EDIT_DESCRIPTION` || Modify description field || 46 || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the description field || 47 48 Attention: the "view tickets" button appears with the `REPORT_VIEW` permission. 36 49 37 50 === Roadmap === … … 42 55 || `MILESTONE_DELETE` || Delete milestones || 43 56 || `MILESTONE_ADMIN` || All `MILESTONE_*` permissions || 44 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page ||45 || `ROADMAP_ADMIN` || Alias for `MILESTONE_ADMIN` (deprecated)||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 || 46 59 47 60 === Reports === 48 61 49 || `REPORT_VIEW` || View [wiki:TracReports reports] ||62 || `REPORT_VIEW` || View [wiki:TracReports reports], i.e. the "view tickets" link. || 50 63 || `REPORT_SQL_VIEW` || View the underlying SQL query of a [wiki:TracReports report] || 51 64 || `REPORT_CREATE` || Create new [wiki:TracReports reports] || … … 62 75 || `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. || 63 76 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 64 84 === Others === 65 85 … … 67 87 || `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries || 68 88 || `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`] || 69 90 70 91 == Granting Privileges == 71 92 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:93 You grant privileges to users using [wiki:TracAdmin trac-admin]. The current set of privileges can be listed with the following command: 73 94 {{{ 74 95 $ trac-admin /path/to/projenv permission list … … 80 101 }}} 81 102 103 The `permission add` command also accepts multiple privilege names: 104 {{{ 105 $ trac-admin /path/to/projenv permission add bob REPORT_DELETE WIKI_CREATE 106 }}} 107 108 Or add all privileges: 109 {{{ 110 $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN 111 }}} 112 82 113 == Permission Groups == 114 115 There are two built-in groups, "authenticated" and "anonymous".[[BR]] 116 Any user who has not logged in is automatically in the "anonymous" group.[[BR]] 117 Any user who has logged in is also in the "authenticated" group.[[BR]] 118 The "authenticated" group inherits permissions from the "anonymous" group.[[BR]] 119 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. 120 121 Custom groups may be defined that inherit permissions from the two built-in groups. 83 122 84 123 Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc. … … 91 130 }}} 92 131 132 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'''. 133 134 == Adding a New Group and Permissions == 135 Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group. 136 137 The 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 }}} 143 144 == Removing Permissions == 145 146 Permissions can be removed using the 'remove' command. For example: 147 148 This command will prevent the user ''bob'' from deleting reports: 149 {{{ 150 $ trac-admin /path/to/projenv permission remove bob REPORT_DELETE 151 }}} 152 153 Just like `permission add`, this command accepts multiple privilege names. 154 155 You can also remove all privileges for a specific user: 156 {{{ 157 $ trac-admin /path/to/projenv permission remove bob '*' 158 }}} 159 160 Or one privilege for all users: 161 {{{ 162 $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN 163 }}} 164 93 165 == Default Permissions == 94 166 95 Granting privileges to the special user ''anonymous'' can be used to control what an anonymous user can do before they have logged in. 167 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. 168 On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''. 96 169 97 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 98 189 99 190 ---- 100 See also: TracAdmin, TracGuide 191 See also: TracAdmin, TracGuide and TracFineGrainedPermissions
