Reusable access profiles
Administrators can assign and review profiles for the work a person performs. Privileged changes belong in the Security & Access workspace, with an audit trail for review.
Security & access
Stratal brings user access, permissions, client visibility and audit history into the same operating environment. Configure the boundaries for each team, then check them against real work.
Access model
A permission to use a module and permission to see a particular job are different questions. Stratal uses both, so access can follow operational responsibility.
Administrators can assign and review profiles for the work a person performs. Privileged changes belong in the Security & Access workspace, with an audit trail for review.
Programme, job and field assignments govern what a user can work on. Client access can be kept separate from internal delivery and administration.
Optional two-factor authentication and configured enterprise identity/SSO support the agreed sign-in model. Provider setup and rollout are checked per deployment.
In daily operation
Security is visible in routine decisions: who can change a record, who can approve it and what happened afterward.
Plan a controlled rollout →Audit history, controlled documents and approval records help teams trace decisions against the underlying job or document.
Client visibility and evidence downloads can be scoped to the appropriate programme and job rather than exposing the wider operation.
Security Centre and diagnostic views help authorised administrators review access, sessions, integrations and deployment health.
Before rollout
Choose one sample programme and check each account against it before opening a wider deployment.
Can they see their assigned work and submit the evidence needed, without access to unrelated jobs?
Can they review the team’s work and act on exceptions within their remit?
Can they see only the agreed programme, documents and reporting views?
Can privileged changes and access decisions be reviewed after they are made?
Available controls and identity options depend on the configured deployment.
Evaluate the controls