Hey,
quick question - i have a problem to finish my agentblazer challenge - i have lauunch my playground but when i try to laynch Agentforce Studio it says i am not allowed to use to so i can't continue.
Can somebody helo with that ?
Thanks
#Trailhead Challenges
Hey Dominika,
Based on Trailhead's own setup instructions for this challenge, here's the exact path that should work:
1. In Setup, Quick Find box, search for and select Salesforce Go
2. In the Search features box (the box on the Salesforce Go page, not the main Setup search), search for and select Agentforce Studio
3. Click Get Started, then click Turn On
That "Turn On" step is what actually enables Einstein Setup and Agentforce Agents for the org — without it, Agentforce Studio stays locked (matches the lock icon you're seeing next to the title in your screenshot).
If you click through this and still get a "not allowed" message, it's usually one of these:
1. You're not logged in as System Administrator in this playground/org. Double-check your user profile — Agentforce Studio setup requires admin-level access, and a limited/custom profile won't be allowed to turn it on.
2. Wrong org type. This specific challenge needs a Developer Edition signed up specifically through the challenge's own signup link (the one embedded in the Trailhead module), not a generic Trailhead Playground or a Developer Edition from the general signup page. If you created a playground through the normal "Launch" button rather than following the specific Connect Org flow the module describes, it likely doesn't have the Agentforce entitlement provisioned.
3. Trail sequencing lock. Some of the 2026 Agentblazer trails are locked until you've completed the prerequisite trail in order (e.g., Agentblazer Champion before Innovator). If this challenge sits inside a later trail, worth confirming you've completed the earlier one first — Trailhead can block trail progress even if the org itself is fine.
Given your screenshot shows you already made it to the Agentforce Studio page itself (just with the lock icon), I'd guess it's #1 or #2. If you signed up for a fresh Developer Edition specifically through this module's signup link and you're logged in as the admin user from that signup, but still hit "not allowed" on Turn On — that would point to a provisioning gap worth escalating to Trailhead Help directly, since that combination shouldn't happen per the documented flow.
