Roles and Permissions in QPR ProcessAnalyzer

From QPR ProcessAnalyzer Wiki
Jump to: navigation, search

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 groups by assigning roles to them. Roles are a collection of permissions. Permissions are fixed in QPR ProcessAnalyzer allowing certain operations to be done. Some roles are project-specific meaning that that role (and its permissions) is applicable only for that project. Roles can also be global which gives rights to all projects in the system. Users belonging to a group, have all the roles assigned to that 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 system.
  • Project roles are used to give rights in a certain project. When assigning projects roles, the project is also defined.

By default, QPR ProcessAnalyzer system 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 Create models SQL Scripting Administrator Designer Analyzer Viewer
View dashboards
  • View project's and model's information (name, description, configuration etc.)
  • List datatables and view their contents
  • Open dashboards (queries made by the dashboards are still restricted by the permissions)
  • Run analyses for model and view the analysis results
  • See own private filters, all published filters and the model default filter (not allowed to create/modify/delete filters)
Save filters
  • Create, modify and delete own filters (private and public, but not model default)
  • Publish own private filters for other users (but not set the model default filter). Published filters are still user's own, so other users cannot modify them.
Design dashboards
  • Create, modify and delete dashboards (as a project role, dashboards in the assigned project; as a global role, all dashboards).
Import data
  • Edit model settings (but not possible to create or delete models)
  • Import data to datatables (either directly or import to a model which uses datatables)
Manage filters
  • View, create, modify and delete all filters in the model (also other users' private filters).
  • Set the model default filter.
Manage project
  • Modify project information (name and description) (also GenericRead permission is needed)
Delete models

As a project specific permission:

  • Moving model to recycle bin (soft deleting) (also project specific ManageProject permission is needed)
  • Delete datatables (for datatables deletion is always permanent)

As a global permission:

  • Permanently deleting models and projects (remove from the recycle bin) (also global ManageProject permission is needed)
Manage scrips
  • 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.

Manage operations
Manage users
  • Administrate users and groups, e.g. create new users and groups, and add users to groups.
Create model
  • Create projects, models and datatables. When a project is created, the creator gets project Administrator role for the project (giving full permissions to the project).
SQL scripting
  • 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.

Datatable Permission

Permissions required for datatables:

  • List datatables, view datatable properties and data contents: GenericRead for the project.
  • Create datatables: GenericWrite for the project.
  • Change datatable properties and import data to datatable: GenericWrite for the project.
  • Move datatables between projects: GenericWrite and DeleteModel to source project and GenericWrite for target project.
  • Delete datatable: DeleteModel for 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.

Permissions for Other Operations

  • Move a model from a project to another: GenericWrite and DeleteModel permissions for the source project and CreateModel permission for the target project
  • Creating a copy of a project: Global CreateModel permission and GenericRead and ManageProject permissions for the 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
  • It's not possible to create project without global CreateModel permission
  • It's not possible to delete project without DeleteModel and ManageProject permission for the project
  • It's not possible to rename a project without ManageProject permission
  • It's not possible to move a project to another without ManageProject permission for moving project and GenericRead for source project and GenericRead + CreateModel for target project.
  • It's not possible to move a dashboard to another project without EditDashboards permission for both the source and target project.

Group Roles

Group administrator Normal 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.