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 revision		Previous revision
76:users_groups_permissions [2021/02/23 14:00] – emr76:users_groups_permissions [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 4: Line 4:
  
   * ''Participant-to-User Group Assignments'': assign participants to user groups   * ''Participant-to-User Group Assignments'': assign participants to user groups
-  * ''Process Execution'':+  * ''Process Execution'': start project processes and execute them in tools like Jira
   * ''Process Execution Configuration'': control edit access to process execution elements and configuration   * ''Process Execution Configuration'': control edit access to process execution elements and configuration
   * ''Process Participant Assignments'': assign users to participants   * ''Process Participant Assignments'': assign users to participants
Line 13: Line 13:
   * ''Role-to-User Group Assignments'': assign roles to user groups   * ''Role-to-User Group Assignments'': assign roles to user groups
   * ''User-to-Role Assignments'': assign users to roles   * ''User-to-Role Assignments'': assign users to roles
-A detailed guidance for the various user actions and which permissions they require can be found in this {{:76:permissions_matrix_7.6.xlsx|permission matrix}}.+A detailed guidance for the various user actions and which permissions they require can be found in this {{:76:permissions_matrix_7.6.xlsx|Permissions Matrix}}.
  
-The dependencies between permissions and licenses needed can be found in the [[:76:stages-permission-license-matrix|Stages Permission-License matrix]].+The dependencies between permissions and licenses needed can be found in the [[:76:stages-permission-license-matrix|]].
  
 ===== Manage User Access through Groups ===== ===== Manage User Access through Groups =====
  
-This approach is best used for access permissions to workspaces that exist only once, e.g. the modeling area, reference models, or standard processes.+This approach is best used for access permissions to workspaces that exist only once, e.g. the standard processes and the reference models. 
 + 
 +===== Manage User Access through Participants ===== 
 + 
 +Participants are users that participate in the lifecycle of a process, e.g. modeling, review, approval, or tailoring. This approach is best used for access permissions to workspaces that exist multiple times for specific purposes, e.g. modeling workspaces, playgrounds, or project- or program-specific processes. Example participants: process owner, process modeler, process reviewer, process approver, tailoring approver.
  
 ===== Manage User Access through Roles ===== ===== Manage User Access through Roles =====
  
-This approach is best used for access permissions to workspaces that exist many times, typically project- or program-specific processes.+This approach is best used for access permissions to workspaces that exist many times, e.g. project- or program-specific processes, but the users do not participate in the management of the process. Example roles: engineer, tester, quality manager. Project managers are typically responsible for their project's specific process and therefore can be added as process owner participants (see above).
  
 =====   ===== =====   =====