Skip to content

Roles & Permissions

This guide explains how Scifeon decides what a user may see and do, and how an administrator sets it up. Access is controlled in four places, which work together:

WhatControlsWhere
User levelAdministrator or regular userAdministration → User Management → Users
RolesWhich modules, administration areas and templates a user may manageAdministration → User Management → Roles
Data accessWhich experiments, samples and other data a user may read or writeAdministration → Settings → Security Settings, Organizations and project permissions
Procedure and approval settingsWho may review, release, withdraw or work on a procedure or experimentAdministration → Settings → Approval & Review and each procedure’s configuration

Every user is either a regular user or an administrator.

  • Administrator - turned on with the Administrator switch on the user. An administrator has every permission, can change system settings, manage organizations, projects, users and roles, and can always read and write all data.
  • Regular user - has the permissions given by their roles, and the data access given by the data access settings below.

Scifeon also ships a built-in Data Manager role. A Data Manager has every permission, but not module access, and can see the audit pages under Administration → Data. Use it for the people who maintain templates, the data model and configurations without making them administrators.

Administrators are not exempt from the access rules set on a procedure, described at the end of this guide.

A role is a named set of permissions. Open Administration → User Management → Roles to see the roles in the system.

Roles page

  1. Click New Role.
  2. Enter a unique Role ID, a Role Name and, optionally, a Role Description.
  3. Click Save.
  4. Open the role and switch on the permissions and modules it should give.

Changes to a role’s permissions take effect for every user who has the role.

A role can be assigned to:

  • Users - under Assigned Users on the role, or with Assign role on the user.
  • Departments - under Assigned Departments on the role. Every active member of the department then has the role.

A user can have several roles. Their effective permissions are all the permissions of all their roles combined: a permission is never taken away by another role.

Role details

The role page shows, from top to bottom:

  • Assigned Users and Assigned Departments.
  • Modules - access to separately licensed modules, see below.
  • Permissions - the permissions in the next section.
  • ELN and Procedures - where the role is used in approval and procedure settings. This is read-only here; it is changed in those settings.
  • Pages - administration pages that the role gives access to.

Permissions are for the people who set up and maintain the system rather than for day-to-day lab work. They decide who may change shared configuration: templates, the data model, procedure settings, dashboards and documentation. Recording experiments, samples and results needs no permission; that is governed by data access and the procedure and approval settings further down.

The permissions are grouped by the area they cover. Each one is described on the role page, and installed apps can add more. Some examples:

PermissionMeant for
Configure Procedure SettingsLab leads who maintain a procedure’s own configuration, such as which roles may work on it. See Configuring Procedures.
Manage Field CatalogPeople who define the shared form fields and result types in the Field Catalog.
Manage Report TemplatesPeople who design the reports generated from experiments and other data.
Audit Trails & EventsQA and auditors who need Audit Events and Audit Trail under Administration → Data.
Create ProjectsProject managers who set up new projects.

Modules are separately licensed parts of Scifeon, such as Insights or the AI Assistant. Module access decides who can open a module at all. It is the way to give a module to the people who need it, for example full Insights access to the people who build analyses and view-only access to those who read them.

Only the modules installed in your system are listed on the role page. Module access is not included in the Data Manager role, so a Data Manager needs a role with the module like everyone else. Administrators always have access.

Data in Scifeon always belongs to a user and to that user’s organization (department), and can also belong to a project. Whether other users can read or write it depends on the system’s data access mode, set by an administrator under Administration → Settings → Security Settings → Data Access.

Data Access settings

ModeEffect
All can read & writeEverybody can read and write all data.
All can readEverybody can read all data, but writing requires write access to the department or project the data belongs to.
Based on departments & projectsReading requires read access, and writing requires write access, to the department or project the data belongs to.

We recommend keeping data at least readable for all. Administrators can always read and write all data.

A user always has access to the data of their own department. To give access to other departments’ data, open Administration → User Management → Organizations, select the organization that owns the data, and use Add User or Organization under Access Control. Choose a user or another organization and whether they get Read or Write access.

Organizations can also be grouped into data scopes, which hide other parts of the organization from day-to-day lists without changing who has access. See Managing Organizations.

On the Projects page, the Manage permissions action on a project lets you assign users and departments to the project with Read or Write access. The project’s data is then available to them under the data access mode above.

Who may review, approve, sign, withdraw and release is not set with permissions on a role. It is set in the approval and procedure settings, which name roles and individual users:

  • Approval & Review - who may approve and withdraw approvals on experiments, per department and experiment type. See Approvals.
  • Procedure configuration - who may release versions, edit templates, create and edit experiments, and act as scientist or analyst on a given procedure. See Controlling Who May Work on a Procedure.

These fields accept both roles and individual users. When a field is left empty, everybody may act; once it is filled in, only the named roles and users may. On a procedure this applies to administrators as well.

The ELN and Procedures sections of a role list every configuration that uses the role, so you can check what removing a user from a role will affect.

When Require Approval Signature is turned on, a user who is allowed to approve, reject, review or withdraw must also confirm the action with a two-factor signature. See Two-factor signature.

  • SCIM - when users are provisioned from Microsoft Entra ID, Entra groups can be mapped to Scifeon roles, so role membership follows group membership. See SCIM Provisioning.
  • Audit - assigning and revoking roles, and adding and removing permissions on a role, are recorded as audit events. They are listed under Administration → Data → Audit Events, which requires the Audit Trails & Events permission.

A typical laboratory setup uses a small number of roles:

RolePermissions and modulesNamed in
ScientistNone, or Insights (View Only)Procedure configuration as scientist, and experiment creator and editor
ReviewerNoneApproval & Review as reviewer; procedure configuration as template reviewer
QAAudit Trails & EventsApproval & Review as reviewer and withdrawer; procedure configuration as releaser
ConfiguratorConfigure Procedure Settings, Manage Field Catalog, the Templates permissionsProcedure configuration as template editor

Assign roles to departments where everyone in the department should have them, and to individual users where only some people should.