Security
This page describes controls that are implemented today, in plain language. It is not a certification, and no page can prove the absence of all defects.
Shift schedules staff, not patients. There are no patient fields anywhere in the product — no names, no record numbers, no clinical detail. The riskiest category of healthcare data is absent structurally, not filtered.
Every table is protected by row-level security scoped to your workspace. One department's roster, schedule, and requests are invisible to every other workspace — enforced by the database itself, not just the application.
Authentication runs on Supabase Auth over TLS. Sessions are cookie-based and every request re-checks membership; removing someone from the workspace cuts their access on their very next request.
Owners and managers configure and publish; techs see their own schedule, volunteer, swap, and request time off. Write paths check the role on the server — hiding a button is never the security boundary.
Calendar feeds and the OrderFlow roster import use long, unguessable per-scope tokens. Each serves the minimum data its purpose needs, and disabling or regenerating a token kills the old link immediately.
Schedule-affecting actions record who did them. The draft engine proposes and a human decides — nothing publishes a schedule, books a person, or changes coverage on its own.
Security questions during procurement: info@axiomeeg.com