Skip to content
  • There are no suggestions because the search field is empty.

Understanding Roles & Permissions in Proqio

Proqio enables users to assign a variety of different roles to team members, and these roles are in turn associated with different permissions within the project. This article goes into detail about the different roles and their associated permissions.

What are permissions in Proqio?

Permissions are the actions that a user is allowed to execute in the Proqio system, which are in turn associated to a variety of different role options, all of which will be detailed in this article. Additionally, some permissions are tied directly to the project as a whole, and the other type of permission is that which is tied to groups set within projects by users. A project can have numerous groups belonging to it. 

Additionally, it is important to note that the set of actions allowed for each "type" of permission (project vs. group) are different, because they are not related to the same entities. Also, many actions in the Proqio interface require several permissions to be granted simultaneously. 

Why is this functionality useful?

Roles and their associated permissions are desgined to manage user access and control within a Proqio project. Their main purpose is to ensure each user has access to the data and features they need, based on their responsibilities within the project. This functionality therefore enhances operational efficiency and data integrity.

 


Functionality Highlights:

  • Access Control: Allows project managers to limit and define user access and control levels within their team.

  • Operational Clarity: Enables project managers to define what actions their team members can perform within Proqio. 

  • Preservation of Data Integrity: Prevents unauthorized modifications to critical configurations, such as instrument settings or alert thresholds.


Project-Level Permissions

The highest level role in the Proqio heriarchy is a project-level is the SuperAdmin role (SAdmin). They will always be able to execute all existing action available in the project as a whole for all groups within the project.
 
Below is a table detailing which permissions are associated with which roles at project-level.
 
Permission
SAdmin
Admin
Editor
Viewer
Edit project details
View users
Invite users to project
Edit users
Delete users
Create new groups
Edit visible groups (group details)
Remove visible groups
View teams (user can always view teams where he belongs)
Create team
Edit team
Delete team
Get users in and out teams (also view permission required)
Get groups in and out of teams (also view permission required, view permission required for groups added)
View categories
Create category
Edit category
Delete category
View parsers
Create parsers
Edit parsers
Delete parsers
Manual data input
View connections
Create connections
Edit connections
Delete connections
 

Group-Level Permissions

As in the project-level permissions, it is important to highlight that any user with a SuperAdmin role (SAdmin) at project-level always has every type of permission for all the groups in the project. Additonally, note that group-level permissions apply to sites as well as groups within a project.
 
Below is a table detailing which permissions are associated with which roles at group-level.
 
Permission
SAdmin
Admin
Editor
Viewer
View instruments
Create instruments
Add instruments to this group
Remove instruments from this group
Edit instruments in this group
Disable instruments in this group
Delete Alerts from instruments in this group
Delete records from instruments in this group
View dashboards
Create dashboards
Add dashboards to this group
Remove dashboards from this group
Edit dashboards
Delete dashboards
View report
Create reports
Add reports to this group
Remove reports from this group
Edit reports
Delete reports
View Alert notifications
Edit Alert notifications