Salesforce Agentforce
In short: employee-facing Agentforce custom actions run as the user submitting the prompt. Service-agent actions run as the agent. Custom actions must enforce object, field and record access. CLI-generated agent users lack passwords and cannot sign in. Match each action's execution identity to the access checks it actually applies.
What does Salesforce Agentforce already give you for agent identity?
- Employee-facing custom actions execute as the user submitting the prompt. Salesforce: Secure Agentforce custom actions, read 2026-11-03
- Service-agent custom actions execute as the agent. Salesforce: Secure Agentforce custom actions, read 2026-11-03
- Custom actions must enforce CRUD, field-level security and record-sharing checks. Salesforce: Secure Agentforce custom actions, read 2026-11-03
- CLI-generated agent users receive the Einstein Agent User profile. Salesforce: Create an agent user, read 2026-11-03
- CLI-generated agent users have no password and cannot log into Salesforce. Salesforce: Create an agent user, read 2026-11-03
- Only administrators can view or edit an agent user in Setup. Salesforce: Create an agent user, read 2026-11-03
Where is the gap?
Review each custom action for access checks under its actual execution identity. Agent registration does not establish approval for risky record changes.
Which key results usually apply?
Which products fit?
| Product | Fits when |
|---|---|
| Okta for AI Agents | Most of your people sign in through Okta. |
| Astrix Security | You do not know how many agents exist or who owns them. |
| NewCore | You need a named person to approve risky agent actions before they run. |
Questions buyers ask
Do all custom actions use the prompting employee?
No. Salesforce documents employee-facing actions using the prompting user and service-agent actions using the agent identity.
Can a generated agent user log in?
The CLI documentation says the generated agent user has no password and cannot log into Salesforce.
Which checks do custom actions need?
Salesforce requires CRUD, field-level security and record-level sharing checks.