Execution identity by agent type
Key Takeaway
Employee agents run as the logged-in end user, Lead Nurturing agents run as the EinsteinSDRAgent User, and Service agents run as the EinsteinServiceAgent User unless credential-based user verification lets them run as the logged-in site user.
Every Agentforce agent runs its actions as some Salesforce user. That user's profile, permissions, field-level security, and sharing rules decide what data the agent can read and change. Which user that is depends on the agent type and, for a Service agent, also on how well the customer is identified.
What an agent's execution context is
An agent's execution context is the user it runs as. The agent's actions and responses inherit that user's profile, permissions, field-level security, and sharing rules.
The execution context depends on three things:
- The agent type
- The channel
- Whether credential-based user verification is enabled