From 93a47c7948cb07e361538fec40236837e8ca033b Mon Sep 17 00:00:00 2001 From: npiccolo <64094541+npiccolo@users.noreply.github.com> Date: Thu, 7 May 2026 15:01:40 -0300 Subject: [PATCH] Update skills/developing-agentforce/references/agent-user-setup.md Co-authored-by: Steve Hetzel --- skills/developing-agentforce/references/agent-user-setup.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/skills/developing-agentforce/references/agent-user-setup.md b/skills/developing-agentforce/references/agent-user-setup.md index a509620..d8649d9 100644 --- a/skills/developing-agentforce/references/agent-user-setup.md +++ b/skills/developing-agentforce/references/agent-user-setup.md @@ -94,7 +94,8 @@ sf agent activate --json \ Critical notes: - `sf org create agent-user` works in **all org types** (scratch, sandbox, production) — use it instead of the legacy `sf org create user` or `sf data create record` approach -- The command auto-assigns `AgentforceServiceAgentUser` — no separate permset assignment needed +- The command auto-assigns `AgentforceServiceAgentBase`, `AgentforceServiceAgentUser`, and `EinsteinGPTPromptTemplateUser` — no separate permset assignment needed +- The command may exit non-zero with `PermissionSetAssignmentError` if a permset license is exhausted, **even when the user was created successfully**. Always inspect `result.username` and `result.permissionSetErrors[]` from the JSON output. If the only failure is `EinsteinGPTPromptTemplateUser` and your agent has no Prompt Template actions, you can proceed. Otherwise, free a license (or use `--base-username` to retry against a different license pool) before continuing. - Capture the generated username from the command output (`result.username`) and use it for `default_agent_user` - Always test with preview BEFORE publishing to avoid version management overhead - Assign any custom permission sets (`{AgentName}_Access`) BEFORE publishing to prevent "Internal Error"