Sign in & accounts
Every way into Wingman, on every surface: SSO for organizations, email and password everywhere else, and one session that follows you through the whole app.
Wingman has one account and several doors. Which doors you see depends on your deployment: Axelera employees use Microsoft SSO, customer organizations use their own identity provider, and other deployments offer email and password or OAuth. Whichever door you use, you sign in once — Chat, Agent Dev, the dashboard pages, and your connected AI CLIs all ride on the same session.
Sign in with Axelera SSO
Axelera employees: sign in with one click
Click Continue with Axelera SSO
Before sign-in, Wingman Home shows Sign in required. The Continue with Axelera SSO button is the only step between you and both modes.
Let the browser approve
Your browser opens and Microsoft Entra accepts the session automatically. No passwords are typed inside the app.
You are in — everywhere
Wingman returns signed in: Home shows your account, and every surface uses the session. Opening Chat can show a one-time confirmation page — click Continue to enter chat as your SSO user. If it expires, go back to Home and open Chat again.
Customer organization SSO
Customer organizations: sign in with your own SSO
Customer organizations get the same one-click flow with their own identity provider: a single Continue with SSO button on Wingman Home and on the web chat, backed by your company Entra tenant. If the button shows as unavailable, your identity provider is not connected to this deployment yet — ask your admin or Axelera contact. There is nothing to fix on your machine. Admin setup lives in Security & admin under Identity & SSO for organizations.
Other ways to sign in
| Sign-in path | How it works | Good to know |
|---|---|---|
| Email & password | Enter your email and password on the sign-in form. | For deployments without enforced SSO. |
| Create account | Sign up with your email, then confirm it from the message Wingman sends. Sign-in unlocks after confirmation. | No confirmation email? Check spam, then retry the sign-up form. |
| Forgot password | Sends a password-reset link to your email. | Blocked when your organization enforces SSO — your identity provider owns the password, so reset it there instead. |
| OAuth providers | Continue with GitHub, Microsoft, or Google where the deployment enables them. | Uses that provider’s own browser sign-in; there is no separate Wingman password. |
| Continue as guest | Skip sign-in and explore with a local guest session. | Not offered when your organization requires SSO. Guest work stays on the machine and is not tied to an account. |
Lock, sign out, and switch
Step away and Wingman can show a lock screen: unlock to continue as yourself, or switch to a different account from there.
Signing out does a full sweep. It clears the app session, the provider sessions behind it, and the connections your AI CLIs made through Wingman — the next person at the machine starts clean. On the web chat, sign out from your profile menu; to change sign-in method or SSO provider, sign out first, then pick the other door on the sign-in page.
Accounts menu and session sync
The desktop shell treats Wingman as a real VS Code account. It appears as Axelera Wingman SSO in the Accounts menu, and the status bar shows Login when signed out and your account when signed in. The status bar menu has two actions: Sync Authentication refreshes the session across every panel, and Sign Out ends it. If one panel looks signed out while Home looks signed in, Sync Authentication is the fix.