User Permissions and Roles

There are two main permission levels in Seal:

Permission Level	Description
Viewer	View entities Respond to training requests Note that the default level for all users is a Viewer.
Operator	All viewer permissions, and Run procedures (create, edit, review and archive runs and records. Includes test runs) Create, edit, review and archive documents and files Create and edit views Create and edit tags Add and remove tags from pages
Builder	All Operator permissions, and Create and edit training requests + view the training management page Create, edit review and archive procedures and steps Create and edit computed views Create and edit view groups Install templates (feature flagged) Create and edit collections (feature flagged)

Note that Admin is not a permission level, but may be assigned to someone who usually manages Seal user accounts.

Admins always have builder permission which cannot be edited.

Admins can make higher level organisational related changes such as edit roles and manage API keys.

Roles

Users can be assigned roles via the settings panel.

Users can be added into more than one role. Review requests can be sent out to roles.

• You can choose to upgrade all users to operator/builder or create custom roles and add specific users to them to assign different permission levels as needed

  • When creating a custom role, if permission level is not configured, users in the role will inherit any permission level given to them by other roles they are part of.

  • Users and custom roles always get the most permissive permission level they are given by their roles. E.g. if the same user is in two roles: one with Viewer and one with Builder permissions, the user will gain Builder permissions.

Adding and deleting users

Only admins can manage user counts within the organisation - click on the 'Members' tag in the Settings page.

Note that if a user limit may have been set on your Seal Platform, based on your contract. If more users are required, please email [e-mail].