HIGH story-supabase-backend-core-global-admin-007 5 pts
5
Story Points
High
Priority
Supabase Backend Core
Feature

User Story

As a Global Administrator
I want to provision a new member organization's context on the Supabase platform including database records, RLS scope, and integration configuration
So that So that the new organization is fully isolated from existing organizations with correct data access boundaries and can begin using the platform without manual database manipulation

Acceptance Criteria

  • Given a new organization is being onboarded, when the admin creates the organization record and assigns an admin user, then the new admin can log in and access only their organization's data
  • Given the new organization's admin performs database operations, when RLS evaluates their JWT claims, then only data scoped to their organization_id is returned
  • Given the new organization has unique terminology (e.g., 'frivillig' instead of 'likeperson'), when the admin configures org_labels, then all UI labels reflect the organization's terminology without code changes
  • Given the onboarding is complete, when the global admin reviews the organizations table, then the new organization appears with all required configuration fields populated
  • Given the new organization uses a different accounting system, when the admin configures their integration_configs record, then their sync service uses the correct endpoint and credentials

Business Value

The platform's business model depends on scaling across multiple member organizations (NHF, Blindeforbundet, HLF, Barnekreftforeningen, and future members). A repeatable, safe onboarding process is required to grow the platform without accumulating manual technical debt or risking cross-organizational data exposure. Each new organization represents recurring platform revenue and expands the impact of the likeperson network.