Organizations and Sign-In¶
Mission Control is invitation-first. An owner or admin invites your email to an organization; you then authenticate with a short-lived magic link, or with a GitHub account carrying that same address where the deployment enables it.
Accept an invitation¶
- Open the invitation email titled Join organization on Mission Control.
- Follow its unique invitation URL within 48 hours. The page shows Join organization, who invited you, and when the invitation expires.
- If you are not signed in, enter the invited email address on that page and select Send magic link. The link brings you back to the invitation.
- Select Accept invitation.
Expected result: your permitted landing page opens and the organization appears in the switcher. You now have the Organization Member preset. It does not grant Team/catalog/inference access. An available deployment audience can grant Chat independently.
If you are signed in with a different address, the page says so and offers Sign out. The invitation refreshes after sign-out is confirmed. If sign-out fails, the page keeps you in place, shows an inline retry message, and re-enables Sign out.
The invitation is tied to its email and organization. Do not forward it. Ask an admin for a replacement when it expires or targets the wrong address.
Sign in¶
- Open
/sign-inat your organization's Mission Control URL. - Enter the invited email address.
- Select Send magic link.
- Open the message titled Sign in to Mission Control.
- Follow the link within five minutes.
Magic-link tokens are stored hashed and rate limited. The configured bootstrap email, existing accounts, and recipients of unexpired pending invitations may receive links. The check-email screen does not grant membership by itself.
Sign in with single sign-on¶
Where your deployment connects your organization's identity provider, /sign-in offers Continue with that provider. If your organization's directory provisioned your account, this is your only way in: magic links and GitHub do not sign in directory-provisioned accounts, so the provider's own checks, such as MFA, always apply. Such an account belongs to that organization and cannot accept invitations from other organizations on the same deployment; use a different address for them.
Sign in with GitHub¶
Where your deployment configures it, /sign-in also offers Continue with GitHub. Select it, authorize Mission Control on GitHub, and you return signed in — no email round trip.
GitHub is a second credential for the address you were already invited with, never a second way to get in. Your GitHub account's primary email address must be verified on GitHub and must already belong to a member, an unexpired pending invitation, or the bootstrap owner. A GitHub account holding any other address is returned to the sign-in page, still signed out, with the reason shown.
The first person in a new deployment signs in with a magic link before GitHub will work: attaching GitHub to an account requires an address the console has already verified, and only a completed magic link or invitation does that. The same applies if an administrator created your account before you ever signed in.
Signing in with GitHub for the first time as a new invitee authenticates you but does not join you to the organization. Open your invitation email and select Accept invitation to finish; see Accept an invitation.
Switch organizations¶
Use the Organization selector in the persistent workspace header. The Organization and Team context selectors remain visible when the sidebar is collapsed. Every route is tenant-scoped; changing Organization opens that Organization's Overview, clears the previous Team and resource query, and reloads your current permissions.
Holding a role in one organization does not grant anything in another. If an expected organization is absent, verify that its invitation was accepted with the same email used for the current session.
Switch Team context and use navigation¶
- In the workspace header, choose a Team through Team context. All authorized Teams on Overview reports across the Teams permitted for each panel; coverage can differ between requests, spend, budgets and Team status. Other destinations keep their own supported behavior when no Team is selected.
- Open a sidebar destination. Links retain the selected Team; reporting links also retain the absolute reporting window. Default and preset reporting URLs redirect to pinned
fromandtobounds before rendering, so sidebar reporting links keep the same window. The URL is the source of truth, including browser Back and Forward. A Team resource route takes precedence over ateamIdquery parameter. - To investigate another Team, change Team context. A resource detail page returns to its list, and resource/filter identifiers and pagination are cleared so an earlier key, Trace, Session, evaluation resource or budget subject cannot carry into another Team. Evaluate uses this same Team selection across Datasets, Experiments, Evaluators, Scores, Definitions and Review, with no separate Team picker; All authorized Teams asks for one Team on these pages. Team detail instead opens the newly selected Team when you can read it; All authorized Teams opens the Teams list. An open Create key flow stays on its creation route with the new Team and resets the form and one-time secret state. If the current workspace is unavailable in the new Team, navigation returns to Overview.
- Collapse the sidebar when you need more space. Every destination keeps an icon and accessible name. On narrow screens, use the menu button to open the modal navigation drawer. Keyboard focus stays inside it; Escape dismisses it. Following a destination closes it, including navigation that changes only the query.
Overview is a direct destination for every Organization member. Capabilities determine Access (Virtual keys, Models & tools, Connect a client), Observe (Requests, Traces, Sessions, Usage), Build (Agents), and Manage (Teams, People & access, Budgets, Approvals, Audit, Settings). My connections is in the account menu and contextual Chat setup; Connect a client is also part of Team and virtual-key setup. Consumers see Chat from available deployments or owned history without gaining technical permissions.
Select Account menu beneath your identity at the bottom of the expanded sidebar to reveal My connections, Account access, Documentation (when configured), and Sign out. The menu starts closed to leave room for navigation. With keyboard focus on Account menu, press Enter or Space to toggle it; Tab reaches its actions. Escape closes the open menu and returns focus to Account menu. Following a link or changing the page or Team context closes it. The collapsed sidebar keeps these actions as direct icons with accessible names. On short screens, the open account actions scroll within the footer.
The header marks People & access, Identity, Settings, Account, My connections, Chat, catalog pages (Models & tools and Connectors), and Approvals with Organization-wide page · Team selection retained. These pages are not filtered by the selected Team. They keep their own permission and ownership rules; the Team selection remains available when you return to a Team-scoped destination.
Context selection never grants authority. An inaccessible or cross-Organization Team produces an unavailable state without revealing its name. A selected Team missing one reporting permission leaves that panel restricted; it does not widen the panel to the Organization. Use Overview for metric coverage and time-window definitions. These context changes require no new sign-in, key, restart or configuration activation.
Teams and roles¶
Select one explicit Team for technical work. Human roles authorize management, while virtual-key policy authorizes inference. Access, Observe, Build and Manage appear only for your current capabilities. A consumer with an available Chat deployment or owned history sees Chat without gaining technical navigation or Team metadata.
The eight presets and bounded custom roles are described in Roles. Joining a Team creates an exact membership instance; ending it invalidates its user keys, and joining again does not revive them. Ask for the exact capability through Get access.
Sign out¶
Open Account menu at the bottom of the navigation and select Sign out. In the collapsed sidebar, use the Sign out icon directly. The console returns to Sign in only after sign-out is confirmed; request a new magic link, or select Continue with GitHub where it is offered, to sign in again. If sign-out fails, you stay on the current page, see an inline retry message, and can select Sign out again. The account menu reopens to show the error if you closed it while the request was pending.
Recover from common sign-in failures¶
| Symptom | Recovery |
|---|---|
| Email and sign-in buttons are temporarily disabled | The sign-in and invitation forms enable when the page is ready for input. If they stay disabled, reload the page and check that your browser allows JavaScript for the Console. |
| No message arrives | Confirm the exact invited email, check spam, and ask an admin to verify SMTP or the invitation list. Do not repeatedly request links past the rate limit. |
| Link expired | The sign-in page says the link has expired or was already used; request a new one. |
| The email address on that GitHub account has not been invited to an organization. | The GitHub account's primary address holds no invitation. Ask an owner or admin to invite that exact address, or sign in with the address you were invited with. |
| That GitHub account has no verified primary email address. | Verify a primary address on GitHub, or use a magic link instead. |
| We can't connect GitHub to your account yet. | Sign in once with a magic link. GitHub attaches to your account from that point on. |
| GitHub sign-in did not complete. | The authorization round trip failed or was cancelled. Try again, or use a magic link. |
| Your organization provisioned this account through single sign-on. | Your organization's directory manages this address. Select the Continue with button for your organization's identity provider; magic links and GitHub do not sign in directory-provisioned accounts. |
| Signed in but no organization appears | The sign-in page explains that the account is not yet a member; open the invitation email and select Accept invitation. |
| Invitation expired | Ask an owner or admin to send a new invitation. |
| Invitation opens but no organization appears | Sign in with the invitation's email, reopen the invitation URL, and select Accept invitation. |
| Your session expired. Reload the page to sign in. in a chat | Your session ended; reload and sign in again. If an administrator suspended you, sign-in fails until you are reactivated. |
| A page says This page isn't available | Your roles do not include it. Ask an administrator or a Team administrator for the role; changing the URL cannot elevate access. |