Setup with Agentforce: An Admin's Honest First Look

Look, I've been admining Salesforce orgs for a long time, and I can tell you the Setup menu has not aged well. You know the drill. Someone pings you on Slack: "Hey, can Emily see that new Accounts list view?" Twenty minutes later you've clicked through three profiles, two permission sets, one permission set group, and you're still not sure. Spring '26 changed that conversation, and I wanted to write up what I've actually seen so far.

Setup with Agentforce went into beta with the Spring '26 release, and honestly, it's the most interesting admin feature I've touched in a while. It's not perfect. But the premise of just chatting with Setup instead of spelunking through menus actually works better than I expected.

What Setup with Agentforce Actually Is

Setup with Agentforce is an AI assistant embedded directly on the Setup home page. Instead of navigating through tabs, you type what you want in plain English. "Does Emily White have access to the Accounts object?" Or "Create a custom field on Opportunity called Renewal Risk with a picklist of High, Medium, Low." The agent figures out what Setup tools to pull up, shows you the relevant information, and if you're making changes, it asks you to confirm before it does anything.

It's in beta right now, which means you have to toggle it on manually. In Setup, search for "Setup with Agentforce" and flip the switch. Then refresh your browser. If you want other admins on your team to use it, you'll need to create a permission set with the "Use Setup with Agentforce" system permission and assign it to them. Standard pattern, nothing weird.

The Permission Audit Use Case

This is the one that sold me. Let me paint the picture. Someone in sales ops messages you because a specific user swears they can't see a particular opportunity. You go through the usual steps: check the user's profile, check assigned permission sets, check the role hierarchy, check sharing rules, check OWDs. Maybe there's a territory management rule involved. By the time you've traced it, thirty minutes are gone.

With Setup with Agentforce, I just type "Why can't Jake see Opportunity 0063k0000012345?" and the agent walks me through it. It checks object-level access, field-level security, sharing settings, and gives me a plain-English explanation of where the block is. Sometimes it's OWD, sometimes it's a permission set missing, sometimes it's a manual share that never got created. I still have to do the work of fixing it, but the diagnosis time drops from thirty minutes to about thirty seconds.

You can also ask questions like "Which users have the Customize Application permission?" and get a real list back. If you've ever been in a security audit and had to produce that report, you know how painful it usually is. If you need a quick refresher on what permissions like these actually mean, salesforcedictionary.com has solid definitions that new admins on my team have found helpful.

Creating Objects and Fields Without Clicking Around

The other workflow I use Setup with Agentforce for almost daily is data model tweaks. I used to dread requests like "can you add five fields to Contact for our new onboarding checklist?" because even simple field creation involves a lot of clicking. Object Manager, new field, type, label, length, help text, field-level security for each profile, add to the page layout.

Now I type something like: "On Contact, create five checkbox fields: Welcome Call Done, Docs Sent, Training Scheduled, First Login, 30 Day Check-in. Add them all to the page layout." The agent shows me what it's about to build, waits for my approval, and then does it. The confirmation step matters, because I've had moments where it misinterpreted what I wanted (once it tried to create the fields on Lead instead of Contact because my phrasing was ambiguous). But that's fine, you just say no and rephrase.

It handles formulas too, which is where I've had the most fun. "Fix this formula" is a real command you can use. You paste in a broken formula, it tells you what's wrong and suggests a fix. For admins who aren't formula wizards, this alone is worth enabling the beta.

What It Can't Do (Yet)

I want to be straight with you because the Salesforce marketing team will tell you this thing does everything. It doesn't. Here's what I've run into.

It can't deploy metadata between sandboxes. If you're using change sets or a DevOps tool like Gearset or Copado, you still do that work manually. Setup with Agentforce is an in-org assistant, not a release management tool.

It doesn't do complex Flow building well. Simple stuff like creating a basic record-triggered flow with one decision and one update works. But anything with loops, collection filters, or subflows tends to need manual cleanup. I treat it as a starter, not a finisher.

It also gets confused by custom terminology. If your org calls Accounts "Clients" and you ask a question using that word, the agent sometimes doesn't connect the dots. This will probably improve as the model sees more orgs, but for now, use the actual API names when you're asking precise questions.

And like every AI feature, it occasionally hallucinates. I caught it once trying to reference a field that didn't exist in the org. The confirmation prompt saved me, but be skeptical and verify.

How This Fits With the Broader Agentforce Story

Setup with Agentforce is one piece of the bigger Agentforce 3 picture that Salesforce rolled out with Spring '26. There's also Agentforce Builder for creating production agents, the Command Center for monitoring agent health across your org, and Agentic Enterprise Search that pulls context from over 200 external sources.

If you're new to all this terminology, it can feel like drinking from a firehose. I've been pointing newer admins to salesforcedictionary.com when they ask what terms like "agent action," "topic," or "atlas reasoning engine" actually mean. Having a clean glossary beats trying to piece together definitions from six different release notes.

The through-line is that Salesforce is pushing admins and devs toward building and managing AI agents as a core competency. Setup with Agentforce is kind of the training wheels version. You learn how to talk to an agent, learn what makes a good request, learn when to override the agent's suggestion. That intuition transfers when you go build customer-facing agents with Agentforce Builder later.

Getting Started This Week

If you want to try this out and haven't yet, here's what I'd do. First, turn on the beta toggle in a sandbox, not production. You want to see how it behaves before you unleash it on real users. Second, create a dedicated permission set and assign it to yourself and maybe one other admin who likes to experiment. Don't roll it out to your whole team on day one.

Third, pick three real tickets from your queue and try solving them with Setup with Agentforce instead of clicking around. Pay attention to where it helps and where it gets in your way. My experience was that permission questions and simple field creation were immediate wins, while anything involving sharing rules or Flow logic needed babysitting.

Fourth, check the Setup Audit Trail after a day or two. Every change the agent makes gets logged just like a manual change, so you can review what actually happened. That audit trail is your safety net if someone asks "who added this field?" and the answer is "the agent, at my request."

Fifth, give feedback. Salesforce is iterating on this fast and the beta period is when admin feedback actually shapes the final product. The in-product feedback button works, and so does the IdeaExchange.

The Bigger Picture

I'm cautiously optimistic about Setup with Agentforce. It's not going to replace admins, and the marketing framing that suggests it might is a little silly. What it does is remove the most tedious parts of the job so you can spend more time on the work that actually requires judgment. Data model design, security architecture, process optimization, user training. That's the stuff that takes a real human who understands the business. For reference material while you're getting up to speed on new Spring '26 concepts, salesforcedictionary.com keeps a running glossary that's been useful to me.

The clicks I'm saving on "does this user have access" and "add a field to this object" are clicks I get back for the harder work. I'll take that trade every day.

If you've been running Spring '26 for a few weeks and you have not tried Setup with Agentforce, this is your reminder to toggle it on. And if you have tried it, drop a comment below and let me know what's worked and what hasn't. I'm curious whether other admins are seeing the same wins and the same rough edges I am.