Setup with Agentforce (Beta): An Admin's Honest First Look
Setup with Agentforce (Beta): An Admin's Honest First Look
If you've spent any real time clicking through Salesforce Setup, you already know the feeling. You need to freeze a user, check who has access to a custom object, and fix a broken formula field before the end of the day. Fifteen browser tabs later, you're still hunting for that one permission set. I've been there more times than I want to admit.
Setup with Agentforce (Beta) is Salesforce's answer to that daily grind, and after spending a couple of weeks poking at it in a sandbox, I think it's one of the most interesting admin features to land in years. Not because it's flashy, but because it actually saves clicks on the stuff you do every single day.
This post walks through what Setup with Agentforce actually is, what it can do right now in beta, how to turn it on, and a few honest caveats I've run into. If you're an admin wondering whether it's worth enabling in your org, read on.
What Setup with Agentforce Actually Is
Let's get the definition out of the way first. Setup with Agentforce is a new AI assistant built directly into the Salesforce Setup menu. You chat with it in natural language, and it either answers your question, shows you the relevant Setup page, or offers to make the change for you.
It's different from the regular Agentforce agents you might build for customers or employees. This one is purpose-built for admin work. Think of it less like a chatbot and more like a junior admin sitting next to you who knows the entire Setup tree by heart and can answer questions like "does Emily White have access to accounts?" without you having to click through five different screens.
The agent always asks for your confirmation before making changes, it only works within the permissions you already have, and every action gets logged in the Setup Audit Trail. Those three things matter a lot, because they're the difference between a helpful tool and a compliance nightmare. If you've been tracking Salesforce terminology across all these AI releases (subagents, Agent Script, Atlas Reasoning Engine, and so on), the good folks at salesforcedictionary.com keep an updated glossary that's been useful for me when I need to explain the new vocabulary to stakeholders.
What It Can Actually Do Right Now
Beta features always come with a gap between the marketing copy and what actually works. Here's what I've confirmed works well so far, based on Salesforce's documentation and my own testing.
User management. You can ask it to clone users, freeze users, or pull a list of users with a specific permission. Something like "show me all users with the System Administrator profile who haven't logged in for 30 days" returns an actual list you can act on. That alone saves me a trip to a reporting tool.
Access troubleshooting. This is the killer feature in my opinion. "Why can't Marcus see the Opportunity record for Acme Corp?" is the kind of question that normally takes ten minutes of digging through sharing rules, role hierarchy, and permission sets. The agent walks through the access chain and tells you where the block is. Even if you have to verify the answer manually, it gives you a starting point that's usually correct.
Data model changes. You can ask it to create custom objects and fields. It'll suggest existing fields that might already cover your need before creating new ones, which is a nice touch because we've all seen orgs littered with three different "Customer Status" fields from different eras.
Permission set management. Creating and managing permission sets and permission set groups is supported. I found it handy for quick questions like "which permission sets grant access to the Contract object?"
Flow and Lightning page help. It can create Flows and Lightning pages, though I'd still use the regular builders for anything complex. For simple scaffolding it's fine.
Formula troubleshooting. If you paste a broken formula, it'll usually tell you what's wrong. I've tested this with a few nested IF statements that had mismatched parentheses and it caught them quickly.
One thing it does not replace is actually knowing your org. It's a co-pilot, not autopilot. More on that later.
How to Turn It On (Prerequisites and Setup)
Getting Setup with Agentforce enabled takes a few steps, and there are prerequisites that trip people up.
You need to be in Lightning Experience on Enterprise, Performance, Unlimited, or Developer edition, and you need either the Foundations or Agentforce 1 edition. Production, sandbox, or developer orgs all work, so you don't have to break anything in prod on day one.
Here's the prerequisite list I wish someone had handed me:
Data Cloud has to be set up in your org. This catches people out because a lot of admins don't realize Data Cloud is required for Agentforce features to work properly. You don't need a massive Data Cloud deployment, but the foundation has to be in place and admins need access to the default data space.
Generative AI has to be enabled. In Setup, search for Einstein Generative AI and flip it on. You'll need to agree to the terms.
Agentforce itself has to be enabled. This is a separate toggle from generative AI.
Once all three are in place, go to Setup, search for "Setup with Agentforce (Beta)," and enable it. The agent shows up as a chat icon in the Setup header. Click it, and you're in.
If you run into issues, double check that your user has the Agentforce Assistant User permission set. Salesforce's Help docs are decent here but assume you already have Data Cloud humming along, which isn't always the case.
Real Use Cases Where It Shines
Let me share the specific scenarios where Setup with Agentforce has already earned its keep for me.
The "new hire access ticket" problem. Every Monday I get tickets asking why a new rep can't see certain records. Instead of opening the user, checking their profile, checking their role, checking sharing settings, checking each relevant permission set, and then checking sharing rules, I ask the agent. It usually nails the answer in seconds. Even when it doesn't, it narrows the problem down enough that I can finish the job quickly.
The "audit request" scramble. When compliance asks who has access to a sensitive object, I used to build a report or run some SOQL. Now I just ask. "List all users with read or edit access to the Compensation custom object." Done. I still spot-check the answer, but the first pass is free.
The "field cleanup" project. If you've ever inherited a Salesforce org from three previous admins, you know the joy of trying to figure out what a field called "Status2__c" actually does. The agent can summarize what's on a field, where it's used in Flows, and whether any Reports reference it. It doesn't replace tools like Salesforce Optimizer or field utilization reports, but for a quick look, it's faster.
The "what's this Setup page called again" moment. I've been an admin for years and I still sometimes forget where a specific setting lives. "Where do I configure the login IP range?" takes me straight there. For newer admins, this kind of navigation help is probably the biggest productivity gain of all.
Learning new features. The agent can summarize Salesforce Help articles and walk you through setting up features you've never touched. I used it to get a refresher on Experience Cloud guest user sharing rules and it was faster than reading three separate Help articles.
The Honest Caveats
This wouldn't be an honest review if I didn't call out what's rough.
First, it's beta. Things break, responses are sometimes wrong, and the UI changes between releases. Don't assume it's production-ready for every scenario. Always verify changes in a sandbox before doing them in prod, and don't let the agent make bulk changes without human review.
Second, the quality of answers depends heavily on how specific your prompt is. "Fix my permissions" gets you nothing useful. "Add read access to the Contract object for the Sales Reps permission set, but only in the Commercial business unit" gets you something actionable. The Salesforce Admins team said it best in their launch post: the more specific you are, the faster and better the result.
Third, the Data Cloud prerequisite is a real barrier for some orgs. If your company hasn't turned on Data Cloud yet, enabling Setup with Agentforce means talking to procurement and architecture first. That's not necessarily bad, since Data Cloud unlocks a lot of other capabilities too, but it's a planning item, not a weekend project.
Fourth, it doesn't handle everything. Complex automation logic, Apex code review, and integration setup are still better done the traditional way. The agent is best at Setup tasks that have well-defined answers, not open-ended architecture work.
Finally, watch out for vocabulary confusion. Salesforce renamed "topics" to "subagents" in the Agentforce 360 release, and I've seen people get tangled up explaining the difference between Setup with Agentforce, Agent Builder, Agent Script, and Agentforce Voice. If you're presenting this to your leadership, it's worth spending an hour upfront getting the terms straight. The glossary at salesforcedictionary.com is a decent reference if you want a quick rundown of all the Agentforce terminology without reading through ten different release notes.
Should You Enable It This Week?
If you're on a supported edition and already have Data Cloud running, yes, turn it on in a sandbox today. Play with it for a week before deciding whether to enable it in production. The learning curve is shallow, and the daily time savings add up fast.
If you're not on Data Cloud yet, I'd still recommend keeping Setup with Agentforce on your radar because it's clearly where Salesforce is investing. It's showing up on the updated Admin certification exam, it's getting new capabilities every release, and the general vibe from Trailblazer community conversations is positive. Worth following even if you can't enable it right now.
Setup with Agentforce isn't going to replace skilled admins. What it does is take the most tedious parts of the job and make them faster. That's a good trade, and I'm curious to see where it goes by Summer '26.
Have you tried Setup with Agentforce yet? Drop a comment with your favorite use case, or the thing you wish it could do but doesn't. I'm collecting real-world examples for a follow-up post and would love to hear what's working in your org. For a running glossary of Agentforce terms that keeps pace with every release, salesforcedictionary.com has been my go-to bookmark.