AI Agents35% of the exam
Agent user, run context and private actions
Whose permissions an agent uses: the Service agent's agent user, the logged-in user for Employee agents and authenticated site users, flow and Apex run context inside actions, and how verified IDs, session identifiers and filters keep private actions scoped to one customer.
Explain the security context in which the agent is actually running, and how it impacts agent action execution.
~7 min read · 18 practice questions ·
What the exam expects
- Identify the user an agent runs as: the agent user for a Service agent with unidentified or verified customers, the logged-in user for an Employee agent or an authenticated site user.
- Configure an agent user with least privilege and fix permission errors when an action reaches a new object.
- Predict what a flow-backed or Apex-backed action can read and change from its run context.
- Secure private actions: identify the customer per messaging configuration, scope queries with session or verified IDs, and gate actions with filters.
- Key terms: agent user (the dedicated EinsteinServiceAgent User a Service agent runs as); run context (user or system context that decides a flow's access); private action (an action that reads or changes one customer's data); VerifiedCustomerId (the variable the Customer Verification subagent, formerly topic, fills after verification); context variable (session data such as MessagingSession.ContactId that identifies but does not restrict); AuthSession (the authenticated session an Experience site login provides).
Key facts
Employee agent identity
- Detail
- Runs in the logged-in user context
Service agent default identity
- Detail
- EinsteinServiceAgent User, Einstein Agent license and profile, minimal access
Where to grant agent user access
- Detail
- [Agent_Name]_Permissions permission set, plus a role and sharing rules
Who can edit an agent user
- Detail
- Only users with admin permissions
Flow-backed action requirements
- Detail
- At minimum, Run Flows plus access to objects used in the flow; flow's FLS and sharing apply
Record-triggered flow context
- Detail
- System context without sharing
Enforcing user context
- Detail
- Screen and autolaunched flows, API 68.0 and later
Flow called from Apex
- Detail
- Always ignores object and field-level access
External-app verification
- Detail
- Identifier saved to MessagingEndUser; no AuthSession, valid until token expiry
Verified ID storage
- Detail
- Customer Verification subagents store it in VerifiedCustomerId
Sources for this section (6)
- Employee Agent Templatehelp.salesforce.com (opens in a new tab)
- Configure Service Agent Accesshelp.salesforce.com (opens in a new tab)
- Create a Custom Actionhelp.salesforce.com (opens in a new tab)
- Flow Run Contexthelp.salesforce.com (opens in a new tab)
- Set Flow Run Contexthelp.salesforce.com (opens in a new tab)
- Add User Identificationhelp.salesforce.com (opens in a new tab)
- Why does OTP verification not change whose permissions govern access?
- When does a user-context flow behind an action run with system access anyway?
- Why can't an authentication passed by User Verification from an external app be revoked immediately?
- Which permission does the identity running a flow-backed action need?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Agentforce Specialist pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 26 lessons of the Agentforce Specialist guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (18 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams