Skip to content

Use Your Own Account with a Connector

Purpose

Some Connectors act as the person calling them rather than as the company. On such a Connector, a tool call runs with your own upstream account: the records it reads and the actions it takes are the ones you are allowed upstream, and every decision names you as the credential owner. My connections is where you connect that account once, see whether it is still connected, and disconnect it.

A Connector runs in one of two per-user modes, chosen by an administrator:

Mode What you provide How you connect
Per-user OAuth A sign-in with your own account at the upstream service Connect opens the upstream consent page in your browser.
Per-user headers Header values only you hold, such as a personal token Enter one value per declared header and select Save.

Nobody else can use what you connect: another person calling the same tool is asked to connect their own account, an ordinary service account has no personal grant, and administrators see how many people connected, never what they connected with.

Prerequisites

  • An active real user session and current eligibility through an allowed ordinary user key, a permitted Team development path, or an available Chat deployment requiring this person's connection. Consumer Chat eligibility does not require Team membership. Management tokens cannot impersonate personal connection setup.
  • For per-user OAuth: an account at the upstream service and a browser that can reach both the Console and that service.
  • For per-user headers: the values the upstream service issued to you. They are stored encrypted by the gateway and are never shown again after you save them.

Procedure

  1. Open My connections from the account menu or contextual Chat link. Each per-user Connector has one card with its status: Not connected, Connecting, Connected, Needs authorization, Temporarily unavailable, or Orphaned.
  2. For a per-user OAuth Connector, select Connect. Sign in and approve at the upstream service; you return to My connections with the card highlighted and Connected. Select Reconnect later to replace the grant, or Disconnect to remove it.
  3. For a per-user headers Connector, enter a value for every declared header name and select Save. The card turns Connected. Select Remove to delete the values; saving again replaces them.
  4. Call the tool as usual, from Chat, from an AI client such as Claude Code, or with a personal key. The call now runs with your account.
  5. When a tool answers Connect your Connector account in Mission Control to use this tool with a link, follow the link: it opens My connections with that Connector's card highlighted. In Chat the tool card shows This tool uses your own account. with a Connect link.

Expected result

A tool call on a per-user Connector uses your own credential and nothing else. Mission Control never substitutes the company's credential, the administrator's discovery credential, or another person's grant. Before you connect, and after you disconnect, the tool answers in band with a connect request instead of running: the response is a successful HTTP call whose result is marked as an error and carries the Console link. Nothing reaches the upstream service in that case.

Personal OAuth grants are refreshed by the gateway like the company's; expiry and granted scopes are shown on the card. Personal header values travel only on your own calls, exactly as you entered them.

A managed deployment uses your grant only for a saved per-Connector Each person's own account requirement and the actual initiating person. Company account uses the exact configured company binding. There is no global person-connections switch, fixed employee fallback or customer-label impersonation.

Verification

  • Your card reads Connected and, for OAuth, shows the granted scopes and an expiry.
  • A call to the tool succeeds, and its decision under Observe → Requests records you as the credential owner.
  • A colleague calling the same tool without connecting receives the connect request, not your data.
  • After Disconnect or Remove, your next call receives the connect request again.

Failure recovery

  • The card reads Not connected after you were suspended or deactivated: suspension deletes your connections along with your keys, and reactivation does not restore them. Connect again.
  • Orphaned: your grant is kept but unused after eligibility ends. Restore a permitted key/Team development path or Chat audience requirement, or Disconnect to discard it.
  • Needs authorization: the upstream service revoked or narrowed the grant. Select Reconnect.
  • Temporarily unavailable: the gateway could not read or refresh the grant. Try again shortly; an administrator checks the gateway's keyring and the upstream service.
  • The upstream consent page rejects the sign-in: check the account you used; an administrator checks the Connector's registered client and allowed origins.
  • The values were not accepted: enter every declared header without control characters and within the size limits; the names are fixed by configuration.
  • The Connector is missing from My connections: it is not a per-user Connector, it is disabled, or no current key, Team development or available Chat path authorizes it.