Changes between Version 1 and Version 2 of TracPermissions
- Timestamp:
- Jul 30, 2012 5:33:42 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracPermissions
v1 v2 19 19 }}} 20 20 21 Then, the user `bob` 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 21 Then, the user `bob` 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). '''Use at least one lowercase character in user names, as all-uppercase names are reserved for permissions.''' 22 23 1. [[Image(htdocs:../common/guide/admin.png)]] 24 1. [[Image(htdocs:../common/guide/admin-permissions.png)]] 25 1. [[Image(htdocs:../common/guide/admin-permissions-TICKET_ADMIN.png)]] 23 26 24 27 An easy way to quickly secure a new Trac install is to run the above command on the anonymous user, install the [http://trac-hacks.org/wiki/AccountManagerPlugin AccountManagerPlugin], create a new admin account graphically and then remove the TRAC_ADMIN permission from the anonymous user. … … 46 49 || `TICKET_EDIT_CC` || Full modify cc field || 47 50 || `TICKET_EDIT_DESCRIPTION` || Modify description field || 51 || `TICKET_EDIT_COMMENT` || Modify comments || 48 52 || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the reporter and description fields. It also allows managing ticket properties in the WebAdmin panel. || 49 53 … … 74 78 || `WIKI_CREATE` || Create new [wiki:TracWiki wiki] pages || 75 79 || `WIKI_MODIFY` || Change [wiki:TracWiki wiki] pages || 80 || `WIKI_RENAME` || Rename [wiki:TracWiki wiki] pages || 76 81 || `WIKI_DELETE` || Delete [wiki:TracWiki wiki] pages and attachments || 77 82 || `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. || … … 82 87 || `PERMISSION_REVOKE` || remove/revoke a permission || 83 88 || `PERMISSION_ADMIN` || All `PERMISSION_*` permissions || 84 85 89 86 90 === Others === … … 91 95 || `EMAIL_VIEW` || Shows email addresses even if [trac:wiki:0.11/TracIni trac show_email_addresses configuration option is false] || 92 96 97 == Creating New Privileges == 98 99 To create custom permissions, for example to be used in a custom workflow, enable the optional [trac:ExtraPermissionsProvider tracopt.perm.config_perm_provider.ExtraPermissionsProvider] component in the "Plugins" admin panel, and add the desired permissions to the `[extra-permissions]` section in your [wiki:TracIni#extra-permissions-section trac.ini]. For more information, please refer to the documentation of the component in the admin panel. 100 93 101 == Granting Privileges == 94 102 … … 115 123 == Permission Groups == 116 124 117 There are two built-in groups, "authenticated" and "anonymous".[[BR]] 118 Any user who has not logged in is automatically in the "anonymous" group.[[BR]] 119 Any user who has logged in is also in the "authenticated" group.[[BR]] 120 The "authenticated" group inherits permissions from the "anonymous" group.[[BR]] 121 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. 125 There are two built-in groups, "authenticated" and "anonymous". 126 Any user who has not logged in is automatically in the "anonymous" group. 127 Any user who has logged in is also in the "authenticated" group. 128 The "authenticated" group inherits permissions from the "anonymous" group. 129 For example, if the "anonymous" group has permission WIKI_MODIFY, 130 it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well. 122 131 123 132 Custom groups may be defined that inherit permissions from the two built-in groups. … … 132 141 }}} 133 142 134 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 isreserved for permissions'''.143 Group membership can be checked by doing a {{{permission list}}} with no further arguments; the resulting output will include group memberships. '''Use at least one lowercase character in group names, as all-uppercase names are reserved for permissions'''. 135 144 136 145 == Adding a New Group and Permissions ==
