Security
What actually protects your data.
Only what we can point at a shipped, running mechanism — nothing broader, nothing hedged.
Tenant isolation enforced at the database
Every table carries row-level security scoped to your organization — access is checked at the database, on every query, not just hidden in the interface.
Role-based access
Every action is gated by capability grants tied to a person's role. What someone can see or do follows what your organization assigned them, never what a screen merely declines to show.
Restricted evidence visibility
Capability evidence used to make decisions about a person is visible only to authorized reviewers. The person it's about sees their own results — never the underlying evidence record.
Tenant-scoped authentication
Every sign-in is verified server-side and bound to one organization's roster. There is no shared login and no standing demo account with access to real data.
Suspension takes effect immediately
Turning an organization off cuts every session tied to it at the next request, across every door in — not on a delay, not only for new logins.
Imported course content runs isolated
SCORM packages are served from a separate origin from the main application, sandboxed away from your session — untrusted course code never runs alongside your data.
Have a security question, or something to report?
Contact security