Roles and Permissions: Difference between revisions
No edit summary |
|||
Line 57: | Line 57: | ||
||ManageIntegrations|| | ||ManageIntegrations|| | ||
* View, edit and delete data tables (requires also ''GenericRead'' permission for the project) | * View, edit and delete data tables (requires also ''GenericRead'' permission for the project) | ||
* Import data to model (requires also ''GenericWrite'' permission). There may be model specific restrictions for maximum number of events, case attributes and event attributes. These restrictions are ignored for users having global CreateModel permission with no limits | * Import data to model (requires also ''GenericWrite'' permission). There may be model specific restrictions for maximum number of events, case attributes and event attributes. These restrictions are ignored for users having global CreateModel permission with no limits. | ||
||[[File:Tick.gif|center]]|| || ||[[File:Tick.gif|center]]|| || || | ||[[File:Tick.gif|center]]|| || ||[[File:Tick.gif|center]]|| || || | ||
|- | |- |
Revision as of 14:27, 31 October 2019
QPR ProcessAnalyzer has a role-based access control, where all operations require appropriate rights in order to be executable. rights are given to users and user groups by assigning users or groups to roles, where roles are a collection of permissions. Permissions are fixed in QPR ProcessAnalyzer and there is a fixed list of operations behind a permission what user can do. Roles can be bound either to projects or be global, which means that that role (and its permissions) is applicable for all the contents in the system. Users belonging to a user group, have always all the roles assigned to that user group.
Global and Project Roles
There are two types of roles in QPR ProcessAnalyzer:
- Global roles are used to give rights in the entire QPR ProcessAnalyzer environment.
- Project roles are used to give rights in a certain project. When assigning projects roles, the project needs to be defined.
When using the Manage Users dialog, global roles are assigned when <All> is selected from the project list. Projects roles are assigned, when a project is selected in the list.
By default, QPR ProcessAnalyzer environment contains global and project roles that are shown in the following table (roles are as columns). The roles have been mapped to certain permissions that are also shown in the following table (permissions are as rows). It's possible to create new roles in QPR ProcessAnalyzer.
Global roles | Project roles | |||||||
---|---|---|---|---|---|---|---|---|
Permission | Allowed operations | Administrator | ModelCreator | RunScripts | Administrator | Designer | Analyzer | Viewer |
GenericRead |
|
|||||||
EditDashboards |
Note: This feature hasn't been released yet.
|
|||||||
Filtering |
|
|||||||
GenericWrite |
|
|||||||
CreateModel (only global) |
|
|||||||
DeleteModel |
|
|||||||
ManageViews |
|
|||||||
ManageProject |
|
|||||||
ManageIntegrations |
|
|||||||
ManageReports | ||||||||
ManageOperations |
|
|||||||
ManageUsers (only global) |
|
|||||||
ManageScripts |
This permission to be effective requires also the RunScript permission. |
|||||||
RunScripts (only global) |
The rights depend also in which of the following contexts the script is located:
|
Notes:
- ModelCreator role will get the project Administrator role for the projects that they create, giving full rights for the created projects.
- Users with global Administrator or ModelCreator role can always import new data into any model without restrictions. Note, however, that a user cannot import more data than what is allowed by the product activation limits.
Group Roles
Administrator (Group) | Member | Hidden Member | |
---|---|---|---|
Add/Remove Group Members | |||
Create Users to Group | |||
Add/Remove Project Access Rights of a User | |||
Open Model Accessible to Group Members | |||
See Unhidden Group Members | |||
See Hidden Group Members |
If a group member is a project Administrator, the user can add and remove project specific access rights for the group or for any individual member of the project.
Scripting Permissions
For viewing script definitions and running scripts, global RunScripts permission is needed. All scripts linked to the current context are available provided that the current user has permission to see the scripts in the context. The required permissions by context are:
- System context: No additional requirements.
- Project context: GenericRead permission for the project.
- Model context: GenericRead permission for the project of the model.
- User context: If the script is linked to current user, then no additional requirements. If the script is linked to a group the current user belongs to, no additional requirements. If the script is linked to other users or user groups, global ManageScripts permission is required.
For script creation, modification, deletion and export, the following permissions are needed depending on the script context:
- System context: Global ManageScripts and RunScripts
- Project context: project ManageScripts and global RunScripts
- Model context: project ManageScripts and global RunScripts
- User context: Global RunScripts and if the script is linked to a user group the user belongs to, GroupAdministrator user group role is required.
If Hide Script Details is set for the script, only users with modify permissions for the script can see the script code and log.
Importing Data Permissions
Data can be imported into a data table with project GenericWrite and ManageIntegrations permissions. CreateModel permission is required if the user is overwriting existing data in the data table, i.e. not appending. User may never import more data than is allowed by product's activation. Data table specific data quotas are ignored for users that have unrestricted global CreateModel permission. Users that have restricted global CreateModel permission or users that don't have any global CreateModel permission may only import the amount of data into a data table specified in data table's own restrictions.
Permissions for Other Operations
- Add a model into project: CreateModel permission for the target project. Model is moved into target project and all old permissions are replaced by the permissions for the target project.
- Create a new model into existing project: Global CreateModel and CreateModel permission for the target project
- Move a model from a project to another: GenericWrite and DeleteModel permissions for the source project and CreateModel permission for the target project
- Restoring a project from recycle bin: Global GenericRead, CreateModel and ManageProject permissions
- Deleting a project from the database: Global DeleteModel permission and ManageProject permission for the project
- Creating a copy of a project: Global CreateModel permission and GenericRead and ManageProject permissions for the project