A database-level backstop between organisations

OrionGIS web 1.61.0Released 9 November 2026

Every organisation-scoped table now enforces tenant isolation in Postgres itself — row-level security with per-request organisation context, a separate app database role, and automated cross-tenant tests in CI — so a missed filter can never leak one organisation's data to another.

Read the announcement: A database-level backstop between organisations

Changes since 1.60.0.

#New

  • Row-level security on every organisation-scoped table. Projects, maps, dashboards, published maps, dataset access records, AI chats, form-project ownership, saved datasets and organisation shares now enforce organisation isolation inside Postgres itself (ENABLE + FORCE ROW LEVEL SECURITY). The platform sets the requesting user's organisations for each request — transaction-locally, so pooled connections never leak one person's context to the next — and an unset context sees no organisation rows at all.
  • A separate application database role. Data queries can run as a non-owner orion_app role that cannot alter the RLS policies, while DDL and identity lookups stay on the owner connection — the two-role split from the platform's security plan. RLS is a backstop: the application layer still filters by organisation explicitly.
  • Automated cross-tenant tests in CI. A lint rejects any new tenant table without an org_id column or policy block, and a negative isolation suite runs per table as the application role: organisation A sees zero of organisation B's rows, including the unset-context case, and cross-tenant writes are rejected.
  • Public share links keep working signed-out. Published maps with link sharing on are the one deliberate carve-out, so a shared map opens for anyone with the link as before.

#Improved

  • Trusted internal services are explicit. Orion Core's platform queries and the machine-to-machine endpoints declare their service identity up front, so internal checks (usage counts, removal batches) keep seeing what they are entitled to see.
  • Saved datasets join the organisation model. A dataset saved while working in an organisation is filed under it, like every other resource.

#Notes

  • Nothing changes for people who do not belong to an organisation: their resources are personal, exactly as before.
  • The platform switches this on with ORION_RLS_ENABLED=1 and ORION_APP_DATABASE_URL; the release is designed so each can be rolled out and rolled back independently.