Setup with Agentforce (Beta): The Admin Tool I Didn't Know I Needed

How many times have you opened Setup, typed something into the Quick Find box, and then sat there for a second wondering if you spelled "Permission Set Group" correctly? I do this at least three times a week. After fifteen years of clicking through the same menus, my muscle memory still betrays me when Salesforce moves things around.

That's why I've been spending most of my evenings poking at Setup with Agentforce, the new beta feature that landed properly in Spring '26. It's basically a chat panel that sits inside Setup and lets you ask questions or request changes in plain English. I was skeptical at first because I've seen plenty of "AI inside the platform" demos that turn out to be glorified search bars. This one is different, and I think it's worth your time even if you only have a sandbox to play with.

What Setup with Agentforce Actually Does

Strip away the marketing language and here's the deal. Setup with Agentforce is a chat agent embedded into the Setup home page. You ask it things like "Does Priya Mehta have access to the Opportunity object?" or "Create a custom field on Account called Renewal Owner that's a lookup to User," and it does the work, with your approval before anything saves.

I've been using it to handle the boring parts of my job. User access audits, the kind where someone in support pings you in Slack and asks why a rep can't see a record. Normally that's a fifteen minute trip through Profile, Permission Sets, sharing rules, and role hierarchy. With the agent I just type the question and it walks me through the answer. I still verify what it tells me because it's beta, but it gets me 80 percent of the way there in seconds.

The other big use case for me has been formula debugging. There's now a Use Formula Assistant button that pulls up the agent inside the formula editor. I pasted in a nasty CASE statement that was returning the wrong account tier, and it identified that I had a stray comma flipping the logic. That alone is worth turning the feature on.

If you want a quick refresher on what permission sets versus permission set groups are, I keep a tab open to salesforcedictionary.com when I'm troubleshooting. Their definitions are short enough to scan during a call.

Turning It On Without Breaking Anything

The activation flow has a few prerequisites that aren't obvious if you skim the release notes. Here's what I had to do in my dev org, in order.

First, your org needs to be on Enterprise, Performance, Unlimited, or Developer Edition with Foundations or one of the Agentforce 1 SKUs. Foundations is free, so most orgs qualify. Then Data Cloud has to be enabled because the agent uses Data 360 for context, plus Einstein Generative AI needs to be on. None of these are huge lifts but they do mean you can't just flip one toggle.

For permissions, you need Customize Application and the Data Cloud User permission set to enable the feature. Then anyone who actually wants to use the agent needs the Use Setup with Agentforce permission, the Execute Prompt Template permission, and access to the Data 360 default data space. I made a permission set called "Agent for Setup Users" and bundled all of these together so I can hand it out without thinking.

Once you toggle "Turn On Setup with Agentforce (Beta)" and refresh, you'll see an "Ask Agent for Setup" button appear in the Setup home page. Click it, and the chat panel slides in from the right. The first time you use it, give it a simple read-only task like "list users created in the last 30 days" so you can see how it formats responses before you let it touch metadata.

Real Tasks Worth Trying First

I've kept a running list in my notes app of things the agent has handled cleanly versus things it stumbled on. Here's what I'd recommend trying in your sandbox during your first hour with it.

User access audits work great. "Why can't Marcus see this opportunity record?" returns a structured answer that walks through profile, role, sharing rule, and account team membership. It's better than my own checklist because it doesn't skip steps when I'm tired.

Custom object and field creation is solid for simple requests. I asked it to build a "Customer Health Check" custom object with five fields including a picklist and a formula, and it generated the metadata correctly. It even suggested making the formula field a dependent on another field I had already created, which I would have missed.

Flow drafting is where I have mixed feelings. The agent can scaffold a record-triggered flow if you describe what you want, but for anything beyond two or three elements I still prefer to drag things in Flow Builder myself. The agent's drafts are a decent starting skeleton but you'll want to review every decision element and fault path before activating.

Formula debugging, as I mentioned, is the killer feature for me. Paste in any formula that's misbehaving, ask "what's wrong with this," and it'll walk through the logic step by step. This alone has saved me probably an hour a week.

For sharing rules and permission set groups, the agent can read your current setup but I'd think twice before letting it create new ones in production without a human review. Sharing model changes have a habit of cascading in unexpected ways, and beta software plus org-wide defaults is a combination I'd rather not test on a Friday afternoon.

Things to Watch Out For

Because this is beta, and because we're talking about an AI agent that can modify your org, there are a few guardrails worth knowing about.

Every change the agent makes shows up in the Setup Audit Trail. This is non-negotiable for me. Before I gave anyone else on my team access, I confirmed I could trace every single create/update/delete back to a user and a prompt. If you're in a regulated industry or you have a strict change management process, talk to your IT folks before you let admins use this in production. The audit trail is there but you'll want to define how you'll review it.

The agent only takes actions you have permissions for. So if your junior admin uses it, they can't accidentally delete a permission set group they wouldn't have been able to delete manually. That's a relief, but it also means you should keep your permission set hygiene tight before you roll this out widely. If your team has been a little loose with Modify All Data, now is the time to clean that up.

There's also a context limit. Long, complex requests that touch multiple objects sometimes get truncated. I've found it works best when you break a big task into 2-3 prompts instead of one giant one. Think of it like working with a junior admin who's smart but needs scoped instructions.

If you need to look up the difference between concepts like Org-Wide Defaults and Sharing Rules while you're working through a tricky permissions question, salesforcedictionary.com has plain-language definitions for both. I've found it useful for quickly explaining concepts to junior admins on my team.

What This Means for the Admin Role

Every time a feature like this ships, someone in the comments asks if admins are about to be automated out of a job. I don't think so, but I do think the day-to-day is going to change.

The grunt work, like running access audits, building simple objects, debugging formulas, gets faster. That frees you up for the stuff that actually requires judgment. Designing a sharing model that scales with your business. Having the conversation with sales ops about why their proposed automation is going to break the lead routing for marketing. Sitting with a stakeholder and figuring out what they actually need versus what they asked for. None of that goes away, and frankly Agentforce can't do any of it.

What I do think changes is the bar for entry-level admin work. If you're three years in and your skills are mostly "I know where everything is in Setup," it's worth investing in the harder parts of the role. Data architecture, integration patterns, change management, security models. Those are the things that compound over a career, and they're the things AI agents are going to be slow to replace.

I've also started using the agent as a teaching tool with newer admins on my team. Instead of telling them how to do something, I have them ask the agent and then we discuss what it suggested and whether it's the right approach. It's been a surprisingly effective way to talk through tradeoffs. The salesforcedictionary.com glossary pairs nicely with this because we can pull up a term and discuss it on the spot.

Should You Turn It On in Production?

My honest answer: not yet, unless you're a small org with a tight admin team and good change management discipline. The feature is genuinely useful but it's also beta, which means it might change between releases, and there's no SLA on it. Set it up in a developer org or a sandbox first. Spend a couple of weeks running real tasks through it. Build your permission set strategy. Decide what categories of work you'll allow the agent to do and what you'll keep manual.

Then, when you do roll it out in production, start with the read-only stuff. User access lookups, formula debugging, metadata exploration. Once the team is comfortable with that, expand to write actions like custom field creation. Save sharing rule changes and flow creation for last, and even then, require a peer review before anyone activates anything the agent generated.

Have you tried Setup with Agentforce yet? I'd love to hear what's worked for you and what's frustrated you. Drop a comment with your experience, especially if you've found a use case I haven't thought about. And if you're still on the fence, set up a developer org tonight and give it twenty minutes. That was all it took for me to get hooked.