One organisation can never see another’s data

One organisation can never see another’s data

Enforced by the database itself, not by remembering to write the right query. A mistake fails closed instead of leaking.

Why the distinction matters

Most multi-tenant systems keep organisations apart by adding a condition to every query. That works until somebody writes a query without it — and the failure is silent, because a query missing its condition returns more rows rather than an error.

Here the rule lives in the database. Every request declares which organisation it is acting for, and the database refuses rows belonging to anybody else. A query written without the condition returns nothing, which is a bug somebody notices in a minute.

What that buys you

The worst outcome of a coding mistake is a page that is empty rather than a page with somebody else’s meetings on it. That is the only version of this property worth having, and it is the thing a security questionnaire will ask us to demonstrate.

Read next

  • Who may do what

    Owner, administrator, host and member — checked at the door, in the page, and in the database, rather than only in the menus.

  • A log of what was done

    Every moderation action, role change and integration change, with who did it — and the database refuses to let it be altered.

  • A browser that cannot be turned against you

    A strict content policy, code from a lesson run in a sealed sandbox, and uploads scanned before anybody can open them.

Everything it does

Want to see this working?

Tell us what you are trying to do with it and we will show you that, rather than a tour of everything else.

info@seeuall.com
    One organisation can never see another’s data — SeeUAll · SeeUAll