Operators are the users who execute procedures in Epsilon3; running steps, recording data, and signing off on the work they perform. In Epsilon3's Role Based Permissions model, an Operator is a role you define once and assign to anyone who runs procedures. This article covers creating an Operator role and assigning it at the workspace or project level.
Before you begin: how roles work
Three principles govern all permissions in Epsilon3:
Roles are explicit. Permissions are never implied. If a permission isn't granted through a role, the user doesn't have it.
Permissions are additive. When a user has multiple roles, they receive the combined permissions of all of them. Permissions are only granted or omitted — never denied.
Workspace and project permissions are evaluated separately. Roles applied at the workspace level and roles applied at the project level do not mix or inherit from one another.
Every role draws from four independent permission categories — View, Operate, Edit, and Admin. These categories do not inherit from one another: granting one category never implies another, so each permission must be granted deliberately. For the full model, see Role Based Permissions.
Create an Operator role
Go to Settings > Roles.
Click New Role.
Enter a Code — a short abbreviation used internally and on sign-offs (for example, OP).
Enter a Role Name — the label shown in the UI (for example, Operator).
Select the permissions to assign to the role. For an Operator role, select all permissions under Operate — the category that covers running procedures, completing steps, and recording data. Leave Edit and Admin unselected for a standard operator unless the person also authors or administers content. If your operators also release procedures or suggest edits, include those permissions as well.
Click Create Role.
NOTE: Changing a role code does not propagate to existing procedures and can cause issues with sign-offs if you change a code that is already in use. Set the code carefully when you create the role.
Assign the Operator role
Because roles are reusable, the same Operator role can be assigned to many users at either level.
At the workspace level: Go to Settings > Users, select one or more users, click Edit Workspace Roles, and choose the Operator role. Workspace roles apply to a project only when the user is added to that project and no project-level roles are assigned to them there.
At the project level: Assign the Operator role from the Users page using Edit Project Roles,
or from within a project's Users tab via + Add User. When any project role is assigned, the user's workspace roles are ignored for that project.
Tip: assign operators in bulk with Groups
If you manage many operators, create a Group (for example, Ops – Operator), assign the Operator role to the Group, and then control access by adding or removing members. Roles assigned to a Group apply to every member, which keeps onboarding and offboarding consistent. See the Groups section of Role Based Permissions for details.
Related articles: Role Based Permissions · Invite / Edit Users · Projects