Sensehawk application supports workflows and access based on your role. We have set the permission sets to aid workflows and restrictions. The permission sets available are Basic, Advanced, Manager, and Admin.
Sensehawk application is access specific. Based on the permissions set to a user, the applications will be accessible. For instance, Administrators will be able to view and access all asset and organization-related information. Other users will have access only to the assets they are assigned to.
Workspace & Permissions
Organization and Asset Workspace
The items in the applications' (Tasks, Forms, and Files) can be accessed at the organization and asset workspace.
Users can have different permissions under the organization and the asset workspaces.
The access to applications and their items depends on the access level set to a user in the permission settings. (Settings >> Users)
Similarly, the items created under the asset workspace of a particular asset are accessible only to the users added to that asset. (Asset >> Settings >> Users)
Organization and asset are separate workspaces that can hold tasks, forms, and files accessible only to the users added to the respective workspace, depending on their permissions.
Teams & Roles
There may be cases where you need to assign specific permissions that apply across all assets to a user. For example, Asset Managers should have admin-level privileges in all the Assets they manage. You don't need to set these permissions in each Asset separately. Instead, a role can be created and assigned the admin permissions at the organization workspace, and the asset managers can be added to this role.
Similarly, if a set of users needs to be assigned to a particular task regularly. A team can be created, and users can be added to the team.
Furthermore, if the team requires restrictions. A role can be created with specific permissions, and this role can be assigned to the team.
Types of Permissions
Each user can be assigned different permissions for each application in a particular workspace. This includes
General - permissions related to modifying organization or asset details, managing users & teams, and assigning permissions to users & teams.
Tasks - permissions related to the Tasks application, i.e., creating and modifying tasks, managing task templates, closing tasks, etc.
Forms - permissions related to the Forms application, i.e., creating and modifying forms, managing form templates, viewing responses, etc.
Documents - permissions related to the Files application, i.e., viewing, modifying, and sharing documents.
Now that we understand the different workspaces. Let's see how we can control the permissions for users in each workspace.
Permission Set
A user can have different permission sets. It may happen that specific permissions defined can be conflicting at some level.
For example, a user may be assigned Manager access in Tasks for all assets added via organization settings. At the same time, this user may have been granted Admin access within a particular asset and Advanced privileges via a role in that asset. Now, how would these different levels of permissions work?
The answer is simple - the permission that gives the highest privileges would be applicable. Hence, the user would have Admin privileges for that asset.
Let us look at some more examples to understand permission settings better.
Let's consider a user with the permissions granted for tasks and forms via organization settings, asset settings, and roles.
As shown above, this user has been granted different privileges for tasks and forms, from organization settings, asset settings, and an asset-level role. Let's see what the resultant permissions for this user would be under the organization workspace and asset workspace of asset "A".
To understand this, let us break the permissions down into two sets:
Set 1 - permissions that influence the organization's workspace privileges
Here, for each application, the permission which gives the higher level privileges will take effect (marked in green). Hence, the resultant privileges would be the "Admin" level for tasks and forms.
Set 2 - permissions that influence the privileges in the asset "A"
Here also, for each application, the permission which gives the higher level privileges will take effect (marked in green). Hence, for tasks, the resultant privileges would be "Admin" level, and for forms, they would be "Advanced" level.