You are here:
User-Level Authentication in Multi-Agent Solutions
Agentforce multi-agent solutions support user-level authentication. Authentication varies by agent type and by the combination of orchestrator agent and connected subagent.
Agentforce multi-agent solutions support user-level authentication. Authentication varies by agent type and by the combination of orchestrator agent and connected subagent.
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions. Required add-on licenses vary by agent type. |
| Orchestrator Agent | Connected Subagent | Authentication |
|---|---|---|
| ASA | ASA | For ASA, a connected subagent runs as the orchestrator agent's session user (the digital user), not as its own agent user. After a customer logs in to the ASA orchestrator, the platform passes that identity through the authenticated session. You can't change the connected subagent's running user with an access element, a variable, or a linked variable. Unauthenticated guest users are also supported. |
| AEA | AEA | AEA connected subagents run in the logged-in user's context. The user must be logged in beforehand. Variables such as currentUserId aren't available in this context, which is by design for security reasons. |
| AEA | ASA | An ASA connected subagent runs as its own agent user, not in the logged-in user's context. Configure the ASA agent user with the permissions required to perform its actions. |
For AEA, assign the logged-in user the permissions required for any operation the connected subagent requests.
An ASA orchestrator with AEA connected subagents isn't supported in this release.
For additional information, see:

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.