Configure multi-profile support
This page is for platform operators who administer an Arcade organization. It shows how to turn multi-profile support on or off in the Arcade Dashboard, what users and agents get while it’s off, and what changes when you turn it back on. Use it before your users connect more than one at a provider, or before you turn the feature off for an organization that already uses it.
Multi-profile support is a setting on each organization. It applies to every project and every Gateway in the organization. It’s off by default.
Prerequisites
- The organization admin role. Only organization admins can change the setting.
Turn it on in the Dashboard
- Open the Organization page (opens in new tab) of the Arcade Dashboard.
- Find the Multi- support card. It lists the providers that support more than one profile.
- Turn on the switch.
Arcade saves the change when you flip the switch. There’s no separate save step. calls can take a few minutes to pick up the change.
To turn multi- support off, turn off the same switch.
Once it’s on, users can connect more than one at Google, Microsoft, Microsoft Power BI and Slack, and gateways whose use these providers offer the argument and tools listed in What an MCP client gets. When a user has two or more profiles for a provider, must name the one each call runs on. See How a tool call picks a profile.
What happens when you turn it off
Turning multi- support off never deletes connections. keep every profile they connected.
While it’s off:
- Each tool call runs on the user’s oldest for the provider, even when the user has several. don’t need to name a profile.
- Agents can’t choose another . definitions no longer show
arcade_profile_id. A call whosearcade_profile_idnames the profile it runs on anyway still runs. Any other value is refused withunavailable_profile, and the refusal tells the to call the tool again without it. - Tool results no longer say which a call ran on.
System_ManageProfilesno longer appears, andSystem_ManageAuthorizationno longer takes theprofilesargument. Agents can’t check or authorize a named , or connect another one.
What happens when you turn it back on
- Every that users connected works again, and can name any of them in
arcade_profile_id. - Agents must again name a when the has two or more for the provider. A call that names none is refused with
connected_profile_required, and the refusal lists the user’s profiles. - Tool results name the each call ran on, and
System_ManageProfilesand theprofilesargument ofSystem_ManageAuthorizationcome back.
Check that it works
Connect an client to a gateway whose tools use Google, Microsoft, Microsoft Power BI or Slack, and list its tools. With multi- support on, the list contains System_ManageProfiles, and those offer an optional arcade_profile_id argument. On a gateway with Tool Recommendation on, arcade_profile_id shows on the tools that Arcade_SelectTools returns.
If the don’t offer arcade_profile_id:
- Confirm that the switch on the Multi- support card is on.
- Wait a few minutes, and list the again.
- Reconnect the client. Some clients cache the list from an earlier session.
Next steps
- Read Multi-profile support to see how agents name, list and connect .
- Read What’s not covered before you rely on profiles outside Gateways.
Last updated on
Overview
How multi-profile support lets each user connect more than one account at the same provider, and how agents on an MCP Gateway choose the account each tool call runs on
Manage Authorization
How System_ManageAuthorization lets an agent on an MCP Gateway check and request all the authorization a job needs in one step