SC-01: Organization Setup

Andi Lamprecht ·2026-05-11· 2 min read· Draft

Narrative

David navigates to the ATOMx registration page and initiates the organization-first registration flow [UERQ-SYS-1976]. He provides the organization’s legal name, organization type (Commercial Operator), and his contact information as the designated administrator.

The system creates the organization with Operator entitlement automatically granted [UERQ-SYS-1898, UERQ-SYS-1901] and creates David’s user identity as Organization Administrator within the new organization’s identity realm. David logs into the organization admin dashboard.

He reviews the organization’s initial state: Pending verification [UERQ-SYS-1998(a)]. He completes email verification and the organization transitions to Active state [UERQ-SYS-1998(b)]. He configures the initial authentication method as local accounts — federated SSO will come later once he has validated the platform’s behavior [UERQ-SYS-1996(a)].

David invites three users: the Fleet Manager (assigned Fleet Manager role), and two senior pilots (assigned Pilot/Operator role) [UERQ-SYS-1917(a), UERQ-SYS-1917(b)]. Each receives an invitation email with a link to create their identity within the organization’s realm. David verifies that the invited users appear in the organization’s user roster with Pending status.

He confirms that the Operator entitlement is active and that entitlement-gated roles (Pilot/Operator, Fleet Manager) are available for assignment [UERQ-SYS-1918]. He reviews the organization data isolation confirmation: the dashboard indicates that the organization’s identity realm is separate and that no cross-organization identity sharing exists [UERQ-SYS-1985, UERQ-SYS-1986].