Permissions Detail

Permissions controlling access to functionality in the Ovation LIMS can be held at one of three access levels: Read, Write and Admin. Each level is inclusive of the previous: Admin access confers the access defined for Write access; Write access confers the access defined for Read.

Functional permissions sometimes pertain to information that is held within a project (requisitions, samples ...). In those cases, the user must have that permission through a role granted to them at the organization level and also be added to the project's user list. In this context, the role in the project user list does not matter.

Roles on the project user list do matter for one thing: results report signing. Requisitions can be configured to require that results reports are signed by a user with a certain role (or by multiple users with different roles). In this context, the role granted to the user on the project is considered.

Permissions controlling access to documents work differently (as described in Documentation Permissions below).

Note: The role called "Admin" confers certain access to users, even if they do not have the otherwise required permission. These exceptions are listed in Administration Permissions below.

The implication of granting each available permission is defined below according to the category of the permission:

• Administration Permissions
• Analytics Permissions
• Biobanking Permissions
• Configuration Permissions
• Document Permissions
• Inventory Permissions
• Project Permissions
• Requisition Permissions
• Training Permissions
• Workflow Permissions
• Webhook Permissions

Administration Permissions

Analytics Permissions

Biobanking Permissions

Configuration Permissions

Document Permissions

Access to documents in the Ovation LIMS is controlled by access levels granted for document folders:

• View access on a folder allows users to see what files are in the folder
• Read access on a folder allows users to see the contents of the files in that folder (previewing and downloading)
• Write access on a folder allows users to create, modify
• Admin access on a folder allows users to delete files in that folder

These permissions depend on how they are held. If the role (that includes this access) is granted at the organization level, the user can access documents in that folder at the organization level (under More > Documents). If it is granted on a project, then they can access documents in that folder in that project (in the Documents tab on the project and on any requisition in that project).

Note that patient result reports are actually documents (stored in the Incomplete Documents or Complete Documents folder for the requisition). Users must have the appropriate document permission in order to preview those reports (in a requisition's Reports tab).

There is one regular permission pertaining to documents:

Inventory Permissions

Project Permissions

Requisition Permissions

Training Permissions

The Org Training Packages and Training permissions are obsolete.

Workflow Permissions

Webhook Permissions

Webhook administration must be done through the API and two permissions control that: Webhook Administrator and Webhook User. Their usage is defined in the article that describes these APIs.