Precedence
The following table explains the order of authorizations:
Admin |
DeleteFol |
Delete |
WriteFile |
Write |
DelChild |
CreateDoc |
ReadFile |
Read |
NoAuth |
|
|---|---|---|---|---|---|---|---|---|---|---|
User |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
User Group |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
Role |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
HR Object |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
Inherited from parent level |
Same sequence: User –> Group –> Role –> HR Object 41... 42... 43... 44... ... ... ... ... ... ... ... ... ... ... ... 77... 78... 79... 80 |
|||||||||
Inherited from next level |
81... 82... 83... 84... ... ... ... ... ... ... ... ... ... ... ... 117... 118... 119... 120 |
|||||||||
... |
||||||||||
Inherited from top level |
||||||||||
Direct allocation of authorizations at the same level always overrides inherited authorizations, for example, user is stronger than user (inherited)
:
User –> User Group –> Role –> HR Object –>…
Admin –> DeleteFol –> Delete –> WriteFile –> Write –> DelChild –> CreateDoc –> ReadFile –> Read –> NoAuth
Precedence of user over user group
If the user is attached to a document with an access control list (ACL), the ACL overrides the ACL of the same user in the user group.
If the same user is in two user groups and the user groups have different ACLs, the highest level is taken into account.
Example
End of the example.Precedence regarding inheritance
If the ACL of the user is inherited, the ACL of the user in the user group overrides the inherited ACL.
Example
End of the example.