Docs menu
Configuration Guide

Configuring CMS Life Sciences for your organization.

What's live today for study setup, access control, and system monitoring — and what's still ahead on the admin roadmap.

Access control

Dashboards are gated by access rights.

Every screen is gated by access rights, so each role sees exactly the dashboards and actions it's authorized for. The admin console itself requires the config:admin right — everyone else is refused before the page ever renders.

Role → access rights
QA Auditor
audit trail · export
Sample Manager
receive · reconcile
Discovery Scientist
biobank:query
Custodian
custody:approve
Administrator
config:admin
Study configuration

Study configuration is set once and enforced automatically.

Every study is configured with the fields below before intake begins, so downstream workflows (reception gates, reconciliation, retention) run without manual re-checking.

Available

Entry model

Design-first or manifest-first intake, set per study.

Governance tier

Clinical, biobank, or commercial — sets the compliance posture.

Reconciliation model

Reconcile before or after receipt, per your operational process.

Retention policy

Fast-dispose or long-term-retain, driving disposition defaults.

LIMS target & manifest template

Where data lands downstream and how intake manifests are structured.

Site, manager & custodian assignment

Who's accountable for the study across sites and freezer hierarchy.

Configurable values, field by field.

The exact options behind each field above.

FieldOptions
Entry modelDesign-first · Manifest-first
Governance tierClinical · Biobank · Commercial
Reconciliation modelAfter-receipt (polling) · Pre-receipt (blocking)
Retention policyFast-dispose · Long-term-retain
Study statusActive · Closing · Closed
Study status

A study moves through three states.

Status isn't a free-text field — it's a lifecycle, and moving from Closing to Closed is gated by the closure checklist below.

Active

Normal operation — intake, tracking, and reconciliation all run.

Closing

Closure has been initiated; the prerequisite checklist is being worked through.

Closed

All prerequisites passed and the study was finalized with a captured reason.

Study closure

Closing a study requires a gated checklist.

Closing a study checks every prerequisite before it lets you finalize. Each prerequisite is Ready, Blocked, or Not yet implemented — you see exactly what's holding up closure, traced back to real operational data.

In progress
  • Sample disposition progress — how many samples are dispositioned vs. remaining
  • Open transfers — none left in flight
  • Open returns — none left in flight
  • Open reconciliations — no unresolved discrepancies
  • Samples currently in use — none checked out
  • Reason-for-change required before finalizing
System monitoring

System health monitoring.

The admin console's system health panel shows live component status and any queued/backlogged records, so operational issues surface before they become compliance issues.

Available
System health
Intake pipeline
Online
LIMS connector
Online
Notification service
Connecting
Queued records
0
What's ahead

On the admin roadmap.

  • Validation-rules consoleRoadmap
  • Email/notification watcher configurationRoadmap
  • Archive lock controlsRoadmap
  • Team activity viewRoadmap
  • Access review workflowRoadmap
  • Cold-chain / temperature IoT monitoringRoadmap
  • Connectors for existing systems & data backbonesRoadmap