Skip to Content

Changes for page Permissions

Last modified by Sean Hetherington on 2021/09/09 20:55
From version 4.1
edited by colinw
on 2021/09/09 18:01
Change comment: Import
To version 7.1
edited by Sean Hetherington
on 2021/09/09 18:01
Change comment: Import

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +Configuration
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.colinw
1 +XWiki.seanh
Tags
... ... @@ -1,0 +1,1 @@
1 +permission|security|restriction
Content
... ... @@ -9,6 +9,10 @@
9 9  
10 10  Permissions can be defined independently by subject and type, and each permission has a policy and a list of exceptions.
11 11  
12 +//Permissions Toggle Switch//
13 +
14 +[[image:attach:permissions_switch.png]]
15 +
12 12  == Permission Subjects ==
13 13  
14 14  Permission subjects in iSymphony are the users and user groups. When viewing the permissions configuration page in iSymphony, the available subjects are listed on the left side of the screen. When evaluating whether a user is allowed to perform an action in the panel, iSymphony may check multiple subjects:
... ... @@ -51,7 +51,7 @@
51 51  
52 52  === Owned Exception ===
53 53  
54 -A special exception exists, called //Owned//. In some cases, a user "owns" some targets - for example, most users own one or more extensions. If the //Owned// exception appears in the list of exceptions, this has the same effect as if the owned targets each appeared individually. For example, if Albert owned extensions 1001 and 1010, and a permission is defined for Albert as //Deny// with //Owned// in the exceptions list, then Albert will still be able to perform that action on extensions 1001 and 1010. Note also that if a third extension is added to Albert, say, 1020, that Albert would automatically be allowed to perform that action on extension 1020 without having to update the permission settings.
58 +A special exception exists, called //Owned by User//. In some cases, a user "owns" some targets - for example, most users own one or more extensions. If the //Owned by User// exception appears in the list of exceptions, this has the same effect as if the owned targets each appeared individually. For example, if Albert owned extensions 1001 and 1010, and a permission is defined for Albert as //Deny// with //Owned by User// in the exceptions list, then Albert will still be able to perform that action on extensions 1001 and 1010. Note also that if a third extension is added to Albert, say, 1020, that Albert would automatically be allowed to perform that action on extension 1020 without having to update the permission settings.
55 55  
56 56  = Editing permissions =
57 57  
permissions_switch
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +26.5 KB
Content
permissions_switch.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +26.5 KB
Content