Governance & audit
Who may change what, which model versions are approved, and an append-only record of every change with its stated reason.
Your access
Sign in to see your role and the audit trail.
Permission matrix
Roles are stored separately from profiles and checked server-side by security-definer functions.
| Role | Can | Cannot |
|---|---|---|
| Viewer | Read the twin, scenarios and the audit trail | Change any variable |
| Operator | Log downtime events and record actuals | Change model variables or approve |
| Process analyst | Build and run scenarios | Amend the baseline model |
| Engineer | Amend model variables and submit versions | Approve their own changes |
| Site manager | Approve model versions and scenarios for the site | Change cluster-wide defaults |
| Model administrator | Everything, including deletion and role assignment | Bypass the audit trail |
| Auditor | Read everything including the full audit trail | Change anything |
Model versions
Each version carries a change reason and an approval state. Only approved versions should inform an investment decision.
No model versions saved yet. The active model is the Yorkshire cluster template loaded from the source workbooks.
Audit trail
Append-only. Entries cannot be edited or deleted, by anyone, including administrators.
No audit entries yet.