Manage customer workspaces and access

Use a provider administrator user session for customer administration. Complete required MFA and recent authentication, then read the current principal before building a customer-scoped operation.

Prepare customer access

1. Create or select an organization with the organization operations.
2. Inspect its resource budget, camera assignments, and grants.
3. Create a customer invitation or authorized user with the appropriate role and camera choices. Invitation delivery checks and reissues have separate operations.
4. Confirm the user’s effective camera access before using the customer workspace.

Switch into a workspace

Switch current workspace requires the current session ID, CSRF token, and workspaceRevision in If-Match. Its body supplies organizationId. Use null to return to provider scope.

The successful response rotates the cookie session and CSRF credentials and supplies a new principal. Update the cookie jar with --cookie-jar as well as --cookie when making the switch. Replace your saved session ID and CSRF value from the returned response before subsequent scoped requests.

Clear cached resources, pending forms, media descriptors, and subscriptions when the workspace changes. A 409 or 403 with X-EyesOnIt-Workspace-Changed: 1 requires reading the principal and resolving the current workspace.

Reconcile uncertain changes

If the switch response is lost, bootstrap the current principal using the current cookie context before deciding what to do next. Retain the expected session identity for scoped requests. Read current assignments and revisions before resubmitting an ownership or grant change. Use the operation’s idempotency and revision headers where required.