You know that moment. You are three tabs deep in Salesforce documentation, trying to remember where that setting lives. Quick Find has failed you twice. Now you are skimming the release notes.
Spring ’26 introduced Setup with Agentforce in Beta, and it puts an AI assistant directly inside every Setup page. Type what you need in plain English. The agent finds it, does the work, and asks for your approval before changing anything.
This guide covers how to enable it, what permissions you need, and where it saves the most time. If you are also working through other Spring ’26 changes, our release readiness playbook for leaders covers the full cycle.
What Setup with Agentforce actually does
Setup with Agentforce is not a chatbot sitting next to your Setup pages. Instead, it is embedded directly into Setup Home and available on every Setup page via an Ask Agent button. You describe what you want in plain language, and the agent brings the relevant tools, records, and documentation straight to you.
Additionally, it does not just navigate. It takes action. The agent creates fields, clones users, troubleshoots permissions, and resets passwords. Every action, however, goes through a confirmation step first.
What it currently covers
Salesforce started with the tasks admins repeat most often. Here is the current list:
- Managing users: clone, freeze, find by permission requirements
- Troubleshooting object, field, and record access issues
- Creating and managing permission sets and permission set groups
- Building the data model: custom objects and fields with suggestions
- Searching Help and Training documentation
- Navigating to the right Setup page for any task
- Creating and managing flows and Lightning pages
- Resetting passwords and fixing formula errors
Furthermore, every change the agent makes is logged in the Setup Audit Trail. Therefore, you have a full record of what happened and when.
You can explore the full capability list on Salesforce Trailhead.
Before you enable it: what you need in place
Four things must be ready before you switch the feature on. Skipping any of them will prevent the feature from working.
Org prerequisites
- Data Cloud must be set up the feature relies on Data 360 as its foundation.
- Generative AI must be enabled go to Setup, search Einstein Setup, and confirm Einstein is turned on.
- Agentforce must be active search Agentforce in Setup and confirm it is on.
- Correct edition Lightning Experience only, available in Enterprise, Performance, Unlimited, and Developer Editions with Foundations or Agentforce 1 Editions.
Required permissions
Two layers of permissions control this feature. First, the admin enabling the feature needs these.
To enable for the org
For each user who will use it
Important: the agent only helps with tasks the requesting user already has permission to perform. It does not elevate access. If a user cannot create a field manually, the agent will not create it for them either.
For a deeper look at permission set architecture in Salesforce, our External Client Apps and integration governance article covers how Salesforce is separating developer and admin permission layers across Spring ’26.
How to enable Setup with Agentforce: step by step
The process takes under five minutes if your org prerequisites are already in place. Follow these steps in order.
The official Salesforce Spring ’26 Admin blog post also walks through activation with screenshots if you prefer a visual reference.
Go to Setup
Use the gear icon in the top-right corner or type Setup in the App Launcher.
Search for Agentforce in Quick Find
Look for the Setup with Agentforce (Beta) toggle in the results.
Turn the toggle on
The feature is off by default. Flip it on.
Refresh your browser
The prompt bar will not appear until the page fully reloads. This is the most common missed step.
Assign permissions to users
Go to Permission Sets. Add Use Setup with Agentforce and Execute Prompt Template to the relevant permission set. Also assign the Data Cloud User permission set to each user.
Open Setup Home and test
You should see a prompt bar. Type a question to confirm everything is working.
Sample prompts to use first
Once the feature is live, these prompts cover the scenarios where it saves the most time. They are a good starting point for testing before rolling out to your team.
Additionally, you can start from the conversation recommendations that appear on Setup Home. These recommendations reflect your org’s health metrics and suggest the most relevant actions for your current configuration.
Where it saves the most time
Permission troubleshooting
Tracing why a user cannot see a field or a record normally involves opening multiple Setup pages. You cross-reference profiles, permission sets, field-level security, and sharing rules. The agent compresses that whole investigation into a single question and a structured output.
Consequently, what used to take fifteen minutes of clicking now takes about thirty seconds.
Data model changes
When you build a new object or field, the agent first checks whether an existing one fits your requirement. This prevents the kind of technical debt that accumulates when admins create duplicate fields under time pressure.
For admins managing bulk metadata operations, our guide to uploading Custom Metadata Type records from CSV covers a complementary approach to data model management.
Onboarding new admins
For new admins or those unfamiliar with a specific Setup area, the ability to ask a question and be taken directly to the right page is more useful than any Quick Find search. Rather than learning the navigation, they can describe what they need and trust the agent to get them there.
What it cannot do yet
This is a Beta. The scope is genuinely useful, but it is important to set accurate expectations with your team before you roll it out.
The feature does not operate in Salesforce Classic. It only works in Lightning Experience. Furthermore, it requires Data Cloud to be set up in the org, which means it is not available in every edition. The capability set, however, continues to grow with each release.
The agent also cannot take action without your explicit approval. However, that is a feature, not a limitation. You retain full control over every change.
Finally, because this is Beta, outputs may occasionally require review before you apply them. Therefore, testing on a sandbox before enabling it in production is the recommended approach.
For a full breakdown of how to manage Salesforce releases and test features safely, see our release readiness playbook.
| What it can do | What it cannot do yet |
|---|---|
| Manage users: clone, freeze, find by permission | Make changes without your explicit approval |
| Troubleshoot object, field, and record access | Perform tasks the requesting user lacks permission for |
| Create and manage permission sets and groups | Work in Salesforce Classic — Lightning Experience only |
| Create custom objects and fields with suggestions | Cover all Setup areas — scope expands in future releases |
| Answer Help and Training documentation questions | Operate without Data Cloud configured in the org |
| Create and manage flows and Lightning pages | Guarantee production-ready output — still Beta |
| Reset passwords and fix formula issues | Work on orgs without Foundations or Agentforce 1 Edition |
The most useful thing about Setup with Agentforce is not any single task. It is that the Setup experience stops being a navigation problem and becomes a conversation.
Tried Setup with Agentforce yet? Tell us what task you tested it on first. And if your org needs help with Spring ’26 readiness in general, contact us through truesolv.com. Follow us on LinkedIn for more admin-focused content every week.
Official resources
More from TrueSolv
