Tenant isolation
Each business edition has its own database, and company data is held in isolated database schemas. Tenant context is established and validated before business data is accessed.
Your business data.
Clear access and control.
Datum helps you control who can see your records and who can act on them, while keeping changes traceable. Company isolation, user permissions, and business rules apply to everyday work and Dot-assisted actions.
Server-side permissions
Module availability and role permissions are independent gates. Access control belongs beneath the interface, so navigation visibility is not treated as the security boundary.
Controlled business actions
Important actions pass through their owning services, permissions, lifecycle rules, and approval controls. The same principles apply when work is initiated with Dot.
Traceable change
Critical business actions retain actor attribution and audit history. The history connects controlled changes—such as postings, reversals, and approvals—to the responsible person and source records.
Layered protection
Protection at every layer.
IDENTITYAuthenticated sessions and unified company identityControlled selection across companies and editions
AUTHORIZATIONRole and object-aware access controlPermissions enforced at the API and workflow level
APPLICATIONCSRF protection and validated business transitionsControlled mutations and approval boundaries
DATASchema-per-company isolation and encryptionCompany data stays isolated
EVIDENCEImmutable audit history for operations and integrationsAttributable actions for compliance and investigation
Dot does not get a security exception
The model reasons.
Datum stays the authority.
Dot interprets your request and prepares work inside Datum's permissions and business rules. It does not decide what you may see, calculate your books, or commit changes on its own.
IDENTITYIdentity + companyValidated context
RECORDRecord scopeFiltered to the user's access
CALCULATIONCalculationDeterministic services, not the model
EXECUTIONExecutionPermission + confirmation
RESULTResultEvidence and audit trail
The same rules,
everywhere you work.
Company isolation, permissions, and audit expectations apply the same way whether someone is switching companies, connecting an accounting system, or moving through everyday work.
Safe company switching
When someone moves to another company, the previous company’s data is cleared before new records load.
Protected integrations
QuickBooks Online and Xero connections use encrypted credentials and can be revoked.
Boundaries that hold
Company isolation and permissions stay enforced as teams work across records, editions, and connected systems.
Attributable activity
Important changes record who acted, in which company, and when — ready for review and investigation.
Assurance
Built for assurance.
Clear about the stage.
Datum is building the technical controls and operating discipline required for enterprise assurance, without presenting readiness work as a completed independent attestation.
Controls designed toward SOC 2
Tenant isolation, role-based access, attributable mutations, immutable audit evidence, secure configuration, and controlled integrations form the foundation of Datum's SOC 2 readiness work.
- Readiness program in progress — not a completed examination
- Control design mapped to the Trust Services Criteria
- Evidence captured as the platform runs, not reconstructed for audit
Application security shaped by real web risks
Datum's engineering and review practices are informed by OWASP Top 10 risk categories, including access control, authentication, injection, insecure design, security configuration, integrity, and security logging.
- Risk-informed engineering, not a product certification
- Access control and authentication reviewed on every change
- Security logging carried into the same audit history
* SOC 2 readiness is not a completed SOC 2 examination or attestation. The OWASP Top 10 is a security-awareness framework, not a product certification.
Common questions.
How is one customer's data kept separate from another's?
Each company's business records are stored in an isolated data area rather than mixed with another company's records and separated only by a filter. Datum validates the company context before any business data is accessed.
Is Datum SOC 2 certified?
Not yet. The controls a SOC 2 audit looks for — how access is granted, how changes are recorded, how each company’s data is kept apart — are built and running, and our readiness programme is underway, with evidence collected as the platform runs. What remains is the independent audit itself.
Can we control what each person sees?
Yes. A person’s role decides what they can open and what they can change, and the system enforces it. Hiding a menu item is not what keeps data safe.
Is there an audit trail?
Yes. For important changes, Datum records who acted, in which company, and when, so a posting, reversal or approval can be traced back to a person and the records behind it.