Organisation groundwork and account-scoping fixes

OrionGIS web 1.54.0Released 9 November 2026

The first slice of the approved multitenancy build: the organisation tables that team sharing will be built on, plus five account-scoping fixes — form AI-publishing now checks project ownership, client accounts can no longer create projects or maps, Orion staff can manage any dashboard, the Governance page requires sign-in and hides member emails, and Orion Central reflects staff changes immediately.

Changes since 1.53.0.

#Security fixes

  • Form publishing checks ownership. The AI form builder's publish step (the one forms route that skipped this check) now verifies that you own the form project before publishing into it — the same guard every other forms route already had.
  • Client accounts stay in their lane. A client account can no longer create projects or maps through the API — matching the boundary OrionForms, Map Studio, OrionAI and checkout already enforce for those accounts.
  • Governance page is sign-in only. The organisations page and its detail pages previously rendered to signed-out visitors. They now redirect to sign-in, and member email addresses are shown only to members of that organisation and Orion staff — everyone else sees names and usernames only.
  • Staff can manage every dashboard. Orion staff could view any dashboard but not edit it. Editing now matches viewing: staff and platform administrators can manage dashboards.
  • Orion Central reflects staff changes immediately. The Central chrome previously used a cached (up to 2 minutes old) staff flag; it now checks fresh, so a staff removal hides Central right away.

#Foundation

  • The organisation data model from the approved multitenancy plan is in place behind the scenes (organisations and their members, with the legacy billing-account and client-account data mapped in automatically). No visible change yet — the team-management UI builds on this next.

#Notes

  • These are the web-side items from the 2026-11-09 multitenancy audit; the backend-side items land in a following release.