Skip to content

Approvals & Review Comments

Scifeon provides a structured review workflow for experiments, steps, form fields, and procedure templates. The feature has two complementary components:

  • Approvals — formal sign-off actions (approve, reject, request changes, etc.) that record who reviewed what and when.
  • Review Comments — threaded discussions that annotate specific steps or form entries, used to communicate feedback during a review.

Both are accessed through the Review Comments panel and the Approve / Review button visible throughout the ELN.

An Approve or Review button appears:

  • In the ELN header — to approve the entire experiment.
  • In each step header — to approve an individual step.
  • On individual form fields — when a field has been configured to require field-level approval.

Click the button to open the Approval dialog.

Approval buttons

The actions available depend on the current approval status and the user’s role:

ActionWhen availableDescription
Request ReviewStatus: Initial, Changes Requested, or WithdrawnAssigns a specific reviewer to evaluate the item.
ApproveWhen not yet completedFormally approves the item.
RejectWhen not yet completedRejects the item. A note is required.
Request ChangesWhen not yet completedMarks the item as needing changes before it can be approved.
WithdrawAfter approvalRevokes a previously granted approval.

Approval dialog

The Approval dialog includes a Notify people field. Use it to send a notification to additional users when submitting an approval action (e.g. to inform the analyst that changes are requested, or to inform a manager that an approval was granted).

The dialog shows a table of all past actions for the item, including who performed the action, when, the resulting status, and any notes. This provides a complete audit trail.

If signing is enabled in the system administration, a Signatures section appears in the Approval dialog. Users can:

  • Sign — attach a digital signature to the experiment or step, indicating their review without explicitly approving. This is useful for the two-eyes principle, where one user approves and another signs to confirm they have reviewed the approval.
  • Withdraw Signature — remove a previously added signature.

Signatures

Individual form fields can be configured to require approval. When enabled, an inline approval button appears next to the field value. The button is disabled while the field has unsaved changes.

Review Comments are threaded discussions attached to a step or form entry. They are typically used by a reviewer to leave feedback for the analyst before formally approving.

Review comments

In the ELN click the dots-menu on a step or form field and select Add Review Comment.

Click inside an existing thread and type your reply. Replies are visible to anyone with access to the experiment.

Once the feedback has been addressed, a user with the reviewer role can mark a comment as resolved by clicking Resolve. Resolved comments collapse and are visually distinguished from open ones. A resolved comment can be reopened by clicking Unresolve.

Procedure templates support the same approval workflow. If template approval is enabled, a Review button appears at the top of the ELN Workflow Template editor.

When approving a procedure template version, an additional action is available:

  • Approve and Release Version — approves the template and releases the procedure version in a single step, provided the user has both reviewer and releaser roles.

For more information on procedure versions and release workflows, see Procedures.


Approval and signing are configured under Administration → ELN Settings → Experiment Approval & Signing.

Settings

SettingDescription
Department(s)The department(s) for which the approval workflow applies.
Type(s)The experiment types for which the approval workflow applies.
Enable ApprovalsTurns the approval workflow on or off for the department.
Enable SigningTurns signatures on or off.
Reviewer RolesRoles that are allowed to approve items and resolve review comments.
Withdrawer RolesRoles that are allowed to withdraw approvals.
Disallow self-withdrawalWhen enabled, users cannot withdraw their own approval.
Require template approval before releaseWhen enabled, a procedure version cannot be released until its template has been approved.