Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
72:manage_users_groups_permissions [2019/04/23 13:24] – emr72:manage_users_groups_permissions [2019/04/23 13:28] – emr
Line 3: Line 3:
 You can [[:72:manage_workspaces|manage workspaces]], users, groups and permissions from the administration tab on the left-side menu. You can [[:72:manage_workspaces|manage workspaces]], users, groups and permissions from the administration tab on the left-side menu.
  
-=== Users ===+===== Users =====
  
 Users can be added and settings can be changed from the users section of the administration tab. Users can be added and settings can be changed from the users section of the administration tab.
Line 13: Line 13:
 Adding a user only adds them to the software, not a specific project or workspace. If you want to assign a role to a user, see the [[:72:assign|assign a role]] page Adding a user only adds them to the software, not a specific project or workspace. If you want to assign a role to a user, see the [[:72:assign|assign a role]] page
  
-=== Groups and Permissions ===+===== Groups and Permissions =====
  
 Instead of adding individual users to specific projects, permissions, etc. it is easier to allow groups access. Users can be added to groups and then the entire group can be allowed access or permissions. Instead of adding individual users to specific projects, permissions, etc. it is easier to allow groups access. Users can be added to groups and then the entire group can be allowed access or permissions.
Line 29: Line 29:
 **Workspace** **Workspace**
  
-The workspace attribute allows access to certain workspaces in Stages.+This attribute defines for which workspace or group of workspaces the permission applies to.
  
 **Transitive** **Transitive**
  
-When the transitive attribute is selected, the permission is set for all subsequent modes after.+When the transitive attribute is selected, the permission applies to the whole subtree of workspaces. If it is not selected, the permission only applies to the workspace as defined with the above attribute.
  
 **RMCD** **RMCD**
Line 46: Line 46:
 **Level** **Level**
  
-The level attribute allows specific access on parts of process applications.+The level attribute is only relevant for the Processes domain. It corresponds with the security level of the individual process elements.
  
 **Precedence** **Precedence**
  
-The priority of permissions is decided through the precedence attribute.+This attibute defines the precedence of the permission. The precendence is as follows: 
 + 
 +**High Deny > High Allow > Low Deny > Low Allow**
  
 \\ \\