Skip to main content

 Hi everyone, I'm working through the "Use Employee Agents to Get Work Done" module (specifically the "Help a Guest Out of a Soggy Situation" unit) as part of the Agentblazer Champion 2026 trail, using the Agentforce Playground provided by Trailhead for this badge. While trying to activate the Coral Cloud Agent (Employee type) in Agentforce Builder, I get this error: "Looks like you don't have access to agent templates associated with the Employee agent type. Make sure that you have the required permissions for the type and try again." When I investigated further, I found that my user (System Administrator profile, User License = Salesforce) is missing the "Use Custom Agents" permission. When I try to enable it via a Permission Set, I get this additional error: "Can't save permission set Access Agents, which is assigned to a user with user license Salesforce. The user license doesn't allow the permission: Use Custom Agents." The User License field is locked/not editable on the user's Edit page, so I can't change it manually. I confirmed I'm using the Agentforce Playground that Trailhead auto-provisioned for this specific unit (not a personal/generic playground), and the "Your Agentforce Playground Is Ready!" message appeared as expected before I started. Has anyone else run into this? Is this a known provisioning issue with the Agentforce Playground for this unit, or is there a step I'm missing to get the correct license/permission for Employee agent types? Any guidance would be appreciated — thanks in advance!  

 

#Agentforce

2 个回答
  1. 今天,17:05

     Hi @Rohit .

     

     

    This appears to be related to the provisioning of the Agentforce Playground and the User License assigned to the user. The “Use Custom Agents” permission is license-dependent, so if the Salesforce User License doesn’t support it, the permission cannot be added through a Permission Set.  

     

    Since you’re already using the Agentforce Playground provided by Trailhead, I’d recommend relaunching the Playground from the unit and verifying that the org is freshly provisioned. If the same error persists, it may be a Trailhead org provisioning issue rather than a configuration issue.  

     

    Hope this helps! 

0/9000