A server drive bay with rows of green and amber status lights.

Foundation

Access & Audit

A leaver still holds three accounts. Disable them once.

A leaver still holds an account in three separate systems. The permission is a button hidden on a screen. Phasis lets IT disable a leaver in one place, and access to every module stops. Login is handled by Keycloak. We did not write it. Your IT team keeps the company login, SSO, MFA, the password rules and the lockout policy. We store no passwords. Every request is checked, not only the login screen.

A user gets a role, and a role carries a level on each module: read, write or approve. Approve covers ordinary write plus the decisions: a calibration, a work-order release, closing an NCR. The server checks the level on every action. Hiding a button is not the guard.

Even with the right level, nobody approves their own work. Quality, Calibration, HSE, Permit to Work and Documents all refuse it, including when one person holds both roles. Access is granted per module, not per record and not per line. Someone with write on Quality can act on any NCR, not only the ones they raised.

Who uses it

IT administrator
Keeps the company login, the SSO rules and the MFA policy in Keycloak, and disables a leaver in one place.
System owner
Maps roles onto modules: read, write or approve.
Approver
Signs off work that is not their own, because the server refuses self-approval.
Quality manager
Reads the history on a record and the central log when an auditor asks.
Auditor
Follows one record from entry to approval and sees who touched it.

Today vs Phasis

Today

With Phasis

TodayA leaver still holds an account in three separate systems.
With PhasisIT disables them once and access to every module stops.
TodayThe permission is a button hidden on a screen.
With PhasisThe server checks the level on every action.
TodayA wrong entry is corrected in place and the old value is gone.
With PhasisThe original stays and the correction is a new record.
TodayWho approved what is remembered by whoever happened to be there.
With PhasisThe record names the approver and the time, years after they left.
TodayNobody can say who changed that field last week.
With PhasisThe database logs every insert, change and deletion, with the fields.

Two trails, kept apart

The history on the record

Every regulated record carries who did what and when, on the record itself. An NCR keeps the reporter, the investigator and the approver. A maintenance job keeps who started it, who submitted it and who closed it. The name is a snapshot, so the record still says who did the work two years after they left.

The central log

On top of that, the database itself records every insert, change and deletion: who, when, and which fields. A module cannot forget to log. Nothing in that log can be edited or deleted, and Settings reads the same table.

Regulated records are not deleted

Every type has a named way out, and the original stays where the auditor can see it.

NCR

Cancel. There is no delete.
Certification

Revoke, with a reason.
Inspection reading

Void, with a reason. The original stays.
Issued permit

Close. A draft can be canceled.
Calibration record

Reject. The correction is a new record.
Risk assessment

Revise. The old version is superseded.
SOP version

Supersede or retire.

What you get

IT disables a leaver once and access to every module stops.
We store no passwords. Login is Keycloak, kept by your IT team.
The server checks read, write or approve on every action. A hidden button is not the guard.
Nobody approves their own work, even if they hold both roles.
The database logs every insert, change and deletion. Nothing can edit that log.