Edgewall Software

Changes between Version 102 and Version 103 of TracPermissions


Ignore:
Timestamp:
Mar 22, 2017, 8:39:19 AM (2 years ago)
Author:
Ryan J Ollos
Comment:

Minor edits.

Legend:

Unmodified
Added
Removed
Modified
  • TracPermissions

    v102 v103  
    88In 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 [TracIni#trac-permission_policies-option "[trac] permission_policies"]. See TracFineGrainedPermissions for more details.
    99
    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 privilege 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".
     10Non-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 privilege for will not be displayed in the navigation.
     11In 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//.
    1212
    1313== Graphical Admin Tab
     
    119119== Permission Groups
    120120
    121 There are two built-in groups, "authenticated" and "anonymous".
    122 Any user who has not logged in is automatically in the "anonymous" group.
    123 Any user who has logged in is also in the "authenticated" group.
    124 The "authenticated" group inherits permissions from the "anonymous" group.
    125 For example, if the "anonymous" group has permission WIKI_MODIFY,
    126 it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well.
     121There are two built-in groups, //authenticated// and //anonymous//.
     122Any user who has not logged in is automatically in the //anonymous// group.
     123Any user who has logged in is also in the //authenticated// group.
     124The //authenticated// group inherits permissions from the //anonymous// group.
     125For example, if the //anonymous// group has permission WIKI_MODIFY,
     126it is not necessary to add the WIKI_MODIFY permission to the //authenticated// group as well.
    127127
    128128Custom groups may be defined that inherit permissions from the two built-in groups.
     
    175175== Default Permissions
    176176
    177 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.
    178 On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''.
    179 
    180 '''anonymous'''
     177By 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.
     178On the other hand, the //authenticated// users will have the permissions to ''create and modify tickets and wiki pages''.
     179
     180//**anonymous**//
    181181{{{
    182182BROWSER_VIEW
     
    194194}}}
    195195
    196 '''authenticated'''
     196//**authenticated**//
    197197{{{
    198198TICKET_CREATE
     
    202202}}}
    203203----
    204 See also: TracAdmin, TracGuide and TracFineGrainedPermissions
     204See also: TracAdmin, TracFineGrainedPermissions