Documentation
How the Axiom platform works
A reference for the architecture behind your workspace: how tenancy is enforced, how access is governed, how modules are delivered and how activity is recorded.
Tenancy model
Each business is a tenant. Every record carries a tenant reference, and row-level security policies scope access to workspace membership. A single deployment serves any number of businesses without shared data paths.
Authentication
Owners register with business name, contact details and a password, which provisions the workspace, the owner membership and a trial subscription in one verified server operation. One-time codes, MFA and SSO extend the same service boundary.
Roles & permissions
Owner, Admin, Manager, Sales, Accountant and HR ship as templates. Roles and permissions are stored as data, so workspaces define their own roles and permission sets without code changes.
Modules
Capability is delivered as registered modules, each with its own permissions, navigation and lifecycle. Modules are activated per workspace and governed centrally from the platform control centre.
Audit & activity
Every meaningful action records actor, entity, action and metadata within the workspace, giving compliance reviews and internal investigations a single reliable trail.
Security model
Privileged operations execute only inside verified server functions with service-role access. Client applications never hold elevated credentials, and policies are reviewed with every schema change.
Get into a workspace
Create a workspace to explore the platform against your own operation, or sign in to continue where you left off. Questions the reference does not answer can go to support@axiom.app.