You need to define profiles, using 'Users', 'Profiles' before you can create user accounts, unless you will be using the standard profiles
.png?width=688&height=369&name=profiles%20(1).png)
You can modify the existing profiles, or use ‘Add a new profile’ if you want completely different roles.
Tick or untick Privileges to create appropriate profiles for the responsibilities of staff in your laboratory, then 'Save' when you are done. Use the specific privileges to create roles required to meet regulatory requirements e.g., you may want to restrict the privilege of locking / unlocking all protocols to a system administrator or QA function.
| Administration Privileges | |
| Can manage use accounts | This is an administrator function by default. |
| Can reset user passwords | This is an administrator function by default. |
| Can configure cloud storage | This is an administrator function by default. |
| Can unlock protocols | All users can lock or unlock protocols which they have created, this privilege is to lock or unlock protocols created by others. It may be useful as an approval function for a team leader or QA role. |
| Automatic inactivity sign out | This is not enabled by default, but may be appropriate for regulated labs. |
| Enable password complexity | This is not enabled by default, but may be appropriate for regulated labs. |
| Enable password expiration | This is not enabled by default, but may be appropriate for regulated labs. The default is expiry after 90 days |
| Community Privileges | |
| Can download protocols | This is a super user function by default. |
| Can download labware | This is a super user function by default. |
| Can download liquid classes | This is a super user function by default. |
| Instrument Privileges | |
| Can access machine logs | This gives access to the machine logs which may be useful to super users, admin users such as lab managers, or site engineers. |
| Can control instrument hardware directly | This enables low level control of firefly instruments, and is ordinarily reserved for service engineers. |
| Can configure instrument | This is an administrator function by default, to set up a simulated firefly. |
| Can control instrument manually | This gives access to the manual controls. It is only appropriate for users who have been trained in using these functions by reliance. |
| Can access instrument setup | This gives limited access to the setup functions. It is not ordinarily required. |
| Can access audit logs | Access to the audit log is not enabled by default, but may be appropriate for admin or QA functions in regulated labs. |
| Labware Privileges | |
| Can manage labware | This is a super user function by default. |
| Protocol Privileges | |
| Can override execution setup | This is a super user function by default. |
| Can design protocols | This is a super user function by default. |
| Can rollback protocols | This enables users to revert to an earlier version of a protocol. It is not enabled by default. |
| Can execute protocols | This is a user and super user function by default. |
| Can execute protocols in debug mode | This privilege allows users to execute a protocol one step at a time, or to ignore pauses, both of which may be useful in protocol development. |
| Can adjust protocol variables | This is a user and super user function by default, to set protocol variables before execution. |
| Can update labware during protocol execution | This is a super user function by default, to update certain consumables. |
Name the new profiles; it would be useful to give them descriptive names e.g., 'Senior Technician' or to match the terms used in your SOPs.