Sessions, access and support

Review browser sessions, MCP clients and issued API keys, and get help.

Open the account menu and choose Sessions & access. This page is account-wide:

  • Browser sessions lists Better Auth browser sessions and lets you revoke them.
  • Arc0 MCP clients lists your runtime MCP authorizations.
  • Management MCP clients lists the organization-management grants you authorized.
  • Your API keys lists the project keys you issued in organizations where you are still a member, including their visible prefix, expiry and revoke action. Full secrets are never returned here.

Revoking an MCP authorization also revokes its associated OAuth tokens. A client can ask you to authorize again later. Business API keys belong to their organization and survive sign-out; revoke the specific key explicitly to stop it. Organization owners and admins can also offboard an issuer and their delegated keys from project settings. Revoking a browser session does not replace explicit API-key revocation.

The account-key endpoints are cookie-authenticated GET /v1/account/keys and DELETE /v1/account/keys/:id. They show and revoke only keys issued by the signed-in user. Listing requires current organization membership. After leaving an organization, you can still revoke your own key by its known ID as a kill-switch; this does not list former organizations or grant access to their resources. Existing MCP revoke endpoints remain unchanged.

End-user connection health

Embedded projects show per-user active, expired, failed and inactive connection counts and last execution activity under End users. Filter by a health state to show users with at least one owned connection in that state. Users with no connections appear under All health with zero counts.

Revoked or revoking connections are inactive. Other connections past their recorded credential expiry are expired. Remaining reconnect-required connections and active connections with at least five consecutive refresh failures are failed. The remaining connections are active. These are health indicators; they do not change admission, refresh behavior or policy. Shared group accounts are not counted as owned connections. Last activity is the latest execution's finish, start or creation time; users without executions have no last activity. The API accepts health=active|expired|failed|inactive on GET /v1/users and returns the counts with each user.

Help & support

Choose Help & support in the account menu for concise troubleshooting, documentation, service status and contact links. Contact support opens the existing Gleap widget when configured. If the widget is unavailable, use the contact form. The widget is never initialized or opened on hosted /connect pages or sensitive auth/capability pages. The service-status link points to the documentation URL selected by the Arc0 team, https://arc0.ai/docs. A deployment can override it with VITE_STATUS_URL.

Copy project support identifiers

Open Project settings and choose Copy project ID for the current project identifier. Copy debug bundle copies JSON with only the project ID, organization ID, your membership ID and the console app version. Review or share it with support as needed. The button waits for your membership to load, and clipboard failures are reported on the page. The bundle contains no credentials, connection settings or browser-session data.

On this page