for the running user, the Fulfiller agent-configure skill's Phase 6
activate
call returns
HTTP 200
with a silent
{success:false, messages:[{... "does not exist"}]}
body and the agent never becomes usable. This skill fixes that gap by assigning the correct Fulfiller persona permset (and its backing license when one exists) —
or
, when no Fulfiller persona permset is provisioned on the org at all, hands off to the Agentforce Studio configure/validate skill so the ITSM AddOn(s) can be enabled first.
The three Fulfiller persona permsets, their AddOns, PSLs, and the userPerms they grant are documented in
references/permset-topology.md
. All are Core-shipped in namespace
force
— there is no managed-package namespaced permset for this feature.
Employee agent is out of scope.
The Employee NGA agent's access model is separate (org-preferences + a different persona layer) and does not map onto these three persona permsets.
Every call runs through the
Salesforce CLI (
sf
)
:
sf api request rest
— authenticated Connect API GET (identity, verify read).
sf data query
— SOQL on
PermissionSet
(persona presence),
PermissionSetAssignment
/
PermissionSetLicenseAssign
(idempotency).
sf org assign permset
— assigning the permission set for the running user.
No token is ever extracted; no MCP is used.
Scope
In scope
detecting which of the three Fulfiller persona permsets (
IncidentFulfiller
,
ProblemFulfillerPermSet
,
ChangeRequestFulfillerPermSet
) are provisioned on the org, letting the user pick which persona to assign, checking existing assignments, assigning the permission-set license (when the persona is license-gated) and permission set to the running user (or a named user), verifying the target
svc_itsm_intelligence__*
invocable actions surface via a follow-up
/actions/custom/generatePromptResponse
read.
Out of scope
Employee-agent access (different access model, different skill), installing/enabling the ITSM AddOn(s) or content bundle (hand off to
service-itsm-agentic-setup-agentforce-studio-validate
), enabling org-level Agentforce feature toggles, creating a permission set, creating or activating the Fulfiller agent (that's
service-itsm-agentic-setup-fulfiller-agent-configure
), CMDB access (
service-itsm-agentic-setup-cmdb-access-assign
), generic non-ITSM permission-set assignment (
dx-org-permission-set-assign
).
Show more
Installs
1.0K
Repository
forcedotcom/sf-skills
GitHub Stars
956
First Seen
13 days ago
Security Audits
Gen Agent Trust Hub
Pass
Socket
Pass
Snyk
Pass