Account scoping tightened, and the groundwork for real organisations
Five account-scoping fixes land today — form AI-publishing now checks ownership, client accounts stay in their own workspace, staff can manage any dashboard, the Governance page requires sign-in, and Orion Central reflects staff changes instantly — plus the invisible groundwork for team organisations.
Sharing maps, forms and data as a team is the direction OrionGIS is headed, and getting there properly means tightening exactly who can do what first. Today's release does that in five places, most of them invisible until someone tries what they shouldn't.
What changed
- Form publishing checks ownership. The AI form builder's publish step now verifies you own the form project — the same guard every other forms action already had.
- Client accounts stay in their lane. A client account can no longer create projects or maps, matching the boundary their forms and dashboards already live behind.
- The Governance page is sign-in only. It previously rendered to signed-out visitors and showed member emails. It now redirects to sign-in, and email addresses are shown only to members of that organisation and Orion staff.
- Staff can manage every dashboard. Orion staff could view any dashboard but not edit it; viewing and editing now line up.
- Orion Central reflects staff changes immediately. A staff removal hides Central right away instead of up to two minutes later.
And beneath the surface: the organisation data model from our multitenancy plan is now in place — organisations and their members, with existing billing and client accounts mapped in automatically. Nothing visible changes yet; the team-management experience builds on this next.
The long version of the plan — teams, roles and shared resources as the next milestones — is in the multitenancy proposal and its implementation plan, both in the public docs.
Release notes: OrionGIS web 1.54.0