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.
Security
Multi-tenancy, authorisation and auditability were the first things built in this platform, not a later hardening pass.
Architecture
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.
Membership, role and entitlement are checked on the server before any write. The interface never decides what you are allowed to do.
Owner, admin, manager, agent and viewer each carry an explicit set of capabilities, shown before you invite anyone.
Consequential changes are recorded with who made them and when, alongside a full audit of every AI action from trigger to outcome.
Email verification is required before a workspace can be joined, and authenticated sessions gate every route and server operation.
Cross-workspace references are rejected at the database level, so one workspace's record can never be linked to another's.
Data handling
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
Silent failure and false confidence are security problems too. i23 is built to report reality, including its own limits.
Human approval
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.
The platform highlights relevant information.
Your team applies judgment and expertise.
The record updates with a clear audit trail.