A database-level backstop between organisations
Organisation isolation is no longer something only the application promises — Postgres now enforces it, row by row, with automated cross-tenant tests on every release.
When several organisations run on one platform, the worst failure is not a bug that breaks a page — it is a bug that quietly shows one organisation another organisation's data. Up to now, OrionGIS has guarded against that in application code: every query filters by organisation, every page checks membership and roles. That is the right first line of defence. But "every query must remember the filter" is a promise you have to keep forever, and the cost of forgetting once is a data breach.
So we added a second line that cannot be forgotten: the database itself now enforces organisation isolation.
Every organisation-scoped table — projects, maps, dashboards, published maps, datasets, AI chats, form projects and more — is now protected by PostgreSQL row-level security. With each request, the platform tells the database which organisations the person belongs to, transaction by transaction. A query that forgets its organisation filter simply sees no organisation rows. Not the wrong rows: no rows. An unset context sees none at all. Cross-organisation writes are rejected outright. And because the setting is transaction-local, a pooled connection can never leak one person's context to the next.
Alongside it, two engineering habits make the backstop durable:
- A separate application database role that runs data queries but cannot touch the security policies themselves — so a compromised query cannot simply turn the backstop off.
- Automated cross-tenant tests on every release: organisation A sees zero of organisation B's rows, per table, including the tricky unset-context case, and any new table without an organisation column fails the build.
One deliberate exception survives: a published map with link sharing on is public by design, so shared links keep working signed-out.
For everyone who doesn't belong to an organisation, nothing changes — personal work stays personal, exactly as before. What changes is the depth of the guarantee behind the organisations that do run on OrionGIS.
Read the full oriongis-web 1.61.0 release notes.
Release notes: OrionGIS web 1.61.0