There are 4 different user permissions that exist within Scilife.
Administrator
This is the highest permission level. The administrator has full access to all functionalities and all settings within the designated environment.
They have access to all documents even if they do not have a role in them and the ability to edit and modify documents.
The default system settings only allow Administrators to create, edit, and delete users. However, permission settings can be altered by an Administrator to allow Managers and Regular Users the authority to do this.
An Administrator can also modify a Manager and Regular User’s unique permissions so that their profiles are more closely aligned to.
Manager
Managers can access document types, they can access and edit module settings, manage contacts, and access the dashboards of other users. (A Regular User does not have these permissions.)
Managers and Regular Users can be given access to do the following if allowed by an Administrator:
Create/ delete/ edit users
Create/ delete/ edit offline users
Create/ delete/ edit new Clients/ Vendor/ Contact
Create/ delete/ edit new Product/ Service/ Project
Managers and Regular Users can also create Tags, but this functionality can be opted in or out for each permission level by an Administrator.
Regular User
A Regular User has access to all available modules, with access to start a document or an event and to be involved in its workflow.
As already mentioned, a Regular User’s permissions can be adapted by an Administrator to line up more closely with a Manager’s if appropriate.
Read-only User
A Read-only User’s main purpose is to have access to the system and view items.
They have sight of all items that are assigned to the groups to which they have been given access. It is important to note that they cannot have a role in any of these items as their access is read-only.
Read-only Users have the option to follow allocated pieces of training and to sign these off once completed.
They are also able to mark tasks as completed and external links as read and understood.
To note
Allowed to be QA Person – indicates if the user will be able to sign off a document as a QA. This is only available to Administrators, Managers, and Regular Users
Groups – all users must be assigned to one or more groups to which they will require access. The main purpose of having groups is to limit access thus only allowing a user access to a group they should have access to.
Module Permissions – specific modules need to be activated when creating a new user. Always ensure you select those that are relevant to the user.
