Organizations & Multi-Tenant

Every resource in MonSPHERE — monitors, dashboards, alert rules, API keys, roles — belongs to exactly one organization. There's no implicit cross-organization visibility, including for regular Owners and Admins.

Membership

Users join organizations via invite (POST /organizations/:orgId/members/invite, quota-checked against user_limit) and hold exactly one role per organization. A single user account can belong to multiple organizations with a different role in each.

Isolation

Data isolation is enforced at the query layer — every list/read/write handler scopes by organization_id. This is what makes the platform genuinely usable for MSPs running many client organizations from one deployment without client data ever crossing tenant boundaries.

Deleting an organization

DELETE /organizations/:orgId (Owner only) removes the organization and cascades its monitors, dashboards, and memberships. Audit log entries for the organization are preserved — they're append-only and outlive the organization they describe by design.

Cross-organization access

The only role that spans organizations is Platform Admin (isPlatformAdmin), used exclusively for platform operations — see Platform Administration.