Switching context between clients
Use the organization switcher to choose which accessible tenant is active in Portal or a product app. The active tenant controls the organization-scoped data and settings used by subsequent requests.
Switch organizations
- Open the organization switcher in the application header.
- Select an organization from the list returned by
myOrganizations. - Wait for the application to reload at its root page.
The switcher displays the organization’s configured company name and logo when available. It also displays your membership role when that information is present. The current interface does not pin a practice organization, provide a client-only filter, or preserve the page path during a switch.
Browser-tab behavior
The selected tenant ID and name are stored in sessionStorage, so each browser tab can hold a different active tenant. On first load, a tab can inherit an older localStorage value when one exists. This makes side-by-side client work possible, but verify the organization name in each tab before entering or changing data.
What changes after a switch
- Portal redirects to the Portal root.
- Accounting and the other product applications reload at that product’s root.
- Queries and mutations after the reload use the selected tenant context.
- Product navigation and available actions are recalculated for that tenant’s role and entitlements.
Unsaved page state is not preserved by the reload. Finish or discard edits before switching.
API context is separate
The browser switcher changes UI state only. API clients must send the tenant context required by the API they call. Do not assume that selecting a tenant in the web application changes an independent HTTP, GraphQL, or MCP client.