The roles are Admin, Owner, Operator and Guest which are hard-coded in the system.
So, these values must NOT be changed. When user is granted administrative (ie full)
role, the user will have DEAR permission set (ie D = Delete, E = Edit, A = Add and
R = Read) on the resource or genus.
System Roles of Katmandoo
|
System Role |
Role Power |
Permission |
Role Description |
|
Admin |
4 |
DELETE |
User will have all the permission to the selected system resource ie ?DEAR?. |
|
Owner |
3 |
EDIT |
User will have just EAR permission to the selected system resource. |
|
Operator |
2 |
ADD |
User will be able to ADD and (of course) READ permission to the selected system
resource. |
|
Guest |
1 |
READ |
User will have just READ only permission to the selected system resource. |
|
None |
0 |
(none) |
User will NOT have any permission on the selected system resource |
|
Column Name |
Description |
|
RoleId |
Identification Number that uniquely identifies a role that can granted on a System
Resource. (PK) |
|
RoleName (AK) |
Name that uniquely identifies a role. (AK) |
|
RolePower* |
4 = Delete, 3 - Edit, 2 = Add, 1 = Read and 0 = None |
*RolePower is used to find the most powerful role that user has on a System Resource.
Please note than a user can have multiple role on a System Resource through multiple
groups it is associated with. For example, if a user has
Owner
and
Guest role on
Site
table through different System groups, then system will take only the
Owner role (using the RolePower) because when
user has
Owner role, then s/he implicitly
also has
Operator and
Guest
roles as well!