Changes between Version 1 and Version 2 of TracPermissions
- Timestamp:
- Mar 28, 2008, 2:16:35 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracPermissions
v1 v2 2 2 [[TracGuideToc]] 3 3 4 Trac uses a simple permission 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 the ''General / Permissions'' panel in the ''Admin'' web interface. 7 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. 7 9 8 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. 9 10 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". 11 12 12 13 == Available Privileges == 13 14 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 youperform any operation.15 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. 15 16 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):17 Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac ('''note that the privilege names are case-sensitive'''): 17 18 18 19 === Repository Browser === … … 32 33 || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the description field || 33 34 35 Attention: the "view tickets" button appears with the `REPORT_VIEW` permission. 36 34 37 === Roadmap === 35 38 … … 39 42 || `MILESTONE_DELETE` || Delete milestones || 40 43 || `MILESTONE_ADMIN` || All `MILESTONE_*` permissions || 41 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page || 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 || 42 46 43 47 === Reports === 44 48 45 || `REPORT_VIEW` || View [wiki:TracReports reports] ||49 || `REPORT_VIEW` || View [wiki:TracReports reports], i.e. the "view tickets" link. || 46 50 || `REPORT_SQL_VIEW` || View the underlying SQL query of a [wiki:TracReports report] || 47 51 || `REPORT_CREATE` || Create new [wiki:TracReports reports] || … … 58 62 || `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. || 59 63 64 === Permissions === 65 66 || `PERMISSION_GRANT` || add/grant a permission || 67 || `PERMISSION_REVOKE` || remove/revoke a permission || 68 || `PERMISSION_ADMIN` || All `PERMISSION_*` permissions || 69 70 60 71 === Others === 61 72 … … 63 74 || `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries || 64 75 || `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`] || 65 77 66 78 == Granting Privileges == … … 81 93 }}} 82 94 95 Or add all privileges: 96 {{{ 97 $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN 98 }}} 99 83 100 == Permission Groups == 101 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. 107 108 Custom groups may be defined that inherit permissions from the two built-in groups. 84 109 85 110 Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc. … … 92 117 }}} 93 118 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. 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'''. 120 121 == Adding a New Group and Permissions == 122 Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group. 123 124 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) 125 {{{ 126 $ trac-admin /path/to/projenv permission add bob beta_testers 127 $ trac-admin /path/to/projenv permission add beta_testers WIKI_ADMIN 128 129 }}} 95 130 96 131 == Removing Permissions == … … 107 142 You can also remove all privileges for a specific user: 108 143 {{{ 109 $ trac-admin /path/to/projenv permission remove bob *144 $ trac-admin /path/to/projenv permission remove bob '*' 110 145 }}} 111 146 112 147 Or one privilege for all users: 113 148 {{{ 114 $ trac-admin /path/to/projenv permission remove *REPORT_ADMIN149 $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN 115 150 }}} 116 151 117 152 == Default Permissions == 118 153 119 Granting privileges to the special user ''anonymous'' can be used to control what an anonymous user can do before they have logged in. 154 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. 155 On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''. 120 156 121 In the same way, privileges granted to the special user ''authenticated'' will apply to any authenticated (logged in) user. 157 '''anonymous''':: 158 BROWSER_VIEW 159 CHANGESET_VIEW 160 FILE_VIEW 161 LOG_VIEW 162 MILESTONE_VIEW 163 REPORT_SQL_VIEW 164 REPORT_VIEW 165 ROADMAP_VIEW 166 SEARCH_VIEW 167 TICKET_VIEW 168 TIMELINE_VIEW 169 WIKI_VIEW 170 171 '''authenticated''':: 172 TICKET_CREATE 173 TICKET_MODIFY 174 WIKI_CREATE 175 WIKI_MODIFY 122 176 123 177 ---- 124 See also: TracAdmin, TracGuide and [http://trac.edgewall.org/wiki/FineGrainedPermissions FineGrainedPermissions]178 See also: TracAdmin, TracGuide and TracFineGrainedPermissions
