Skip to content

Security

Isolation at the database, accountability in the record.

Multi-tenancy, authorisation and auditability were the first things built in this platform, not a later hardening pass.

Architecture

Isolation first, then permissions.

Workspace 1Records · Members · AuditWorkspace 2Records · Members · AuditWorkspace 3Records · Members · AuditServer-side authorization · row-level access rules · audit logging

Row-level isolation

Every record carries its workspace, and the database itself enforces that you only ever see your own. Isolation is not an application filter that a bug can bypass.

Server-side authorisation

Membership, role and entitlement are checked on the server before any write. The interface never decides what you are allowed to do.

Role-based permissions

Owner, admin, manager, agent and viewer each carry an explicit set of capabilities, shown before you invite anyone.

Audit trail

Consequential changes are recorded with who made them and when, alongside a full audit of every AI action from trigger to outcome.

Verified authentication

Email verification is required before a workspace can be joined, and authenticated sessions gate every route and server operation.

Referential safety

Cross-workspace references are rejected at the database level, so one workspace's record can never be linked to another's.

Data handling

Your records stay inside your workspace.

Records are workspace-scoped by design, and every server-side operation validates membership, permission and entitlement before any change is made. Customer content is not written into platform logs. We do not publish certifications we do not hold.

Truthfulness

A system that tells you what it does not know.

Silent failure and false confidence are security problems too. i23 is built to report reality, including its own limits.

  • Delivery status reflects what the transport actually reported — nothing is marked sent on assumption.
  • Integration health shows the real connection state of each channel.
  • AI confidence is stated in words — confirmed, likely, uncertain, not found.
  • Without supporting evidence, i23 answers unknown rather than inventing one.
  • Approvals expire instead of executing against stale conditions.
  • Approved actions execute exactly once, even if retried.

Human approval

Judgement stays with your team.

i23 never quotes, binds, endorses, cancels or decides a claim on its own. It prepares the work and routes the decision to a licensed person, recording the whole chain.

01

Signal surfaced

The platform highlights relevant information.

02

Human review

Your team applies judgment and expertise.

03

Approved action

The record updates with a clear audit trail.

Want the architecture detail?

We're happy to walk your team through how access, isolation and auditability work.