The Organizations tab (OrganizationsPage.qml, route Organizations) manages multi-tenant identity workspaces when connected to a server control plane (Modes 2–4). Users can operate inside their personal tenant or switch into shared Organization workspaces to collaborate on shared models, remote workers, and cloud storage quotas.
Signed-in Organizations view with New organization, Accept invitation, Your organizations table, and Pending invitations list.
Availability & Authentication Gate
Signed-Out State (!isSignedIn): Displays a gated empty state ("Sign in required") explaining that organizations and team workspaces require authentication, with a primary Sign in button triggering Keycloak OIDC Authorization Code + PKCE sign-in (accountViewModel.signIn()).
Signed-In State (sessionState === "signed_in"): Unlocks header actions, Your organizations, and Pending invitations.
Step-by-Step User Workflows
1. Create an Organization or Accept an Invitation
Click New organization (organizationDialog) in the header to create a new team tenant.
Click Accept invitation (acceptDialog), or act directly on rows under Pending invitations when invites are waiting for your account.
2. Activate a Tenant & Manage Organization Members
Locate a workspace row in Your organizations (organizationsTable) and click View.
Clicking View invokes activateTenant(row.tenant_id), switching the active desktop/server tenant context (which updates available models in Models and quota space in Storage).
When the activated tenant is an "organization" (activeTenantKind === "organization"), membersDialog (openForOrganization(tenantId, name)) opens so owners/admins can inspect memberships or send invitations.
flowchart LR
SignedOut{"sessionState == signed_in?"} -->|No| SignIn["Sign in (Keycloak OIDC PKCE)"]
SignIn --> Table["Your organizations & Pending invitations"]
SignedOut -->|Yes| Table
Table --> ViewOrg["Click View on Tenant Row"]
ViewOrg --> Activate["activateTenant(tenant_id) updates Active Space"]
Activate -->|kind == organization| Members["Open membersDialog (Manage Members & Invites)"]
View (activates tenant and opens membersDialog for organizations), plus Refresh
Technical Reference
Server-Side Tenant Enforcement: The desktop displays tenant memberships returned by the backend after verifying the user’s OIDC token; authorization checks and ownership boundaries remain strictly enforced server-side.
Downstream Impact of Switching Tenant: Activating a different organization immediately scopes server-side Storage quotas, Model Registry sharing visibility, and Remote Workers access to the selected tenant.