Solving Sharing Mysteries with Setup with Agentforce

Today on the Salesforce Admins Podcast, we talk to Nikita Kothari, Senior Member of the Technical Staff at Salesforce.

Join us as we chat about using Setup with Agentforce to understand and manage record access.

You should subscribe for the full episode, but here are a few takeaways from our conversation with Nikita Kothari.

Setup with Agentforce simplifies sharing

Why can't I see this record? It's a simple question but, as any admin knows, finding an answer can get complicated quickly. If you've ever found yourself digging through Setup pages and running SOQL queries to troubleshoot permissions and record access issues, this episode is for you.

This week, I'm talking to Nikita Kothari, a Senior Member of the Technical Staff at Salesforce. She's here to tell us how Setup with Agentforce can help solve sharing mysteries. Using natural language questions, admins can trace access across org-wide defaults, role hierarchies, sharing rules, groups, and manual shares to figure out what's really going on.

Troubleshooting permissions and record access issues

As Nikita explains, permissions and record access issues are so complicated because they are affected by many overlapping configuration settings. Small changes can accumulate over time, especially in a reorg.

Setup with Agentforce was built to help you detangle these issues with simple natural language prompts. You can put your questions about permissions and record access to an agent, instead of having to wade through 1,300 pages of Setup to figure it out on your own.

Once you've got a handle on what the problem is, you can use Setup with Agentforce to help you implement changes and get everything sorted. And it's built with trust in mind: every write action requires your explicit approval, the agent is bounded by your permissions, and every configuration change is captured in the Setup Audit Trail.

Plan permissions for your org

If you're trying to figure out where to get started, Nikita recommends starting small. "It's very difficult to go back and fix something," she says, "so I would highly recommend trying any changes in a sandbox with the minimum set of users to see if it is working as expected or not."

And because Setup with Agentforce makes looking at permissions and record access so much easier, Nikita recommends taking advantage of it to conduct a monthly permissions review. Again, these issues accumulate over time, so an ounce of prevention is truly worth a pound of cure.

Make sure to listen to my full conversation with Nikita for more on Setup with Agentforce and how to get sharing straightened out in your org. And don't forget to subscribe for more episodes of the Salesforce Admins Podcast.

Podcast swag

• Salesforce Admins on the Trailhead Store

Learn more

• Salesforce Admins Blog Post: Mastering Your Org's Sharing Configuration with Setup with Agentforce

• Salesforce Admins Blog Post: 5 Use Cases To Get Started With Setup with Agentforce

• Salesforce Admins Podcast Episode: Setup with Agentforce Makes Salesforce Admin Tasks Easier

Admin Trailblazers Group

• Admin Trailblazers Community Group

Social

• Nikita on LinkedIn

• Salesforce Admins on LinkedIn

• Salesforce Admins on X

• Mike on Bluesky social

• Mike on Threads

• Mike on X

Full show transcript

Mike Gerholdt: Today on the Salesforce Admins Podcast, we're talking with Nikita Kothari, Senior Member of the Technical Staff here at Salesforce, about using Setup with Agentforce to understand and manage record access. Sharing can be one of those invisible parts of the platform until someone can see a record they shouldn't or can't see one they need to. Nikita explains how admins can use natural language questions to trace access across org-wide defaults, role hierarchies, sharing, rules, groups, and manual shares. We also discuss why validation, permissions, testing, and human approval remain essential when AI helps make configuration changes. So give this episode a listen, click that subscribe button, maybe share it with another Salesforce admin who's ever asked, "Why can this user see this record?" Let's get Nikita on the podcast. So Nikita, welcome to the podcast.

Nikita Kothari: Thank you, Mike. It is amazing to be here. I'm from the engineering team, so you'll get my lot of perspective on how we are building Setup with Agentforce on sharing.

Mike Gerholdt: Yeah, that's exactly what I wanted to talk about. Let's first get a little acquainted with you. What do you do at Salesforce, and what are some of the things that you've worked on?

Nikita Kothari: So it's been close to two years I'm working with Salesforce. And currently, I'm working with access control and sharing space. What pulled me in is the realization that sharing is one of those invisible infrastructure layer. When it works, nobody thinks about it, but when it breaks, it actually breaks the customer trust. And you know how customer-centric Salesforce is, its number one priority is trust. So there is lot of critical issues that we are dealing with and we are trying to make the sharing as the best place for the admins. And we love our admins and we are trying to make things better for them.

Mike Gerholdt: I love our admins too. I used to be one for a while. I'd like to still think I am, but we'll see. Well, let's get into it. So I read your article and I'll link to that in the show notes. Tell me, I mean, before Setup with Agentforce, what did an admin have to do to answer a question of, why can this user see this opportunity and this user not?

Nikita Kothari: Oh, good question. So it's the simplest way of dealing with solving the sharing's toughest problems. So just to enable the Agentforce, you don't have to do anything. It comes along with the Agentforce. So go to the setup page, search for the Agentforce agent and enable your Setup with Agentforce, and then you can start writing those questions. You don't have to know anything beforehand, that's the best part of the Agentforce setup. And sharing is the challenging domain, I won't deny that. It is very, very complex. So answering even the simplest question that you ask, like, "Who this person is having access for this thing," it requires to look into a lot of different domains like OWD, role hierarchy, sharing rules, sharing groups, manual shares, to see which layer actually give that access to that particular user. And looking that information, sometimes it's easier with the UI, but most of the time user has to run lots of SQL queries to get the correct answer. And previously, admin was spending hours of work and sometimes even the afternoons just to deal with that single questions. And with Setup with Agentforce, it just a minute of work. You just give prompt to your chatbots and it'll give you the correct answer within seconds.

Mike Gerholdt: Yeah. I mean, boy, it used to be a lot of archeological digging. I think you called it that in the article. I know I used to have to feel like I was going through a checkbox, but tell me, I mean, walk us through a real investigation where an admin discovers that a user can see a record, they probably shouldn't. How would they use Setup with Agentforce to trace where that access came from?

Nikita Kothari: Yeah, great question. So while building these actions, we particularly divide it into two different segments. First segment is the read action and the second segment is the write action. Just to keep it, things untangled, read actions will help you to investigate. When you ask a question like, "Why Nikita has access for these things?" So our agent will go into the background, it will do all kinds of research and it will come up with the best answer. "Okay, Nikita is part of this group, and these groups provide the access to this particular record." And what a write action on the hand will do, it will help you to solve that problem. Now you know Nikita is part of the particular group. You can go ahead and ask your write action, "Can you please remove Nikita from this group?" And your write action will help you to remove that particular user from that group and boom, your problem is solved within a few minutes. It's reliable, it's fast, and I'm sure admin can save a lot of time with these two things. And you don't need to know which action or which thing you need. You just write the plain natural language and our LLM will be able to guess where to navigate and how to solve that problem.

Mike Gerholdt: Yeah. No, I hear you. I think you walked us through what a good sharing investigation looks like. But for you, is there a sequence admins should follow so that they don't just jump straight to changing configuration?

Nikita Kothari: I would say I would highly recommend admin to start playing