As I'm developing an agent that performs record DML and queries of records the current(human) user has access, but will be returned when trying from the agent interface? Whose access is applied in this scenario?
#Agentforce
,
The short answer: it depends on whether the channel your agent is deployed on requires an authenticated Salesforce session — not on the agent type itself, though the type strongly correlates with it in practice.
1. Authenticated channels (Lightning Experience/Mobile, internal Slack, an internal portal where the user is logged in) — the agent runs in the context of the logged-in human user. Your normal Salesforce access controls apply exactly as they would if the user clicked around manually: profile/permission set object & field-level security, sharing rules, role hierarchy, OWD. Whatever that user can query or DML, the agent can — nothing more, nothing less. If you're testing from the Agentforce panel inside Lightning while logged in as yourself, your own access is what's being applied.
2. Unauthenticated channels (public Messaging, embedded chat widgets, email) — there's no human session to inherit from, so Salesforce falls back to a dedicated Agent User: a special integration-type Salesforce user (License: Einstein Agent, Profile: Einstein Agent User) that you configure explicitly in Agent Creator. Here, the agent user's
permission sets, field-level security, and sharing access govern everything — completely independent of what the anonymous customer typing into the chat could see.
Hope this helps.
