Roles and Permissions

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	View project's and model's information (name, description, configuration etc.) and data (cases, events, attributes etc.) Open dashboards (queries made by the dashboards are still restricted by the permissions) Run analyses for model and view the analysis results See user's own private filters, all published filters and the model default filter (not allowed to create or modify filters)
EditDashboards	Create, modify and delete dashboards (as a project role, dashboards in the assigned project; as a global role, all dashboards).
Filtering	Save new filters Modify and delete user's own private filters Publish filters for other users (but not set the model default filter). Published filters are still user's own, so other users cannot modify them (except if user has the ManageViews permission).
GenericWrite	Edit model settings (but not possible to create or delete models, or import data to models) Create, modify and delete filters for model
CreateModel (only global)	Create projects, models and data tables. When a project is created, the creator gets project Administrator role for the project (giving full permissions to the project).
DeleteModel	Moving model to recycle bin (deleting) (also ManageProject permission is needed) Delete data tables
ManageViews	View, edit and delete all filters in the model (also other users' private filters)
ManageProject	Modify project information (name and description) (also GenericRead permission is needed)
ManageIntegrations	View, edit and delete data tables (requires also GenericRead permission for the project) Importing data to QPR ProcessAnalyzer models (requires also GenericWrite permission).
ManageReports
ManageOperations	View operations from all users in the QPR ProcessAnalyzer Operation Log Terminate in progress operations run by any user
ManageUsers (only global)	Administrate users and groups, e.g. create new users and groups, and add users to groups.
ManageScripts	As a project role, create, modify and delete scripts in project and model context. As a global role, create, modify and delete all scripts. This permission to be effective requires also the RunScript permission.
RunScripts (only global)	View scripts code and other script properties (with additional restrictions listed below) Run scripts (with additional restrictions listed below) Create, modify and delete scripts that are in user's own context. The rights depend also in which of the following contexts the script is located: project: To view scripts that are in project or model context, user needs to have the GenericRead for the project. model: See above. user: Only the user itself can view, create, modify and delete scripts that are in the user's own context (except users with global ManageScripts permission can see scripts in other users' context). system: All users with RunScripts can see scripts in the system context.

Group Roles

	Group administrator	Member	Hidden Member
Add and remove group members
create users to group
Add and 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

See Also

• Case Level Permissions Control
• Manage Users in QPR ProcessAnalyzer Excel Client
• How to Publish Analysis Results to Others