Enterprise (employer)
Employer / enterprise sponsors: contracted employers, enterprise admin, user roles and approval limits; shares org/billing/users patterns with other sponsor shells (per OPS handoff).
Implementation status: requirements documented — authenticated workflows not built (blocked on backend).Intended users
Employer / enterprise sponsors with contracted programmes and internal admins.
Authentication & access
Invitation-based access; shares org/billing/users patterns with other sponsor shells (OPS handoff).
Enterprise admin capabilities (e.g. US-007 / MEDICA-37 in ops designs).
Onboarding
Organisation & contract setup (OPS·20).
User provisioning and approval limits.
Navigation & screens (Figma)
Organisation dashboard, users, billing, settings (shared sponsor shell pattern).
Workflows
Contracted employer → admin invites employees → sponsorship / approval within limits.
Permissions boundary
Enterprise admin vs member; approval limits enforced server-side.
No provider quotation or expert case tools unless explicit multi-role.
Backend capabilities needed (no API paths in repo)
Organisation, contract, and billing integration.
Sponsor approval and spend limits.
User invite and role APIs.
UI states to implement
Contract pending
Empty users
Approval pending
Limit exceeded
403
Acceptance criteria
Enterprise admin sees org shell consistent with OPS·20 patterns.
Approval actions respect contract limits from API.