Salesforce Admins Podcast
The Salesforce Admins podcast features real-life Salesforce Admins, product managers, and community leaders who transform businesses, careers, and community with clicks, not code. This 20min (sometimes a bit more) weekly podcast hosted by Mike Gerholdt feature episodes to empower Salesforce Admins who are implementing Enterprise CRM solutions. There may be some (digital) confetti. For more than our most recent episodes, go to https://admin.salesforce.com/salesforce-admin-podcast.
info_outline
What Salesforce Admins Trust AI to Do Now (That Seemed Outlandish a Year Ago)
11/19/2026
What Salesforce Admins Trust AI to Do Now (That Seemed Outlandish a Year Ago)
Today on the Salesforce Admins Podcast, we talk to Jennifer Lee and Kate Lessard, Lead Admin Evangelists, and Joshua Birk, Senior Director of Admin Evangelism at Salesforce. Join us as we chat about how our relationship with AI has changed over the past year. You should for the full episode, but here are a few takeaways from our conversation with Jennifer Lee, Kate Lessard, and Joshua Birk. AI has gotten better at building things For Kate, the biggest difference when it comes to AI is that she trusts it to do more things. While she used to make sure that an agent never did anything without her approval, she’s much more confident in relying on the guardrails she’s put in place. Jen has had a similar experience. “A year ago, if AI asked me if it could create a record or touch my Salesforce org I’d say no way,” she says, “I’m going to need to see everything.” Nowadays, she just needs to make sure it’s on the right track before letting it go off and create something. But AI has been amazing for creating demos, especially for testing and creating dummy data. Trusting a personal assistant agent Josh, meanwhile, has been taking advantage of AI as a personal assistant. It’s allowed him to reclaim his inbox and stay on top of things. “I can use my inbox on a daily basis, without having to spend the morning deleting hundreds of emails before I can read something that is actually useful,” he says. However, he’s quick to note that his personal assistant agent has very clear boundaries on what it can and cannot do. “If it goes wrong, how quickly can you recover from it?” he asks. An empty bank account is a lot harder to fix than an email that went to the wrong person. Getting financial advice from an agent For me personally, this is the year that I’ve felt comfortable having an AI look at my finances and make some suggestions. It’s helped me adjust my retirement savings and plan for the future, and I couldn’t say I would have done that a year ago. What about you? What are you doing with AI that would have seemed ridiculous to you a year ago? Make sure to listen to the full episode for more from Josh, Jen, and Kate on how they’re working with agents. And don’t forget to subscribe to the Salesforce Admins Podcast to catch us every Thursday. Podcast swag Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins Podcast, we're doing a November retro with three of my Salesforce admin evangelist teammates, Jennifer, Josh, and Kate. Now, here's what I asked them. I wanted to know what they trust AI to do today that would've sounded just a little outlandish a year ago. And I think you're going to be surprised maybe what the answers are. We also talk about where everyone's going to draw the line with AI, and Josh shares a simple test for deciding how much access to give an AI agent. So, if you're a Salesforce admin figuring out your own comfort level, you'll probably recognize yourself somewhere in this conversation. And in case you haven't already, make sure you follow and subscribe to the Salesforce Admins Podcast, whether you're listening to us on iTunes or on the podcast app, or if you're watching this on YouTube, be sure and subscribe to the Salesforce Admins YouTube channel. So, with that, let's get my fellow teammates on the podcast. So, everybody, welcome to the podcast. It's November and time to talk some AI with fellow admin evangelists. So, we'll get started. Jen, could you do a brief introduction of what you do at Salesforce? Jennifer: Sure. Oh, I do all sorts of things at Salesforce, whether it's blogs, presentations, videos. I've been doing videos galore. You probably are sick of seeing me with AIforce in Action, but that's been my thing lately. Mike: Never sick of AIforce in Action. Josh? Josh: We all have very similar roles, but humorously I've had a couple of conversations this week alone about how do you keep up with the platform? And it's like, well, thankfully a large part of our job is research, right? We get time to actually go in and research and to keep this on topic. Gosh, AI is making that so much easier. So, talking to AI and creating content, that's what I do. Mike: Oh, I thought you were going to say pressing two. Josh: There's a lot of pressing two, yes. Mike: Pressing two. And Kate, certainly last but not least. Kate: Oh, well, thank you. I do a lot of the same things just mentioned. I have not been doing videos galore lately. I think the thing on the team that I do that's maybe a little bit different is that I own the workshops for our team. So, I've been spending a lot of time on our hands-on workshops lately and creating new AI force content to get more admins hands-on. Mike: Mm-hmm, fun. Obviously, it's crazy because just a few years ago we were barely talking to AI and then we had some workshops where we had thousands of prompts that we were building. And now I feel like every day there's at least every part of what I do, AI touches some part of it. Either it's advice that I need or research on something or to Josh's point, I'm just telling it to go do something while I switch a screen and go tell another AI to go do something. I think it's fascinating how with very little training or no training, AIs just permeate our lives and especially as Salesforce admins. So, the question that I'm going to pose to everybody, and Kate, we're going to start with you, is when you look back a year ago, what's something you trust AI to do now that a year ago just seemed outlandish? Kate: Man, and it really does come down to trust, right? I think that over the past year for me, the biggest shift has been how I interact with AI. I think I've gone from just asking how to do something and asking a question to actually having a level of trust to have AI go and do the work for me. And I think a lot of that really comes down to the capabilities of the headless toolkit and still being able to have that kind of direction and judgment and that control over what's going to happen. But while I can provide that direction and judgment, I don't necessarily feel the need to execute every single step anymore. And that's been a really big mentality shift over the past year. Mike: Mm-hmm. Wow. Okay. We'll continue on. Josh, I feel like you're probably doing more with AI than all of us combined, but- Josh: Yeah, I recently made the joke. Somebody asked if I use an agent at work and I'm like, "No, I don't use an agent at work. I use five, some of them simultaneously." I just had one agent, one AI proof the other AI's work and it actually found a whole bunch of flaws on it, which I wouldn't say is something I wouldn't trust AI doing in the past. Although I think previously, I would force myself to be the human in the loop and not necessarily put AI, checking AI, checking AI kind of thing. So, that's sort of new. For me, the big revelation that I'm so comfortable with is the surprise to me is AI is in my inbox. AI is in my Slack. AI is in my calendar. And if you had gone to early AI Josh in his speeches, I would be like, "Why would you even want that?" But I use a personal assistant and I've reclaimed my inbox. I can use my inbox on a daily basis where it used to be I would spend a morning just deleting hundreds of emails before I could even read something that was actually useful. Now I wake up, Slack is actually in my inbox and it's like, "Hey, here's all the important things you actually need to address right now." And for somebody who sometimes has a little bit of an attention deficit problem, AI adding a little bit of focus has been very helpful to me. Mike: Oh, sometimes. Kate: I remember those early Josh AI speeches about that. Josh: I have been the warning sign in the past. It's true. Mike: I was, as you were explaining that, Josh, thinking of all of my friends that easily a year ago were just tired of everything, every application having an AI component to it. And I think it's because it didn't do anything, anything better than the search bar already done. But that was a year ago. Now, now it's almost the starting point for every application that you launch on your phone or on your desktop. Jennifer, how about you? Jennifer: It's really been a productivity booster for me. I think a year ago, if AI asked if I could create a record or touch my Salesforce org, I'd be like, "No way, dude. I'm going to need to see everything." You make the recommendations like Kate, I will go in and do it. And I've been using a lot of Claude lately to do some of my demo work. And first I had it set to show me what you're about to do, get my approval. And then after just reviewing it, I'm like, "Okay, you know what you're doing. I'm going to let you go ahead and do." And it's just been amazing having it just thinking about the idea, sharing it with Claude, and then it just doing things. Sometimes, it's not perfect. You still have to go in and make some tweaks, but it's pretty close and I love the fact that it goes and does testing for you and it tells you what it's going to test. And then in terms of your demos, you want to make it look real, full of data. And I love the fact that it goes and creates the data and loads it in for you. So, that's been a huge saver for me and something that I wouldn't have done a year ago at all. No, no way. Josh: Right. Yeah. I actually got called out by the community on a video I did about hooking Claude web browser, the web version to Salesforce. And somebody was like, "Why isn't that dangerous?" And the first speech I ever gave earlier was, I don't know if it was a user group that I did with Mike here in Chicago, and I gave the example of people putting in internal code and then OpenAI basically just owned that proprietary data. And yeah, that was true at the time. And I think part of the reason trust with AI is so hard is because it is moving so fast and the goalposts do shift drastically. And all of these big players, OpenAI, Facebook, Anthropic, they knew they had to get the enterprise market, right? And so, they also knew that they're not going to get those customers if you don't trust them with hooking something up like to a Salesforce org. But honestly, it happened and I didn't even see it. It wasn't until I was told, "Hey, go make a video hooking it up to Salesforce," that I double checked that I'm like, "Is there privacy guidelines? Are there guardrails?" And there absolutely are these days. Mike: Yeah. I had to think about this question because I also wanted to answer it, and my answer is probably not what everybody expects, but this year, and I would say since probably June forward, I felt comfortable having an in AI, I won't mention which one, look at my finances, like my pay stub and help me adjust my retirement savings amount and the amount that I'm saving to hit different targets. Josh: Interesting. Mike: And I say that two caveats because the second one is a question, will be a question. First of all, I 100%, here's the pay stub, it's a PDF, and you don't know a single checking or any account. I am not there yet. The second that leads to my second question is I feel like I'm seeing more and more commercials where people are asking an agent to find this hotel and book it or find this trip and book it. Or one of them is they take a picture of a bill and they ask the agent to pay it. In realistic terms, because we live in the real world, how comfortable do you think you are? And do you think maybe a year from now we'll look back and be like, "Wow, I can't believe we said that"? Jennifer: I'm just shaking my head. Nope, no way. Kate: We were just talking about how worried I am in general about just everything in life. So, that's a no for me at this point. Talk to me in a year. We'll do a recap and see where we're at, but- Josh: Yeah. I have a very good friend. He's a technical architect and we're very like-minded when it comes to things like applications and AI and security and stuff like that. And I told him I started using this personal assistant and he thought it was insane, but it does not have access to any of those things that you just... It does not have access to my credit card. It can't buy anything. It can't book anything. It is a wonderful little research assistant and helps me on my day-to-day, but it can access my email and send emails on my behalf and also send texts on my behalf, but it does follow the right guardrails, right? It does not do it without my permission and without me reviewing and all of that kind of stuff. I think it's a very slippery slope. And the thing is what you're describing, Mike, is that's very much where the big players are going. That's how they want to really get a personal AI into your day-to-day life is to make these things so easy that it's like using a calculator with math, right? You're not going to book a trip anymore because the AI is just going to do so much of the day-to-day for you and so much of the to-do list. My two thoughts on it is, first of all, I don't think they're there yet when it comes to actually have access to a banking account and actually spending money and having things that would be if it goes wrong, put this on the list. If it goes wrong, how quickly can you recover from it? If my AI was like, "I am sorry, I sent an email to that person, I thought we were talking about it," I can send an email follow up and be like, "I'm so sorry, my AI screwed up." If my bank account goes empty overnight, that's a little bit harder to fix kind of thing. So, I think right now it really is, there's a personal question to it of is this going to make your life easier versus the risk involved if the AI actually does make a mistake? Mike: Yeah, it's interesting because you think of you want that to happen. It's such a time saver, but the trust factor of the money is real and does the AI feel like the money is real? I've also run into, I feel like we're at this convergence point where a lot of people are safeguarding against AI's hitting AIs, makes it sound like I'm 72 and setting the VCR clock, the AI's hitting their website. So, I asked one, I have this rug in my living room that I love, but it's starting to get worn out and I really want to replace it. And I asked to find me another one and it searched for three hours and it came back and it said, "Look, I can't get to any of these sites. They're blocking my ability to pull up the website." And I feel like it's a push-pull, right? We need to safeguard that and people rightfully so with the website, I don't want this type of traffic, but also there's people like me that I really want this to be able to search this site and crawl and it's not. So, it hits that kind of barrier for me. Josh: Yeah. And it's strange because they're different in their approaches and I won't call out specific AIs, but earlier today I was trying to get cloudy into an image and one AI told me I cannot recreate brand and logos for you now that you've told me this is an official mascot conversation over. And so, I went down the street to one other AI and I was like, "Hey, can you do this?" And it was totally no problems. And remember, there's all these guardrails that are totally human created, and there's a line in one guardrail list and there's not in another one. So, it's an interesting mix of possibilities right now. Mike: You went down the street, you mean you just turned down the dark alley where they just relaxed their guardrails. Josh: Exactly. Mike: This will be the example I use for a long time, but I still remember Josh showing up on a team meeting and I forget what you were using, but you were like, "We can just ask it to generate a cat as a pirate on a ship in the middle of the ocean." What? That was the coolest thing. So, I was all ready to go for AI. Great. Well, it'll be interesting to see a year from now if we're telling a bot to update our checking accounts or not. I had somebody in the grocery store pay with cash the other day, and the poor lady at the register looked at it as though she was being handed Mexican pesos, Kate, because I'm old enough to remember being at the grocery store and begrudgingly writing a check and being like, "Oh, if you just had cash, this would go so much faster." And now it's just- Kate: Even better, being the person at the cashier stand trying to run the check through the little scanner thing. Josh: Right. Oh my God. Kate: I remember that. Mike: And you had to make the cross, fill things out. Josh: Yeah. Yeah. Or the [inaudible 00:16:09] credit card readers. Jennifer: Yes. Kate: Yes. Mike: I was part of the [inaudible 00:16:12] credit era. Josh: Thank you. Thank you for that. Mike: Yeah. Now, Josh, you just tap it. It's a chip. Josh: You tap it and you go. Sometimes, I just tap it. Kate: Here's your watch. Mike: Oh yeah, I know. Yeah. That to me still feels a little magical to tap a phone. Josh: Yeah. I moved back in time over the weekend because I was running around doing chores and realized one of my tires had almost like 10 PSI, dangerously low pressure. And so, I went to the most Chicago experience of getting this fixed because the actual garage was an actual garage behind the office building that they reside in. You have to go through their Chicago Bears paraphernalia in order to get into the garage, and then the whole thing turned into just a cash transaction. There was no cash register. I'd have to go all the way back to the other building in order to do it. Mike: Wow. Josh: So, I just gave them 40 bucks and got 15 bucks back. And I was like, "When was the last time I got change? Actual change." Mike: Yeah. Well, there's no pennies now. Kate: It costs that much. You need your own air compressor. Mike: There's no pennies. You do, Josh. I can recommend some for you. Josh: Nice. Mike: They're not that bad. Well, appreciate you all coming on the podcast and sharing what you do and don't use AI for, and of course, building really cool AI projects. So, thanks all. Josh: Cheers everybody. Jennifer: Thanks. Kate: Bye. Thanks. Mike: Thanks again to Jennifer, Josh, and Kate for joining me. And I think the idea I keep coming back to is the one that Josh questioned about recovery and that's if your AI gets something wrong, how quickly can you fix it? An email to the wrong person is just one apology, but a bank account being emptied overnight is a different story. And that's a useful way to think about how different requests could get handed over. And I think it's also why we saw four people can have four very different answers about what they thought AI would do for them now versus a year ago. So, if this conversation sounds like something you enjoyed having, thanks for watching. And if it sounds like something someone else would enjoy watching, be sure to share that out on social. We'd love to have more people listen to the podcast, whether you're listening on iTunes or you're watching this on the Salesforce Admins YouTube channel. So, with that, until next time, I'll see you in the cloud.
/episode/index/show/buttonclickadmin2/id/43807869
info_outline
How Builder Central Is Changing the Way Admins Build
11/12/2026
How Builder Central Is Changing the Way Admins Build
Today on the Salesforce Admins Podcast, we talk to Tiaan Kruger, Senior Director of AI Product Management, and Daivat Dholakia, Product Manager for Builder Central at Salesforce. Join us as we chat about how admins can use Builder Central to create better solutions, faster, for their organizations. You should for the full episode, but here are a few takeaways from our conversation with Tiaan Kruger and Daivat Dholakia. What is Builder Central? Every admin has a backlog of ideas that are good but never quite urgent enough to build. Builder Central, now in beta, is here to help you take those ideas into production. This week, I sit down with Salesforce product managers Tiaan Kruger and Daivat Dholakia to find out what it’s all about. With Builder Central, you can go from describing an idea to a working solution on the platform without using code. You can use the agent-powered tools that you love while keeping your data on the platform you trust, grounded in the context of your business and configuration. Most importantly, it’s delightful to use. “I have not had this much fun building on the platform in probably 16 years,” Tiaan says. With Builder Central, you can build things in hours that used to take days or even weeks. See what you’re building before publishing to a sandbox Obviously, we want to test things out in a sandbox before pushing them to production, but that can mean making changes to your metadata as you’re building. It’s cumbersome, time-consuming, and sometimes dangerous. That’s why Builder Central lets you work things up in a virtual environment before pushing them to your sandbox. You can explore an idea and hash things out without having to roll back metadata. Similarly, visualizers let you see how a flow you’re building looks in your org before it ever gets there. By the time something hits the sandbox, it’s already working the way you want it to, and you can focus on the finishing touches to push your solutions to production. How Builder Central helps you with tech debt With 10 years under his belt as an admin and developer, Tiaan understands that a big part of the job is fixing, maintaining, and improving existing infrastructure. So how does Builder Central help with that? Because it has access to all of your metadata, you can refactor or test existing flows. If you have tech debt in your org (and who doesn’t?), you can probably get an agent to help you with that. You can refresh existing apps with a modern UI and your brand’s colors, then make modifications to your heart’s content. Finally, everything you create in Builder Central follows your security settings and naming conventions, so your solutions are secure and easy to maintain. Make sure to listen to the full episode for more from Tiaan and Daivat about Builder Central, and check out the video to see the demo. And remember to subscribe to the Salesforce Admins Podcast to catch us every Thursday. Podcast swag Learn more Salesforce Admins Blog Post: Salesforce+: Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins Podcast, we're talking Builder Central, and I'm going to admit upfront, I'm its biggest fan. I'm joined by Tiaan Kruger and Daivat Dholakia from the platform product team, who spent the last couple of years really figuring out how to bring AI to low-code builders without putting your sandbox at risk. Now, we're going to get into why you build in a virtual environment and how you can scrap everything if it goes sideways, and really how it helps with that 90% of your job, which is just fixing and maintaining what already exists. Not to mention what's coming in terms of governance and policies. Now, if you're in and you enjoy the show, make sure you follow and subscribe wherever you're watching, wherever you're listening. So with that, let's get Tiaan and Daivat on the podcast. So Tiaan, Daivat, welcome to the podcast. Daivat Dholakia: Thank you. Tian Kruger: Thank you, Mike. Mike: Good to see you. Long time since we've talked, I think it was what, Dreamforce just a few months ago, which in Salesforce terms is like 14 years, because months are years at the rapid pace that things are innovating. For those people that haven't met you at Dreamforce or one of our events, Tiaan, let's start with you. What do you do at Salesforce? Tian Kruger: Thank you, Mike. So I am in the product group in platform, been here about seven years, I have built a bunch of different things, but I've really spent the last couple of years focusing on how we bring AI to our low-code audience. It's a very big challenge, it's something we want to do really well. And before that, I was actually a developer and an admin. So I actually worked in the industry for 10 years. So before I came to Salesforce, actually did the job that I'm trying to make easier for people. Mike: Which is awesome. Diva, I had the pleasure of meeting you this Dreamforce. You thankfully were on our Salesforce Plus feed, as I can't put Tiaan everywhere because he's also in the keynote. Daivat Dholakia: Yes, thank you, Mike. Yeah, it was an amazing experience being on Salesforce Plus. Just to give a brief background about myself, I've been with Salesforce almost five years at this point, I've done a couple of different things, including working on identity and also working on the Salesforce authenticator app that we still have around and it's still being used by a lot of people. And I also worked on mobile before I started working with Tiaan on Builder Central and helping out our admin persona to reduce the amount of time it takes them to get to build, and then soon we'll have a lot of additional things as well that we'll probably talk about in here as well. But super excited to be talking with you on this podcast. Mike: Yeah. So the cool thing about this, is you have the number one fan of Builder Central hosting this podcast with you. I saw it a little bit before Dreamforce, but I got my hands on it after Dreamforce. And let me tell you, I am the happiest, one of the happiest admins on earth. I can't wait until this gets unleashed for people to try. But let's talk about that because this is the most fun podcast I'm going to record all year because we're going to talk about Builder Central, and I can't build enough things with Builder Central. If you follow me on LinkedIn, you know that I've already built an app and I'm a kid of the '80s, so I built a Knight Rider dashboard, and then I built a car dashboard. I do have plans for a Goliath dashboard, so I'll sneak peek that just because I like building dashboards. But let's talk about quite possibly in my opinion, the coolest thing Salesforce has ever released, which is Builder Central. Tiaan, tell me what Builder Central is. Tian Kruger: Absolutely. So by the way, I loved your enthusiasm. It's hard to get somebody who works on the platform all day long, to be this excited about something. So I'm enjoying your enthusiasm so much. Mike: Good. Tian Kruger: But Builder Central is the end result of about two and a half years of work internally to figure out how we build on the platform with AI in a constructive way. How do we go from idea, describing it, to a working solution on the platform? And not just using any process, but making it no-code, low-code friendly, taking an admin and giving them the same tools that developers have been enjoying for the last two years, and creating things on the platform. It's built on top of all of the hard work the team has put in in their headless story, trying to figure out how do we make it easier for you to build with agents on the platform, do everything from MCPs, do it using skills, all of this stuff that we've been doing for vibes and we've been doing for frontier models. How do we take advantage of all of that, but then bring it in a package and an easy to use kind of experience that makes it delightful to use. And I think we actually managed to achieve it. The experience of- Mike: Oh, you did, in my opinion. Tian Kruger: The experiences, I've been on the platform for 17 years, I have not had this much fun building on the platform in probably, I don't know, 16 years, because it just takes so much of the pain out and that's really the goal. The goal is just to be delightful, to be fun, to be visual, take the schlep work out of it and just make it fun to create on the platform again and just unleash it for your business. Mike: Yeah. I will say it's never not been fun to build on the platform. I think it's rewarding and I think that's why people come in, because I can tell you exactly how I felt the first time I created Dependent Picklist. And Dependent Picklist sounds like the easiest thing in the world to make, until you get in the Wayback Machine and you go back to 2007 and CRM and everything was hard and Salesforce Dependent, this, this, next save. Oh, oh, oh, it's there. And I remember showing it to people because the first Picklist had three ideas and then it depended on the answer, and everybody in the office was like, "Wow, Mike, you did really good." I was like, "Yeah." Builder Central is the next evolution of that. The last time I was this excited was when we introduced branding and themes, because I was really big into the show Top Gear, and I created an entire org to track cars and episodes and lap times and podcasts. And I was like, "This is amazing. This is the best thing I've ever built in Salesforce." And then Builder Central came along and it's scratched an itch I didn't know I had. Tian Kruger: I think it's time for a reprise of that app, don't you think? Mike: Oh, you have no idea. I have so many plans to build things. Daivat, tell me a little bit about you were at Dreamforce and got some customers sharing their experiences and talking about stuff that they were building. What was some of the stuff that you heard and have heard while it's still in beta? Daivat Dholakia: Yeah. The feedback from the customers that have tried it has been phenomenal. It's very similar to what you have also been sharing, which is it's opened up new possibilities that they did not even think were even in their realm of what they could do within Builder Central. For example, we have had a couple of different customers that have said that, "Hey, what used to take us about seven days, 10 days worth of time for multiple people to do, now a single person can do it in like two to three hours at most." The way they are thinking about solving problems is changing now because they were previously dependent on, "Hey, do we need to have the right prioritization for this?" This goes into this bucket list of, "Yeah, it would be great to have this, but we don't have the bandwidth and it's not high enough in our priority list." Versus now they're like, "Yeah, let me just go ask this and get this done in Builder Central and show what is possible." And when everyone's aligned, they're like, "Yeah, this is great. Just let's push it out into production and get it to work." So it's changing how they're working as well. We have one customer that has been very, very engaged in the product and for them, their primary use case is how do they go about building an entire service portal, for example, for internal as well as external? And that is also, they're trying to do a POC on that to show that, hey, today in the traditional world, it takes about six to eight weeks for that to get done, versus now they were able to actually build something within a couple of hours as a prototype, and now they're iterating on it to be able to see how far they can push just by having a natural conversation without them having to know every nitty gritty detail of how that is getting done under the covers. Mike: Yeah. No, I agree. Tiaan, I don't know if you baked this in, it's got a little bit of attitude. I love how it sometimes comes back. When I was building the Knight Rider dashboard, it was like, "Ooh, I like this idea." And I was like, "Well, hello, how are you?" And it's not a lot, but it's a little bit of something that was just enough to be like, "I'm with you on this. I'm not just a robot doing what you tell me to do." And it kind of felt like it was on the path. So I had to tell you about that because I thought it was pretty cool. Tian Kruger: There's a little SaaS in it. Daivat Dholakia: Yes. Mike: Oh, yeah. Tian Kruger: And it's not a lot, but it just reminds you that SaaSy is still alive somewhere out there. And it cracks me up because it does feel a little bit like a coworker at times in a positive way. It sometimes challenges you sometimes. My favorite moment was I was asking to build an agent for me and it said, "Can I build an employee agent?" And I said, "No, no, I want you to build a customer service agent." And it's like, "But that's a lot more metadata." And I said, "Yes, it is." And it said, "Okay, if you really want me to build it, that's the right thing to do, I'll go do it." But it just cracked me up, because I was like, "Really? Does it really make a difference?" Mike: I know. Tian Kruger: Just a little personality, it makes it a little bit more fun, but it'll do what you want it to do ultimately for sure. Mike: Yeah. No, it did for me. When I went back into the dashboard and I said, "Hey, I need to add an exit button because I realized I don't know how to get out of the dashboard without just closing the tab and I think that's really bad," and it replied, it was like, "Yeah, we probably should have done that to begin with, shouldn't we?" And I was like, "Folks, thank you for baking that in." Talking about building something new though, I know you guys have a demo and we'll put the demo in here in a little bit, but before I get to the demo, I do want to talk about one thing that you both pointed out to me, which is when you tell Builder Central to do something, it doesn't actually build it in your org. Can you explain that? Daivat Dholakia: Yeah. So historically, what we have done is if you are trying to build something new, you go to your sandbox and you're making changes to the metadata as you are building. Now the problem with that is rolling back metadata is extremely hard and extremely dangerous. So in order to avoid that, what we did in Builder Central is build this whole concept around how you can build in sort of a virtual environment, so that you can keep vibing on it, you can keep exploring, you can keep trying out new things, but at any point you're like, "Yeah, this is not going in the direction I wanted or actually I do not want this to affect my sandbox," you don't have to worry about it because it did not change any of your sandbox metadata. At any point you're like, "Yeah, this looks perfect to me now. I'm ready to push this into my sandbox," You hit a button and it publishes your project essentially the same as how you would in an Agentforce vibes project as a developer would do it. It pushes all of that into your sandbox and that's it. It gives you the peace of mind so you're not worried about like, "Oh, I'm going to mess up my sandbox." And that means that you can work, you can vibe, you can play around with it, you can explore and push it hard as much as you can. And then when you're ready, it is available for you in a single button. Tian Kruger: And I want to point out there's a really key piece to this. One of the number one questions we get, is "I already have Claude Code. Why do I need this?". Mike: Good question. Tian Kruger: Like, "What does it really give me?" I had two customers, we did a big workshop that started with that question. And after two hours of using it, they both said, "This is revolutionary. This is amazing." And I said, "Why? I love it. Yes, I agree. But why? Why do you say that?" And they all were in agreement that the fact that we give you visualizers and previews, so this means concretely, and you'll see it in the demo, concretely, when you generate a flow, even though it's just local, it's your project, you can actually see it. We actually load up a visualizer, you can see the flow just as if it's in your org. So that gives you the ability to visually see the way that you're used to seeing a flow, it looks just like a flow than it does in the org. You can see what you're building before it's ever in your org. This is a superpower, because it allows you to, as Daivat just said, vibe and revibe and tweak things and whatever, ever before it ends up in your org. In fact, one of our early renditions of the product about a year and a half ago, I actually found out that there's a custom object limit in the org in about two hours. I managed to fill up an entire org with custom objects in about two hours. So that's when we realized, we're like, "Metadata can be created, like it's no longer a difficult thing to produce." Producing the right metadata is important and producing it as efficiently and with as little impact as possible in your org is actually really important to help that flow feel more magical. And so yeah, it was really interesting to me to watch both of these customers go, "Oh, this is different. This is a different experience." And I was like, "Yeah, those visualizers." And we're adding more, by the way. We're adding more visualizers constantly to help you. So if people have strong opinions about which visualizers they'll use, tag me or Daivat on LinkedIn and say, "Hey, they help me visualize X, Y, and Z." We're looking for that input. Mike: Cool. Well, we've teased out the demo enough. So do you want to introduce the demo? And then for everybody listening on audio podcasts on iTunes, there'll be a video version of this over on YouTube, two versions actually. One will just be a replay of the audio and the other is actually the video one that you'll get to see the demo in. So I'll let you guys introduce the demo. Daivat Dholakia: Awesome. So the demo that we're going to have is about a branded customer that wants to create a site for support so that the users in the field that are customers, end users essentially, are able to go to this portal, able to ask questions about whatever problems they have, and at the same time, interact with an agent. The other piece that you will also see is a way where when you are trying to work on building out the agent, all you need to do is do inline editing. And this is one of the critical pieces, because what Claude cannot give you is a way to say, "Hey, I want to change this one very particular thing in this agent or in this flow or in the UI." Every time you are asking to make a change in Claude, for example, you have to put the entirety of the text saying, "Hey, on this particular page, on this particular agent, I want this exact change." And that means you're having to type out a lot of text to try and tell Claude that this is the exact change you want to do. Versus in Builder Central, because we have visualizations, because we have a way to edit in line, all you do is say, "Hit edit at the top," and then you will select a specific component you want to change and just say, what do you want to change over there. And the change can be as simple as, "Hey, I want to change colors of this particular component, or I want to change the text of this particular component." Or it can be, "Hey, I want to add this particular piece in this flow." Or it can be, "I want to change this particular agent to do an additional action." All of that becomes possible because of this editing piece that is extremely pinpointed, which no one else offers you today. And this saves you so much more time, because you're not having to type out everything and you're not going back and forth with the Claude agent or Codex or any other tool to say, "I actually want to make this change, but I need to tell you all of my details around it." It simplifies the whole process. And as we add more visualizations, we will have more ways for you to do pinpointed...
/episode/index/show/buttonclickadmin2/id/43729089
info_outline
What Does an Admin Certification Prove in the Agentforce Era?
10/29/2026
What Does an Admin Certification Prove in the Agentforce Era?
Today on the Salesforce Admins Podcast, we talk to Stacy Jacobs, Partner Ecosystem & GTM Leader at Salesforce. Join us as we chat about why certifications and knowing how Salesforce works is even more important when AI is helping you build. You should for the full episode, but here are a few takeaways from our conversation with Stacy Jacobs. Why Admins need to see the big picture Certifications are a rite of passage for every admin. But now that AI can walk just about anyone through how to build a custom object, are they still worth pursuing? I sat down with Stacy Jacobs, Partner Ecosystem & GTM Leader at Salesforce, to find out why certifications still matter and how AI can help you prepare for your exams. One thing that Stacy emphasizes is that as powerful as AI tools are, getting the most out of them requires a solid understanding of how Salesforce operates within your specific business context. Agentforce can help you put together all of the pieces, but it’s up to you to decide what the puzzle looks like in the first place. Investing in the human in the loop Certifications are more than something you put on your resume to get your first job. Even if you’re a veteran of the ecosystem, they can help you get up to speed with best practices for things like security models, native features you might not be using, and how to confidently build with AI. “We are the gas that’s powering AI,” Stacy says, “we have the long-term knowledge, the history of our organizations, the history of our industries, our platforms, and we have that common sense that maybe AI is lacking.” Certifications are an investment in the human side of this equation, and by deepening our knowledge of the platform we expand the possibilities for what we can accomplish with Agentforce. Building the right solution With Agentforce, it’s never been easier to build whatever we want. But how do you know if you’re building the right thing? Are you making an app that fulfills the requirements? Or are you making something that actually solves the problem? Many Salesforce certifications focus on the soft skills that help you make sure you’re building the right solution. As Stacy explains, these skills are more important than ever. In a world where AI can help you build just about anything, admins are there to build the best solution suited to their specific business problems. Make sure to listen to my full conversation with Stacy for more on certifications and how to prepare for them. And don’t forget to subscribe to the Salesforce Admins Podcast for a new episode every Thursday. Podcast swag Learn more Trailhead: Trailhead: Admin Trailblazers Group Social Full show transcript Mike Gerholdt: This week on the Salesforce Admins Podcast, we're talking about certifications and with AI making it easier than ever to get answers, build apps, and figure things out on the fly, you might be wondering, does certification still matter? Well, my guest today, Stacy Jacobs has some thoughts on that. Stacy works with Salesforce partners on certification and learning programs, and she's been a part of the ecosystem since the ExactTarget days. We're going to talk about why knowing how Salesforce works is even more important when AI is helping you build. How to use AI to prepare for your next certification and why experience and credentials aren't competing with each other. Plus, Stacy manages to beat me to a food analogy on my own podcast. I don't even know if I've still recovered yet. So let's get to our conversation with Stacy. So Stacy, welcome to the podcast. Stacy Jacobs: Oh, thanks for having me. Mike Gerholdt: Well, I think it's a really cool article that you also put out on admin.salesforce.com about certifications in the AI era. And I think I've thought a lot about this. I think we're seeing AI disrupt. Are we still disrupting? I feel like disrupting was a very 2010 word when we were coming out with apps, but maybe AI is also disrupting a lot of things. And certification is definitely one of them, but maybe not in the way that I'm thinking. So first off, I think let's start with what do you do at Salesforce around certifications and how did you get into the ecosystem? Stacy Jacobs: Oh yeah. So I've been within the ecosystem for several years. In fact, most of my career is within the partner ecosystem outside of Salesforce, and I've always wanted to be part of the mothership, and I've been here about seven years. Came in as a technical architect in ProServe, and now I am running programs to enable all of our partner audiences. And certification is a big part of that. So we run programs throughout the year to help enable, educate, motivate all of our partners within the ecosystem to get certified and learn more about our products. So that is a little of what I do. Mike Gerholdt: That's really cool. ProServe, what does that stand for? Stacy Jacobs: Yeah, it's professional services. Mike Gerholdt: Ah, okay. It's not like the tennis machine. Stacy Jacobs: No. Never been a tennis player. Mike Gerholdt: Me either. Stacy Jacobs: Ball [inaudible 00:02:53]. Mike Gerholdt: That's why I was like, wow, we have a whole department of people that just sell. Nevermind. People that listen to the podcast know there's always going to be a few bad jokes right away and then probably some food worked in somewhere, although everybody's going to be at the edge of their seats to see how I work food into an AI certification podcast. Stacy Jacobs: Maybe also [inaudible 00:03:14] too. Mike Gerholdt: Buckle up. Just wait for it. It'll be there. So I think what's interesting is when you first came to us and started talking about certifications and AI, I immediately went to, oh, well, obviously people are just using AI to pass the certification, but I think it's a little bit different than that. It's also getting certified in AI, correct? Stacy Jacobs: A little bit, yeah. We have a lot of AI aspects to all of our certifications and it is definitely sprinkled in as a common theme around the board for our products. So naturally it's going to be part of our certification process and I think we need to embrace that. Mike Gerholdt: Yeah, absolutely. Now, so I was looking back a few years ago because I remember the first time I was introduced to a cassette tape, my mom showed it to me and how you could rewind it with a pencil. So everybody that's my age and older knows what I'm talking about and everybody younger is like, "What are they doing? Thought this was a Salesforce podcast." I also remember the first time I was kind of, I'll call it introduced to AI, and it was Josh Burke got on a team call and he talked about, I forget what it was called, but he's like, "I just told it to render a cat on a pirate ship and here's the image." And I was blown away because up until that point in my life, if I wanted a cat on a pirate ship, I would've had to Photoshop or do some work. And this was just a prompt that he told me. And I look back at that now as like, wow, that's so easy to do because I think my understanding of AI, I know my understanding of AI has increased, but also the tools have gotten so much stronger and so much smarter, I'll call that. How in the certification world do we keep up with certs and the rapid pace of how AI is developed? Stacy Jacobs: Oh man, one step at a time. I mean, one of my most favorite sayings is asking somebody how they multitask and nobody can do everything altogether. We always do one task at a time. So it may be overwhelming at first seeing how many certifications we have out there, the advances we're making in all of our products. But I guarantee you, if you learn little bits here and there, you can reach any goal that you set your mind to. And I've actually used AI to help study for certifications and I encourage a lot of folks to do that as well. It's not as much of what questions are on the exam and how do I get answers to all the questions on the exam? That is not something that anybody should be doing. But for the matter of gathering all the materials that we have out there to help enable not only any audience out there, anybody looking to learn more, that is a powerful thing that we have now that we did not have back when I started my career. And I was reading PDF documents and printing out papers and taking notes here and there. But now we have wonderful skills in Slack that can help you study for exams as well. So little bits at a time, you can't multitask everything and definitely just do one thing at a time. Mike Gerholdt: Right. Yeah, no, that's actually a really good point because a lot of the AI, I always feel like I sound old, like the AIs out there. There's a comedian that's like sound old, you just add the and pluralize it. The AIs out there. But they have access to a lot of information and you think of they could pull all of that together and then start quizzing you to really help you prepare. Because I know when I read material, I consume it a certain way, but then I never think back to, well, how will the question come that's going to quiz me on this? So very good point. Stacy Jacobs: Yes. Mike Gerholdt: One thing that as we kind of head into this, so it's a brave new AI world, there's a huge maturity curve in our Salesforce ecosystem that I think a company we're just starting to really realize Salesforce is 27 years old. Which is nuts because I remember starting working in the ecosystem and I was like, oh, Salesforce not even 10 or whatever. But because of that, there's a lot of people that have been doing Salesforce for a long time. They've seen the evolution of, they were around when Chatter was launched or Service Cloud and they've seen the tools released, they've seen the features come about. They've implemented them, they've seen them sunset, their skillset is pretty solid. Why would somebody like that go and get just any Salesforce certification, let alone an AI certification? Stacy Jacobs: Yes, this is something that I hear a lot too, Mike. And first off, I never downgrade any experience anybody has regardless if it's with Salesforce or not. I think that's what makes us human and being a human is a big part of this AI world we're living in. So what I would recommend everyone thinking about, encouraging them to be open-minded about is that you may learn something. If you're somebody who's been within the ecosystem for the 27 years, you might be surprised at what might be under the hood that you can turn on out of the box and all of that. So when you're fine-tuned in one organization, in one org or one mindset, it's really hard to see what you're missing. And certifications really help you hone in on the fuller picture. So understanding more of those security models, the native features that maybe you're not using because we all have bad habits and we're not adopting best practices, but certifications help you stay on top of what those best practices are so that you can scale even easier for the AI future we're in. There's a lot of things that we're building on top of, especially the platform that AI is loving. And if you are using it now and if you can massage your organization into some of these standards, you'll be able to scale and go way further with AI. So that's why you should get certified. Mike Gerholdt: So let me ask you then, because I can see people sitting back and saying, "Well, I mean, if there's apps out there that'll help me, I could just go to any one of these AIs, ask it a question, how do I build a custom object in Salesforce?" And it'll tell me that and I can kind of prompt my way through building an app. What's the benefit if AI is available to bring us all of that information on demand at my fingertips, do I really need to spend all that time studying for a certification? Stacy Jacobs: Yes, I think you do because we are the gas that's powering AI. We have the long-term knowledge, the history of our organizations, the history of our industries, our platforms, and we have that common sense that maybe AI is lacking. I don't ever recommend an AI situation where a human is not in the loop. And so us understanding what the platform is, how it works, and being a Salesforce admin really sets you up for success. It sets your organization up for success, and it sets the AI that you are buddying with, becoming your coworker with, up for success too, because you have that knowledge and that experience that you've had for years that you can bring to the table and fine tune the AI logic in ways that even it couldn't even imagine, right? We're in this together. So absolutely, it's definitely worth getting certified. Mike Gerholdt: Yeah, and I didn't mean to impromptu put you on the spot, but the other thing I would add to that, again, Josh pointed this out to me, I feel like this podcast is, here's what Mike knows in terms of what Josh has taught him. Mike's learned other things. For a long time, if you asked a model how many Rs were in strawberry, it told you one or two and there's three, and then you'd ask it to spell it for you and it'd spell it with three Rs and it would still confidently respond, "Well, there's only one or two." And I think that's also part of the difference of getting that certification and going through and getting that experience. Of I hear what you're saying the answer is AI to building this app, but you're making this part up because you don't know and you're doing it. And I feel like there's a term for this, I should look it up, but there's a term for when AI tells you something so confidently, even though it's making it up. Stacy Jacobs: Yeah, it's hallucinating. It's definitely hallucinating. So the way I look at it this, and Mike, I'm going to beat you to this food insert to our podcast today. Mike Gerholdt: Oh, look at that. That doesn't happen. Stacy Jacobs: But here's how I think about it. So we are starting to speak the same language as AI. We are definitely in this together. We need to be coworkers, we need to be colleagues, we need to be best friends with AI because you're starting to speak the language of AI. Now, I like to think of this as you're ordering food. Let's say we go to a restaurant, you might have a general idea of how a pizza is made, but if you don't know the typical ingredients, you might really be surprised once it comes out and there's cheese on it. And if you have a dairy allergy, that is a huge problem. So once you know it comes with cheese, once you know you're speaking the same language as the pizza makers, you have a general idea of what a pizza consists of, then you can start customizing it. You can order it any way that you want with, even without cheese, you can add items on there that you enjoy, maybe your audience enjoys. You can customize all of that and get exactly what you need. So AI really works the same way. So let's take this and transfer from pizzas into the platform. So if you ask it to build a flow, if you ask it to design a data model and you really don't know what any of that means, you're going to take whatever it gives you and it might hallucinate. It might pull in personal information that should not be there. So thinking of highly regulated industries, but these are all things that you learn when you go and get certified. You understand the components of the platform, you understand what it's built up, you know what an object is, a custom one, a standard one. You know how it all fits together, and that's how you can work with AI to kind of build your pizza. Mike Gerholdt: Yeah. That's a really good analogy. I can't believe you beat me to the food analogy. I'm stumped. So there's a TikTok I keep seeing where a guy walks in, orders pineapple on his pizza. Where do you fall? Are you pro-pineapple, not pineapple? Stacy Jacobs: Maybe once a year I'll do pineapple, but only because I'm really hungry. Mike Gerholdt: Yeah. Yep. Stacy Jacobs: But I don't order it. Mike Gerholdt: I've done it once. Stacy Jacobs: If it's in front of me, I'll eat it just to be polite, but I don't go out and say I want it. Mike Gerholdt: No, there's five people in the world that crave pineapple and ham pizza. Just made me think of that. You really brought up another interesting point, which is once you're certified, it's kind of like the beginning of your learning because we also have maintenance exams, right? I mean, actually they're Trailhead modules now. Stacy Jacobs: Right. And they are so nice in Trailhead. And those are really, really important too. I always encourage everyone, if you're going to spend so much time studying and learning and applying yourself to something that stays with you, you better keep it. And these modules only take minutes to complete. They don't take months, in some cases, to study for some of these exams. They can be quicker than that, but keep what you earn and definitely stay up in the know with the latest and greatest because it really prepares you and all of your decisions in the future when it comes to career. Yeah. Mike Gerholdt: I mean, and getting certified, I know the few times I've been certified, getting there and then taking that exam is not cheap. I don't want to scare people away with price, but to your point, if you're going to spend money on the investment, don't just do it for a one-time thing, do it because it's durable and you can maintain it. I think the coolest thing that we did was moving to Trailhead for the maintenance part of it because you can get hands-on and actually see some of it. I know some of it is just multiple choice answers, but some of it you can really get hands-on and do and actually, oh wow, be a part of that. Whereas a hundred years ago, we would just get a developer org that had the newest release enabled, and then it was up to you to figure out a scenario to use it. Stacy Jacobs: Yeah, absolutely. It was such a game changer, especially in the marketing cloud world where I come from. But really having everything in there in an easy to digest and kind of a fun format, right? Everyone likes to get points and earn badges and things like that. It definitely changed my perspective and my willingness to go and keep my certifications because it is an important piece of our ecosystem pie here. You know, you have your experience, you have your certifications, and then we have AI and all three together, just kind of a super place to be right now. And that's what motivates me and my role and how important it is for all of our ecosystem to understand we're in this together and all these three things definitely do matter. Mike Gerholdt: Yeah. You bring up a point that I can't believe we didn't talk about, but you're not just at Salesforce having been part of the ecosystem and, oh, now I'm on this team and cheering for certifications. You're actually certified. Stacy Jacobs: Oh yes. Yeah, absolutely. Mike Gerholdt: What was one of the driving factors for you to get certified even before you joined Salesforce? Stacy Jacobs: Yeah. Back in the day, I was a marketing cloud administrator back when it was ExactTarget before the acquisition. So that kind of time stamps me here, but I knew there was more that we could do with the organization I was a part of. I knew personalization was really important. I knew because of my marketing background, a target audience and understanding what they want and listening to their needs and what they value in the messages they were receiving. Whether it was marketing or... I'm sorry, through emails or through SMS, I knew that we could do more than just blast emails out, but I didn't have the eloquent ways to talk about it then. I just knew that the platform controlled and had this power that I wanted to unlock for my marketing audience here. And so I decided to step out of my comfort zone, understand what it was the platform was. And mind you, this was way back in the day when Marketing Cloud was acquired by, or ExactTarget was...
/episode/index/show/buttonclickadmin2/id/43518774
info_outline
Winter ’27: What Admins Should Check Before Their Org Upgrades
10/15/2026
Winter ’27: What Admins Should Check Before Their Org Upgrades
Today on the Salesforce Admins Podcast, we talk to Jennifer Lee, Lead Admin Evangelist at Salesforce. Join us as we chat about all the cool new features coming in the Winter ‘27 Release, including Builder Central, Setup with Agentforce, and what’s new with Flow. You should for the full episode, but here are a few takeaways from our conversation with Jennifer Lee. Admins are agent-powered with Builder Central and Setup with Agentforce First of all, this is the first week with our new format, there will be a video version as well. Coming soon to the Salesforce Admins YouTube channel to see demos, clips, and visual explainers for each episode. Today, we’re looking ahead to the Winter ‘27 Release with Jennifer Lee to find out which new features admins need to know about. One thing that generated a lot of excitement at Dreamforce is Builder Central. It’s an intelligent, agent-powered workspace where you can build, test, and deploy solutions using natural language. You really need to see it in action to understand how powerful it is, so check out the video for this episode, where we have a demo for you. Setup with Agentforce is also now generally available (GA). This tool simplifies so much about managing users, configuring your org, and troubleshooting user access issues. Jen’s found it to be especially helpful for reorganizing role hierarchy and, in general, taking control of permissions in your org. Three Flow enhancements to make your life easier Jen highlights three Flow enhancements that she thinks will have a big impact for admins: Edit History allows you to review, restore, and reuse past versions of a flow. If you’ve ever found yourself staring at a broken flow and asking yourself why you can’t just go back to a version that worked, this enhancement is for you. Also new in Winter ‘27, you can now process multiple records with Screen Flows from List Views and Related Lists. This makes it easier than ever for your users to do bulk updates with a quick mass action, without having to leave the screen flow they’re already working in. Finally, Test Mode (Beta) allows you to debug and test in Flow Builder in one place. You can save manual tests so you’re not entering the same criteria over and over again, and use them to build an automated testing suite. Jen’s steps for release readiness The wonderful thing about Salesforce is that a new release is always around the corner. For Jen, release readiness comes down to four steps: Plan and learn Get hands-on Test Communicate with your team and users The good news is that by reading this post, you’re already doing step 1. So my advice is to pick one new feature for this week’s episode and spend some time exploring it. As admins, we learn so much more when we get our hands dirty and start building. Make sure to listen to my full conversation with Jen for more highlights from the Winter ‘27 Release. And don’t forget to subscribe to the Salesforce Admins Podcast to catch a new episode every Thursday. Podcast swag Learn more Salesforce Admins YouTube Channel: Salesforce Admins YouTube video: Salesforce Admins Blog Post: Salesforce Admins Blog Post: Salesforce Admins Podcast Episode: Admin Trailblazers Group Social Full Transcript Mike Gerholdt: Welcome to the Salesforce Admins podcast, this week I'm joined by Jennifer Lee to walk through Winter '27 Release readiness, including Builder Central setup with Agentforce Flow and some of the features that admins should be paying attention to after Dreamforce. Now, hey, quick heads up, if you're listening on Apple Podcasts, Spotify or wherever you get your podcast, there's a video version of this episode over on our Salesforce Admins YouTube channel and this time it matters because we're actually dropping demos and clips into the conversation. Now, don't get me wrong, you'll still get the full discussion right here but you're going to miss out on some really fun stuff by not seeing the video one. So, go check out that video version on YouTube, let me know what you think, in the meantime, let's get Jennifer on the podcast. So, Jennifer, welcome to the podcast. Jennifer Lee: Thanks for having me. Mike Gerholdt: Yeah. Well, it's October, it's post Dreamforce time which means we got to start paying two releases and you put out an amazing release readiness blog. We've also gone through Dreamforce, there's been iterations of stuff being updated so I figured why not have Jennifer back on the podcast to talk about everything that we saw at Dreamforce, everything that was in the release and maybe, I think, some stuff that missed your blog or needs to be updated. Does that sound current? Jennifer Lee: Yes, that makes sense. Mike Gerholdt: Okay, perfect. Well- Jennifer Lee: And I had to get all dolled up for this episode. Mike Gerholdt: I know. It's a video podcast so, for those of you listening on iTunes, there's a video version of this over on YouTube where hint, hint, there will actually be GIFs and video demos to watch so stay tuned. Hopefully it turns out, it's early, here we go. First thing I want to talk about is one of the cool ... There's a lot of cool stuff that we launched at Dreamforce but Builder Central. It was right after the keynote with our Salesforce live content, it was featured in the admin keynote. I hadn't had a chance to really play around with it until after Dreamforce which is now. You've had a chance to see it and interact with it but tell people about Builder Central if they skip past it. Jennifer Lee: All right. So, what Builder Central is, basically, it's a tool where you go in and describe what you want. You can describe the app or the agent in plain language and then the build agent goes and does all these things and it creates this plan for you, describes all the requirements and then it goes and builds all the things and you can go in and preview the items and make tweaks to it. And then, when you're ready, you can go, say, deploy from your sandbox to production. Mike Gerholdt: Yup. Yeah, it builds it. So, I talked to the PM just this morning, it builds it in a virtual environment because I had no ... I was like, "How is it doing this thing? Is it changing stuff already?" He's like, "No, it's a virtual environment and it doesn't change anything until you deploy." Even in a sandbox, you deploy it. So, I used it, it was so cool. I think it was so cool because it's just top of mind, you're like, "Hey, could you give me this?" And, spoiler alert, I had it create a screen flow. Not that I can't create screen flows, I can, it just takes me a little bit and Builder Central just cranked it out, no problem then it was like, "Hey, do you want to add this to a page?" and I said, "Yes." And then I could go back ... The cool thing is then I could go back in and I could actually see the flow components that were built, to me that was like, "Ugh." This is so much easier not because it's building it for me, it is, but because now I can learn and go back and see what are the components I should have built as opposed to getting frustrated that I don't know what the right thing is to build next. Jennifer Lee: Yeah. The great thing is, in that preview mode, you can go in and drill into the data model and you can actually see the things versus it just coming back and saying like, "Oh, I did these things for you and here's just a list." Mike Gerholdt: Right, yeah. Jennifer Lee: The fact that you can actually drill into it and look at it is really cool. Mike Gerholdt: Yup. And it doesn't just duplicate stuff. It looks at your org and says, oh, well we have this, let's integrate this. It really feels like, man, if I would've had that as a new admin, it would help me jumpstart all of the things that I need to build. And could you go over your skis building a little bit? You could but I think the onus is then on you to go back and learn all the things that it built and why it built it. Jennifer Lee: And I love that it puts that human in the loop piece, it just doesn't just do it for you. You're going in and you're like, "Okay, this wasn't quite right so I'm going to tweak this a little bit," but, yeah. Mike Gerholdt: Right. It's currently in beta, right? Jennifer Lee: Correct, correct. So, this is the time where folks can go in and just kick the tires and check it out. Mike Gerholdt: Yeah, I can't, I can't wait. Actually, one thing we're going to do so, if you're listening to the audio version of this, jump over to YouTube because right now I'm going to put in a demo of Builder Central. Okay. So, that was the demo that the PM team put together of Builder Central, I think it's really cool, it's also the demo they showed in the connected content. It only begins to scratch the surface, I think this is the strongest V1 product I've seen us come out with in terms of just admins having a superpower. It needs a cape, Builder Central should get its own cape. Jennifer Lee: Let's totally make one. Mike Gerholdt: I know. So, there's a lot of other tools. Set up with Agentforce is one of them, let's talk about that. Jennifer Lee: Yeah. So, folks, if you're in my release notes blog, notice that I don't nearly have as many of the setup with Agentforce features that are currently in the release notes so don't come at me for that but let me just highlight a few that weren't in my blog. So, Data 360 is no longer required so that's great but do note that there are some specialized tasks such as, if you're using related list enrichments and custom report types, that will still need Data 360 so just keep that in mind. They also streamline the enablement page so it's easier to enable set up with Agentforce in your org and, previously, you needed to separately assign two permission sets to each user and now they bundle that in a perm set group. So, you just need to assign the perm set group and you're all set to go with your users. Mike, back in the day, I would've loved to have this and have an agent do this but now you could manage your users in bulk, you could freeze a bunch of users, unfreeze a bunch of users or specify here's these users that need their password resets instead of doing it one by one by one because who has time for that. Mike Gerholdt: Period. Just that alone would make me happy. Jennifer Lee: Mm-hmm. So, for your profiles, you can go into the setup agent and you can say does this user profile have added access opportunities or which profiles have the customized application permission and it'll come back and surface that for you like just asking an agent. You don't even have to go through and click every single profile page, that's time-consuming. So, with summarizing permission sets, permission set groups and having it surface up the information you need without having to, again, do those manual clicks. Another thing is, if you have a major reorg in your role hierarchy, you can just subscribe it to the agent and then it'll just reorganize your role hierarchy for you. Can you imagine back in the day you have to manually row by row, yeah. Mike Gerholdt: I'm just thinking of, of all the parts of my Salesforce org that got the most stale, role hierarchy was it. You almost set it up and then you get elbows deep in building apps and onboarding users and role hierarchy is the first thing that gets out of date. Jennifer Lee: Yeah. And then one last feature I'll mention for setup with Agentforce which I do mention in my blog is the org health and usage metrics dashboard. Now, we provide all sorts of metrics to you but now you can go in and say these are the ones that are important to me so I could favorite those and you can say these are the ones that I don't care about and then they're hidden so that you basically customize it to what's important to you which is really cool. Mike Gerholdt: I like that. Was that in the admin keynote? I feel like a version of that was. Jennifer Lee: A version of that ... So, I think you're thinking of security center essentials. Mike Gerholdt: Oh, essentials, yup. Look at that, we have more than one tool for a thing. Jennifer Lee: Imagine that. So, should I continue on with a couple of other features for- Mike Gerholdt: Oh, please. Jennifer Lee: Okay. Mike Gerholdt: Because I think there's other stuff that you wanted to talk about. Jennifer Lee: Yes, absolutely. So, in a record, when an owner leaves the company, you naturally will assign a new owner to that record. Now, if that record had any manual shares with it, those manual shares just evaporate into the ether when you assign it to a new user so then you're going to have John Smith knocking at your door as an admin saying, "Hey, I had access to this record, now I don't." But in this release, you can go into sharing settings and then enable keep manual shares when transferring records and enable that checkbox. And then org-wide, once that happens, it will take that manual share and move it along to that new owner so you don't lose any of that record access so that's great. Mike Gerholdt: Oh, my God. Yeah, nobody keeps track of that. Jennifer Lee: Exactly. Mike Gerholdt: When a user asks another user, "Hey, can you share this?" and they click share, there's no log for that. Jennifer Lee: Nope. Mike Gerholdt: Oh, man. And what's crazy is you wouldn't know it until somebody has to go to that record which could be eight months after a person left. Jennifer Lee: Right, right. And then you're like, "Well, how did you get that access?" Mike Gerholdt: Right. What have you been snooping around on? Jennifer Lee: And then digging through the setup audit trail to figure it out, yeah. Mike Gerholdt: Oh. Jennifer Lee: Yeah, no. Mike Gerholdt: Just don't set up audit trail into an AI and be like, "Help." Jennifer Lee: Mm-hmm. Or you set up with Agentforce. Mike Gerholdt: Right. Jennifer Lee: So, another feature for reports is that now you can preview a record within the report and it doesn't jump out of the report, you can preview it within the context of the report. Now, to use that, you need to enable it so you need to go to the reports and dashboard settings page and then there's a feature called show record previews on lightning reports beta. So then, once you do that, when you're in the report mode, you have to click on this little icon that looks like an eye and then you click on any of the record links and then they'll open up in the side panel. Mike Gerholdt: That's cool, wow. It's been a while since I've built reports, that was probably the one thing I always tried to shy away from as much as possible. Jennifer Lee: Same. Mike Gerholdt: Thankfully, now we can just have Coworker build things for us, I don't know. We would be remiss to ... I'm surprised we've made it this far and haven't talked about Flow. Everybody's sitting here like, "You awesome, you have Jennifer Lee on the podcast and for 12 minutes you don't talk about Flow." Jennifer Lee: Well, I saved the best features for last. Mike Gerholdt: I know. I was going to say, right, you got to ... Ironically, it's why they put the milk at the back of the grocery store because everybody needs milk and they just want you to walk past the aisles of canned chili to get milk. Jennifer Lee: So, as always, kudos to the Flow team because, with each release, they're rolling them out, there's just a lot of them. Mike Gerholdt: Yeah. Jennifer Lee: I'm not going to possibly go through all of them, I'm just going to pick three that I'm going to highlight. Mike Gerholdt: Okay. Jennifer Lee: So, the first one is being able to review, restore and reuse past Flow versions. It's 4:00 p.m. on a Friday, you're looking at a Flow that's broken and then you're trying to figure out where it went wrong and who changed it and what happened, well, now you can go into the edit history when you're in Flow Builder and you can see every single change that was made. You can see which elements were changed, you're able to then restore to a previous version or copy the logic into a new Flow. So, that just really makes the troubleshooting and whatever changes you need to make so much easier instead of back in the day where I had different versions of flow and trying to figure out is this different, is this not? Mike Gerholdt: All of us did. Jennifer Lee: Crazy. Mike Gerholdt: I know. And the number of times that I would have to ping Jennifer Lee and be like, "Why doesn't this Flow do this thing?" And she'd be like, "Because you didn't check a box," ugh. Just go back to the version that worked before I broke things. What else can we do in Flow? Jennifer Lee: Well, on Screen Flows now. So, from a list view or related list, you can check the records so check the records and then specify the Flow action and then that will take those selected records and process them in bulk. So, instead of having, for example, you're on one record and you're clicking a Screen Flow or autolaunched flow and having it processed for that one record, you're on a list view and you're like, "Okay, well, I want it to happen to these multiple records so I'm just going to select them," and, boom, it just happens for all of them instead of having, again, to go one by one by one. So, this is something I'm really excited about because I wish I had this when I was back as an admin way back when. Mike Gerholdt: I could imagine. Jennifer Lee: Because I told my users, sorry, you have to do it one by one, can't put it on a list view. Mike Gerholdt: Yeah, nope. We have some stuff in beta for Flow as well, right? Jennifer Lee: Yeah. So, the last thing I'm going to talk about is Test Mode which is in beta. So, in Winter '27, when you're building your Flows, you're going to have a little build tab and then a test tab and all your testing and debugging is now going to be in one place which is great. And so, there are a bunch of features that come with Test Mode. So, when you're working through a Flow and you're having to iterate through and test and test and test, know that now you could save that manual test so you're not entering the same criteria for your records over and over again, you save it and then you just reuse that. So, there's a lot of reuse so that's great for as you're building a Flow. And then, when you're ready to activate it, you don't want to lose any of that test so then you could promote it to become an automated test where you have assertions. So, assertions are a developer term but essentially what it means is you test for something that is positive. So, if your Flow creates a task, you want to test that as part of your process, a task was created. So, the great thing about automated tests is, once you built them, it's there forever so then, when you go and test your Flows, when you make a change to it, you want to then go and test to make sure nothing breaks, you don't have to manually test them, you can now go and say, "Oh, I want to run this entire suite of tests for this one given flow or I just want to run these couple," and it does it for you. You don't need to manually go in and manipulate records, it just remembers it. Now, another thing is if you have Flows that call another Flow or maybe you have an HTP call out, when you do your testing, you want to isolate those other pieces because those would've been tested elsewhere, you don't want to test an integration every single time and a subflow would've been tested in and of itself so you want to isolate those out and really focus on the main flow. So, now you can do that with specifying mock outputs for your actions and subflow elements. And then, lastly, when you're testing records, there are records that aren't easily searchable. So, examples would be case or campaign but you know the record ID so you have the option now, instead of searching for a record, if you have that record ID, you can pace either that 15 or 18 character ID and then use that to test your Flows. Mike Gerholdt: Ooh, that's easy, I like that. Jennifer...
/episode/index/show/buttonclickadmin2/id/43294619
info_outline
How Do I Decide If a New Salesforce Feature Belongs in My Org?
10/01/2026
How Do I Decide If a New Salesforce Feature Belongs in My Org?
Today on the Salesforce Admins Podcast, we talk to Alastair Dinning, Senior Solution Architect at Salesforce. Join us as we chat about the process of adding new features to your org, from what to look for when you’re reading through release notes to rolling something new out and driving adoption. You should for the full episode, but here are a few takeaways from our conversation with Alastair Dinning. Which new features should I pay attention to in the release notes? The exciting thing about working in the Salesforce ecosystem is that it’s continually evolving. A new release is always around the corner, chock-full of new features that could improve your org. But how do you sift through everything to figure out what will add value and what’s just a shiny new toy? My guest this week is Alastair Dinning, a Senior Solution Architect with Salesforce Professional Services. He has 14 years of experience as a consultant for businesses of all sizes, helping admins change their orgs for the better. For Alastair, the most important thing when you’re looking through release notes is to have a clear understanding of your business processes and problems. Do any of these new features address a pain point? Whether you practice SABWA, run a steering committee of power users, or use a case management system for feedback, you need to have your finger on the pulse of your users. Three pathways for adding a new feature to your org Once you’ve identified a problem you’d like to address, Alastair lays out three options: you can build a declarative solution yourself, you can buy a solution off of the AppExchange, or you can work with a developer to code something custom. Building your own declarative solution means that you end up with something that’s tailored exactly to your specific business requirements, but it also costs you resources in terms of time. Buying something off the AppExchange, on the other hand, costs you money up front, but you’re saving a lot of time and can deploy the change quite quickly. Even if the solution isn’t 100% right for your specific problem, Alastair encourages you to reach out to the AppExchange partner because they’re often willing to make improvements. Finally, coding a custom solution is probably the most expensive in terms of internal resources, but gets you exactly what you want. The drawback here is flexibility. You don’t want to end up with a solution that you can’t update if your business context changes in the future. Know when to keep Salesforce steady for your users If you’ve spent time with your users and really understand their pain points, adoption should come easily. But at the end of the day, the job of the admin isn’t to constantly roll out new features—it’s to make life easier for your users. Sometimes, the best thing you can do is to keep your Salesforce environment consistent and stable. That means not only identifying which new features could possibly be helpful for your org, but having proactive conversations with leadership about the bigger picture. Make sure to listen to my full conversation with Alastair for more about how to roll out new features to your org and how admins can best work with consultants. And remember to subscribe to the Salesforce Admins Podcast so you never miss an episode. Podcast swag Learn more Salesforce Admins Podcast Episode: Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins Podcast, I'm talking with Alastair Dinning, a senior solution architect with Salesforce Professional Services about how admins can decide if a feature is right for their org. We're going to dig into how to spot the business problem behind a feature, when to click, buy, or code your solution, how to prototype before making a big investment, and why timing and support ability matter just as much as functionality. So next time you find yourself reading the release notes and thinking, "Oh, that looks cool," you'll have a framework for deciding when to implement it. With that, let's get Alastair on the podcast. So Alistair, welcome to the podcast. Alistair Dinning: Thank you, Mike. It's good to be here. Mike: We connected ironically over Slack. Not ironic. Is it ironic? I always get hung up because I'm afraid I say ironic because I learned irony from Alanis Morissette, but we connected over Slack because you're a fan of the podcast and you work at Salesforce. And I was like, "Hey, I have this topic that I think you're perfect for." So let's start off by you letting everybody know what you do at Salesforce and how you got there. Alistair Dinning: So I am a senior solution architect with Salesforce Professional Services. I've been at Salesforce for give or take five years. I've been working in the ecosystem for 13 and my entire career has been as a declarative consultant and into being in the architect world. And I came to Salesforce through the acquisition attraction on demand and having spent my whole career, my Salesforce career in Salesforce consulting. So I've worked with a good number of organizations, whether they be small business, medium business, large business, government. I'm working currently with the Canadian federal government. I've worked with education, with nonprofit. And I mean, as a consultant, that's my approach to this job. And it's like, how do we as admins do things declaratively and do things well? And what can we bring to the table? Mike: Yeah. Wow. Worked with government. You must have a lot of scissors to cut all the red tape. Alistair Dinning: Yeah, government does bring a lot of red tape with it, but you make sense when you're talking about taxpayers' money. Mike: Yeah, no. I mean, it's all intentional for a reason. So let's talk... One of the biggest questions I always get, and it's a question I had as a Salesforce admin, which is how do I decide if this feature is right for my org? And feature could be anywhere from the biggest feature do we flip on? At one time we had customers had a choice of turning on lightning all the way down to the smallest little checkbox that maybe we added. And I was reading through some of the stuff that you do at Salesforce and I thought it'd be great to have that conversation with you about helping admins figure out if a feature is right and maybe give them some of your thought process into that. So I think that's where we'll start. Alistair Dinning: Absolutely. So one of the fun things about Salesforce that I've always appreciated is the three releases a year and the fact that we get new functionality every four months or so, and there's always something that's in those release notes that's exciting. And again, the advantage of having been a consultant is I've seen all of these different organizations and I see these new tools coming from the release notes and I'm like, "Oh, that's cool. That's really fun, and I think that's going to add value." But to your question, is it just this shiny new toy or is it actually going to add some real value into the solution? I think I always start with, "Okay, so that looks cool, but how is the business going to utilize it?" From two points, either is there a business value that we can add with this new feature or is there a pain point that I as an admin have seen, I've heard from my users time and time and time again where they're all like, "I don't like this. I don't like this. This is a slow process. This is in my way," boom, boom, boom. And does this new feature address that pain point? So if I was to take Dynamic orms in the Lightning Page Builder, they're super cool because we could do all sorts of fun things with it. But it's only useful if, for example, the business say to me, "Hey, my page layout is completely cluttered with all this stuff that I don't use at the beginning of a opportunity process. So why do I have deep fields on or a whole ton of fields on opportunity development when really we're just trying to identify what the opportunity value might be, value prop might be for this customer?" Mike: I think that's a great start. And I know I thought of that. I'll say this, I would really love it if the business was as explicit as you say they are like, "Oh, there's really this problem with too many fields." I think oftentimes you have to peel back a layer and listen to users say, "I'm just struggling to find the right information on this page." Or I remember when I was an admin, we brought on a different business unit and I remember the business unit asking why there was this entire section of the account page and it was kind of in the middle and it was above all of the information that they needed. And I said, "Well, if you don't like it, you can just collapse that section." And they said, "Yeah, but shouldn't it know whether or not it should show that to me?" And this was before Dynamic Pages. And so I bring that up to say, I hear you. I wish it was that explicit, but sometimes you almost have to listen and put two and two together for them. Alistair Dinning: That's right. It can be hard for the business to know how to articulate what they want from the solution. But as an admin, there are a couple of tools you've got. One is you could spend some time desk side with your key users or have a steering committee of users who are giving you feedback on a regular basis on what they're using, what they like, what they don't like. The other option is that if you have an ITSM light solution where you've got case management, so your users are providing functionality cases or technical cases on Salesforce, on their usage of Salesforce, then you can actually scroll through the data and see what people are saying, "This works for me. This doesn't work for me." And I mean, if all the cases are coming around a particular topic, then you know that there's a problem there and that's got to go in your admin backlog of things to address in due accord. Mike: Yeah. And I think you mentioned the three releases a year. Obviously we're always working to solve issues that enough customers have brought up, maybe not specifically in your case, but somebody has that issue. That feature didn't just get born out of a wishlist. It got born out of somebody really had that pain. I also think you bring up an interesting point of, so when you're looking at, should I just implement this feature? Is it actually solving a real problem or do I have to invent the problem or is there a better way to solve that problem? Alistair Dinning: So when we come to, is there a better way to solve that problem, there's a three step process that I've always applied to implementing functionality in Salesforce. And there's two steps to this process. One is those, are we going to click it? Are we going to buy it? Are we going to code it? In terms of solving the problem for the business requirements? We've identified a business requirement. We've said, "We need to fix it." Can I declaratively solve this problem? Can I just build it out of the box with the tools that come? And I mean, I'm a declarative consultant. I don't write code. So could I do it? Can I build a piece of functionality that's going to allow me to do that? Do I want to buy it or do I want to install it? So do I want to go to the AppExchange and pull something from the AppExchange that's going to solve the problem because this is a problem, to your point, this is a problem that multiple people have had. And so somebody else already went and built the solution and put it on the AppExchange. So we already know that those requirements exist. We already know that the solution exists and somebody's taken the onus of really digging through that solution and thinking through the problems and debugging the solution, whether they've built a very comprehensive declarative solution or they've coded a solution and they've put it on the AppExchange and just made everybody else's life easier. And sure, do you have to pay for that product? Most of the time, yes. But does that take away from you having to invest in development time? Also, yes. So paying somebody for a solution off the shelf can be a lot easier than coding it, but then coding it is our third option. So you've looked at the declarative solution, you've gone, "This isn't quite going to solve the problem the business has brought to me." You've looked at the AppExchange and there's nothing quite there that's going to fit the bill. Again, this isn't solving the problem the business bought to me. So then yes, then you're into the point where you want to code a solution and work with your developers, work maybe with your UX team, work with your testing team on actually coding out a comprehensive solution to solve the problem, solve that business requirement that was there in the first place. But that's a heavy investment. So the flip side to that is that if you were to declaratively build it, can you get 80% of the way to the business requirement, whereas a coded solution would get you 100% of the way there? If you declaratively build it and you get 80% of the way there, what you also get is a lot of feedback from the business before you make a big investment in coding a solution. And that accelerates your development path, gives you a lot of feedback into what your coded solution might look like, but it does help you mitigate the cost and stop you going down the wrong path because your view as an admin as to what the business is after versus their feedback when they start road testing something in production is going to be two different things. So either declarative and be done with it or declarative and use that as the prototype to inform your development path, again, assuming there was nothing on the AppExchange that met that requirement. Mike: Right. Or a hybrid of the two. I know there's some AppExchange apps that you can even add on to. Alistair Dinning: Oh, yeah. Mike: And that would help out. I think that you bring up a good point and it's one I never brought up when I was an admin, but not everything on the AppExchange is free. There's a cost to it, but the cost would be ongoing as opposed to massive upfront that they would spend on you and it's a small monthly fee. And you also benefit from, then they get time to upgrade it. Whereas if you've built something, who knows if you're going to have time to upgrade it. Alistair Dinning: All of the above is true. The other thing with the AppExchange, which has blown my socks off in such a good way in some occasions, is that I found a product on the AppExchange that met 85%, 90% of my business requirements, presented it to the business, the business, "It would be nice if... I really needed to do X plus." And I've actually been able to go back to the AppExchange partner, have a conversation with them because some of these... These are not giant software houses that are difficult to talk to. Some of these are very small independent consulting shops or software development shops and they will take your feedback and they'll go, "Oh, that's a good idea. That's not on my product roadmap," or, "That is on my product roadmap. Let me accelerate it." Or, "Let me bring that into my roadmap and we will bring it to you as part of the product." And they will actually take that feedback if you ask. And I think the important thing to consider there is don't assume that what's in the app exchange is locked and finite and immutable, but it could be a discussion. And they will take that feedback because they want their product out there as much as anybody else does. Mike: Yeah. And if it's a feature you're requesting, who's to say it's not a feature that a lot more of their customers aren't requesting? I like that. One thing I wonder in your day-to-day, because you have a really cool title of senior solution architect, how much, when you sit down with an organization or you sit down with an admin and the people that use Salesforce, how much do you talk to them about the amount of change that's going on outside of just implementing Salesforce? Alistair Dinning: It can be some very extensive discussions because when I get pulled in to work with a customer, we're typically doing a technology overhaul or a migration from a legacy platform into Salesforce. So there's a lot of business process change that has to happen to make sure that Salesforce meets those requirements, but also make sure that the business users understand that Salesforce is going to support them and how Salesforce is going to support them. And these requirements will... The method of working can change quite drastically, even if the end goal is the same. The process of spending time and training people and understanding what motivating them before you actually even get into making any development change is really important. So I try and step out of the weeds of, I need a form that asks X, Y, Z and fields, but what are we trying to achieve with this form? What are we trying to achieve with this business process? Or maybe even what is the metric that the business users are being evaluated on or being comped on? Because if you understand how people are being evaluated or how people are being compensated, that will drive and you can build a platform that will support those behaviors that will drive adoption and that will bring people into your world or into your process. Mike: The second you talk money, that's when it becomes real for people, especially compensation. For every time I've rolled out a sales process, the salespeople want to know if X, when, Y, what's my pay? Because A, that's why we work, but also I want to make sure that I'm doing things right. And the reason I ask that is for the longest time as an admin, if I was pushing out new features, I felt I was doing my job. If I was constantly giving, and not constantly, not every day, but on a regular basis, if I was giving my users new features, I felt like I was doing my job. And it didn't really dawn on me until one of the organizations I was working at went through a massive leadership change. And here I am pushing out new features on opportunities for salespeople and stuff across the board, and everyone else is kind of grappling with also massive organization changes. And I remember I sat back for at least two months and just didn't push anything new because if I could control that environment and give my users a sense of normalcy when the rest of the organization is changing, then I wasn't contributing to their stress. Alistair Dinning: That's a very reasonable way of moving things forward and allowing the team to stay on an even keel. Mike: Well, I mean, part of, I think, understanding and thinking through is this feature right, is, is this feature right right now? Or would it be more right later given where everything's at? The last thing, the cliche of that is you don't want to push something new the last two weeks of a quarter because you're radically changing a possible sales process or something that could affect books and numbers. So obviously that seems to make sense, but the same also holds true for other parts of the year when other parts of the organization are maybe going through a different change. Alistair Dinning: And this taps onto another point, which has just occurred to me. So yes, absolutely. When we are making changes in the Salesforce platform, we've got to be organizationally aware to, for example, to your point, where salespeople are in their sales cycle. Are we at the end of the month? Are we at the end of the quarter? Is this the end of the fiscal? I mean, everything should be end of fiscal. Big sales organizations that I've worked with or worked at, you don't make any changes in the last month of the fiscal because the sales people are always focused on a single task and that is getting to their number. And we're talking about salespeople, but it could be any other organizational goal and team where you need stability...
/episode/index/show/buttonclickadmin2/id/43098803
info_outline
September Monthly Retro: What Changed, What Matters, and What Admins Should Do Next
09/24/2026
September Monthly Retro: What Changed, What Matters, and What Admins Should Do Next
Today on the Salesforce Admins Podcast, we talk to Joshua Birk, Senior Director of Admin Evangelism, and Kate Lessard, Lead Admin Evangelist at Salesforce. Join us as we chat about what caught our attention at Dreamforce, what surprised us, and what’s worth spending time on. You should for the full episode, but here are a few takeaways from our conversation with Joshua Birk and Kate Lessard. Build fast and accurately with Builder Central Probably the most exciting announcement from the keynote is Builder Central. It’s a low and no-code workspace to enable admins to build fast and accurately, without compromising on security. From React sites to flows to agents, you can get an idea off the ground with plain language prompts. But just because you move fast doesn’t mean you need to break things, thanks to automated testing, safety checks, and built-in controls. “We can take what we as admins already know about data models and our org structure and really, truly define what we're building,” Kate says. You can upload requirements documents and information about your organization’s business processes to make sure everything that you build works from the get-go. Create consistently amazing Salesforce experiences The other thing that was touched on in the keynote was Headless 360 and the Headless Experience Layer. You can bring Salesforce to Slack, Claude, and anywhere else your users need to interact with your data. If you’re feeling overwhelmed by how many different ways there are for users to interact with your Salesforce data, know that you’re not alone. But at the end of the day, these are experiences that you’re designing for your users to make their lives easier where they’re already working. Admins need to focus on governance and security Finally, the biggest takeaway from Dreamforce this year is that governance and trust are more important than ever. Hackers use AI too, and the threat landscape is constantly evolving. Now more than ever, the role of the Salesforce Admin has shifted into governance. That means data cleanup and strict permissions controls to make sure that your agents are working as intended. And that also means getting a better handle on how your data is moving across platforms and who might have access to it. Trust is a core principle at Salesforce, and so we’re rolling out new tools like Security Center Essentials and the Transaction Security Policy Accelerator to help you take control of what’s going on in your org. There’s so much more great stuff in our September Monthly Retro recap of Dreamforce, so make sure to listen to the full episode. And don’t forget to subscribe to the Salesforce Admins Podcast to catch us in your feed every Thursday. Podcast swag Learn more Salesforce Admins Blog Post: Salesforce 360 Blog Post: Salesforce Platform Guide: Salesforce 360 Blog Post: Admin Trailblazers Group Social Full show transcript Mike Gerholdt: Before we jump into today's conversation, I want to give you a quick heads up about what's coming on the Salesforce Admins Podcast. Starting in October, we're moving to two episodes a month with a little bonus episode to kick things off. So October 1st, we're talking about how do I decide if a new Salesforce feature belongs in my org? Because Salesforce just released it and we should turn it on, are two very different things. Then on October 15th, Jennifer Lee joins me for a special video and audio episode, Winter '27, What Admins Should Check Before Their Org Updates. We'll help you figure out what deserves your attention, what you should test, and what you need to be ready for before the release hits your org. And then on October 29th, we're asking the question, what does an admin certification prove in the Agentforce era? We'll look at what certification tells employers and admins today and where hands-on experience and judgment fit into that picture. So after October, you can expect two episodes a month focused on helping you understand what matters, why it matters to your work, and what you can actually do with it when you get back to your organization. And that brings us to today's episode. So I'm joined by Kate Lessard and Josh Birk for a post Dreamforce conversation about what caught our attention, what surprised us, and more importantly, what's actually worth an admin spending time on. We're going to talk about Builder Central and what it could change about how admins build, new ways Salesforce can show up in tools like Slack and Claude, and why that data permissions and security in your org are even more important. We'll also get into Security Center Essentials, transaction security policy accelerators, Agentforce vibes, and some of the new tools that can help admins understand and work with their org faster. But there's a bigger thread running through all of it. AI can help you build, investigate, and move faster, but it doesn't replace knowing your business or knowing when something is actually right for your org. Josh calls it trust but verify. And I think that's a pretty good way to head into this conversation. So let's get Kate and Josh on the podcast. So Josh and Kate, welcome to the podcast. Joshua Birk: Thanks for having us, Mike. Kate Lessard: Thanks. Mike Gerholdt: We all have a little post Dreamforce voice in our step because it's been a long few days, but I wanted to get something together with all of us really fresh right after we landed. Some of us landed sooner rather than later leaving San Francisco and talk about what we saw, what really stuck out to us, maybe some of the demos we got to work on and things that surprised us. So Kate, you are in the keynote and keynotes always get top billing, so we're going to start with you. Kate Lessard: Woo, I love it. Mike Gerholdt: Yeah. Talk to me about some of the stuff that you guys showed in the keynote for people that missed it and what you're excited for. Kate Lessard: Yeah, the keynote this year was really fun to work on the demos because there's just some really exciting new technology out there for admins to leverage. I think that there are just a lot of exciting new features that are specifically for admins that are really designed to improve our building experience. And if you are able to catch any of the sneak peaks or any roadmap sessions, you know that there are even more coming. But if you did join us for the keynote or if you plan to go watch it later, a really great example is Builder Central. And this is an amazing AI builder that is specifically designed for low-code and no-code builders. So not only can we use it to build fast and accurately, but we can also use it to edit directly in the Explorer, which is I think my favorite feature. And we can really visualize everything that we build and that spans from things like react sites to flows to agents, and then even all the way over to data model and permissions, which is super cool as an admin. And I want to say that I think that the most important thing to note though as an admin is that using tools like this, my expertise and my strong foundational skills that I've developed are still really necessary. With Builder Central, we have the ability to add things like requirements, documents, or information about the different business processes from our organization so that we can take what we as admins already know about data model and our org structure and really truly define what we're building. And so I think to me, the message and the excitement here is that as admins, we still need to understand the business and the technology to be successful and that doesn't go away, but using a fantastic product like Builder Central, we're more important than ever and we get to create these exceptional experiences and that really has lit me up this Dreamforce. Mike Gerholdt: I'm going to pause you there because I know you've got more to talk about. Kate Lessard: Oh, yeah. Mike Gerholdt: I'm so glad you brought up Builder Central first. I was floored. So I had seen, obviously we work on stuff prior to seeing it at Dreamforce and I'd seen demos and I think maybe it just kind of skipped off the surface for me as, "Oh, it's another AI thing and it can do this." And it kind of looked like a little bit of setup with Agentforce or Agentforce for setup. And I gave it some credibility, but I didn't really understand what I was looking at. And then I got on the show floor and this was Thursday and Daivat, who works for Tiaan, who was in the keynote, pulled me aside and said, "Mike, you got to come to our demo booth." And I'm like, "Okay." And he showed me a customer that came up and was really into Star Trek and this is why I'm like, "Okay," took a screenshot of a Star Trek set, kind of like those glittery panels that 70s, 60s tech ad. And he said, I think I want to make a dashboard for my executives because they're really into Star Trek. And they gave Builder Central that screenshot and the data it should pull and it created a dashboard, I kid you not, that looked just like Gene Roddenberry had created it for the 1960s Star Trek episodes. Kate Lessard: Oh, very cool. I love to hear stuff like that. Mike Gerholdt: I was like, "Seriously?" Joshua Birk: Right. Mike Gerholdt: Now I have no idea. This is where my limited information comes in because Josh, it's a React site or it's a React page or I don't know what to do with it after that, but I was just like, "Oh, I could make my whole instance look awesome." Joshua Birk: Yeah. And well, we're moving towards this realm of you can use Lightning, you can use React, and you have a lot of flexibility in the technology that's driving this. And that's, I think lending to that your dashboards don't have to look like what you think your classic dashboards are like. And it goes back to not that there's anything wrong with the Salesforce UI, but it's like, as was said during the main keynote, was the UI really ever our main driver? Was that what made us distinct? And I don't think that's the answer. I think the answer is the platform, it's the APIs, it's the features. And if you can update your UI to be like Star Trek, which is freaking awesome, all the better for everybody. Mike Gerholdt: Yeah. I think that's a demo video somebody should do. Kate Lessard: Yeah. It really takes that concept of storytelling with data to a whole new level and making it really impactful for the people that are digesting that information. Mike Gerholdt: I mean, if that's what your company wants, then that's what people... If you want people to look at dashboards or whatever, then put it into something they're at. So, Kate, I share with you the same concern. Am I right to worry that it's almost like when we first get the calculator in algebra class and everybody just uses the calculator and assumes it's right for admins in terms of Builder Central? Because my worry is I see that and I'm like, "Okay, but wait a minute, how do I know if that number's right?" And I know how to pull that dashboard. Should we do something else besides build that Sparkle dashboard in Builder Central? Kate Lessard: Yeah. And I think the really important thing to know as you start working with Builder Central is you have to have a strong admin foundation. Everything that you know is important because you are sharing that information about your data model and what you need in that either prompt area, that box where you're entering in your prompt, or through your requirements' information where you add in a file. And so I think that it's actually incredibly important to have your strong admin foundation to be able to create these exceptional experiences. Joshua Birk: Yeah. And say it with me everybody, always do it in your sandbox first, press but verify. And these are the same skills and the same habits that we've been forming all along is even if you were working with a developer team, you wouldn't necessarily assume everything that was coming out was 100% accurate. And the same's going to be true with Builder Central and these other tools. Mike Gerholdt: Continuing on, Kate, after that Builder Central, I think that was the first chapter in the keynote, right? Kate Lessard: Yeah, that was our chapter one, building trusted AI. Mike Gerholdt: What did we talk about for chapter two? Kate Lessard: Chapter two was all about delivering trusted AI everywhere. So I think that admins go to Dreamforce. I know that when I was an admin, I would go to Dreamforce and I would feel a little bit of overwhelm because there's just so much to take in. And I think that maybe that was something that I was hearing from admins this year that they're feeling a little bit overwhelmed because everything that they do is actually now expanding to all of these different interfaces as well. So we saw examples of Salesforce and Slack, we saw examples of Salesforce and Claude, and this is going to continue across other interfaces. So I think that the big takeaway here and what I'm continuing to watch is how admins can deliver to new and more interfaces without changing that true foundational work that we've done in Salesforce. And that's super exciting. And that was really what our second chapter in the keynote was about. I think the example we used was a really good one. In the keynote, we showed exposing and running a flow directly in Claude. And that example was super simple. It was just a really easy auto launch flow to escalate a case. But that business implication is huge because as admins, I feel like one of our superpowers that moving forward is really meeting users where they are working and providing that same exceptional experience, whether they're in lightning or in a different interface. So I think that that is really cool and something I'm really excited to see how it progresses because we're only going to more interfaces. Mike Gerholdt: Yeah, I agree. Was that the chapter where, maybe I'm confusing my keynotes, where you could preview what the Salesforce, I'll call it a card, would look like in Claude or Slack or ChatGPT? Kate Lessard: Yeah, we did show HXL, the headless experience layer. We did show an HXL component in Slack as well. And HXL is really a way to be able to take that component, that experience, and exactly display it in Slack, display it in Claude. So that's really cool. And admins can get hands on with the HXL playground if they want to try that out. It's been one of my favorite places to spend time lately. Mike Gerholdt: I mean, to me, and I said in the architect and developer keynotes too, it only served to almost refocus me more as an admin to think of, I have the Salesforce core as my foundation and everybody's going to be coming to use it. I have to make sure that my data and my security are the utmost because once somebody uses that headless layer or AI force to ask Salesforce a question in Claude, if my data's not right, then their answers aren't right. And I was thinking of that as that's the home base for me. And it almost just reaffirmed it that we weren't interface engineers because now the interface is everywhere. We're really data and security. Joshua Birk: Yeah. And I mean, this is the promise of headless, is that it's the client that you need, not necessarily the client that we are going to enforce on you. And I think there's a lot of interesting variations of using Claude and using Slackbot and using Coworker and things like that, but you're not wrong. It's like the core responsibilities are still going to be the same and that's what's going to drive, and context is king and you can't have good contacts without good data and you can't have good data without good security. So a lot of the foundations, they're just still there and they're going to help you through whatever agentic route that you're going to be going through. But as Kate was saying, the importance of those core responsibilities is never going to go away. Mike Gerholdt: You brought up Coworker. Josh, did you make it to any coworker sessions? Joshua Birk: I did not, but I have been poking around with Coworker and I think Coworker's a really interesting feature. What's interesting to me is that we are now seeing these tools that are very similar but different. We have Coworker, we have employee agents, we have Slackbot, and they all kind of overlap each other in various ways. Coworker, I think the big strength at Coworker is that it's basically you turn it on, you connect it to your sources and then you let it go. Whereas an employee agent is something that you are involved in highly customizing. And then Slackbot is kind of its own tool and obviously it's something that's very important if you're actually using Slack. And I think the nice thing is we don't have to put all our eggs in one basket. You can utilize the client, the agent, the AI that is best for you, whether that's Coworker or Claude or Claudeforce, it's whatever's going to be best suited and they all have their little distinctions for using it. I'm a big Coworker fan because it puts a lot of feature and functionality and information right at your fingertips, but it doesn't have the customization that say an employee agent does. Mike Gerholdt: Right. Kate Lessard: Yeah. And I want to hop in and specify, we're talking Agentforce Coworker here. And I think the really cool thing for admins to know here is... that you can turn this on in under five minutes and have it set up and ready to go and supporting your users and providing them with the information they need, which is, I mean, talk about just a really quick win for us to be able to deliver these awesome AI experiences to our users. Mike Gerholdt: So would you do that first, Kate, instead of building out an employee specific agent? Kate Lessard: I think it depends on the situation and what you need the agent to do. I think that Agentforce Coworker is going to allow users to help themselves quite a bit, and it's going to be a really straightforward, quick win that you can get them moving in the right direction. If you need your employee agent to do kind of other things and have a lot of different connected data sources, I think that maybe you would go in that direction, but I think it always comes down to that what is the use case? Joshua Birk: Yeah. And to throw a little bit in favor of an Agentforce employee agent is you can enforce a certain level of determinism using flow, right? So you have a lot of control over what that employee agent can do, whereas Coworker is just sort of out of the box. Kate Lessard: Absolutely. Mike Gerholdt: I will say this. So the architect keynote finally, because there are things that Mike can read five and six times and it still doesn't make sense to him, the architect keynote finally described to me the difference between probabilistic and deterministic. I think I'm saying both those right. Kate Lessard: That's a mouthful. Yeah. Mike Gerholdt: It is. I know. It feels like when you go... But that word- Kate Lessard: Oh, look what we did to you. Oh, no. Joshua Birk: Yeah, you tricked your brain into you didn't know how to pronounce it. Mike Gerholdt: There's only so many times you can say that word before the fuse breaks and I already said it. I already broke the fuse. But that is the AI saying, "Oh, well to win the deal, you need 18%." And then deterministic is the AI using its reasoning, but also being grounded in saying, "Well, 18% would win the deal, but our max is 15%." And I was like, "Oh." Joshua Birk: That's a good way of putting it. Mike Gerholdt: Maybe it was a developer keynote. Again, they kind of all smeared together for me. But I remember seeing that slide and I thought, "Now it makes sense to me." I had a light bulb moment. Joshua Birk: Nice. Mike Gerholdt: Just didn't appear as normal. And then of course I've already blown the fuse on terministic and probabilistic times I can say that. It's like exclamation points. Do you ever have an...
/episode/index/show/buttonclickadmin2/id/43007323
info_outline
What Does the Salesforce Admin Job Market Look Like Right Now?
09/10/2026
What Does the Salesforce Admin Job Market Look Like Right Now?
Today on the Salesforce Admins Podcast, we talk to Maria Alvarez-Zarrilli, Founder and Principal Consultant for Throughline HR LLC, and William Walsh, Salesforce and AI Recruitment Lead at Harvey Nash. Join us as we chat about what Salesforce employers are looking for in new hires and how to get your career started. You should for the full episode, but here are a few takeaways from our conversation with Maria Alvarez-Zarrilli and William Walsh. How the Salesforce Admin job market has changed Over the past few years, the role of the admin has changed a lot. It’s no longer about how many certifications you have or how many users you can manage. While those skills are still important, being a great Salesforce Admin is much more about how you put that knowledge into action to support core business processes and generate value for your organization. So how do you stand out from the crowd? That’s what I wanted to talk about with Maria Alvarez-Zarrilli and William Walsh. As recruiters, they see the Salesforce Admin job market from both sides: what it’s like when you’re looking for a role and what employers are asking for when they hire. Increasingly, it’s not just about what you can do in Salesforce, but how you can connect it to the business and make an impact. Talk about business impact The number one thing that Maria looks for in a Salesforce Admin is requirements literacy. “It’s not just being able to take a set of orders and execute it, but really be able to fine-tune that,” she says. “Push back, make recommendations, be in front of what's happening and have that longer future vision, knowing that so many of these runways are going to be short with AI.” Showing you have that skill is tricky, but it starts with how you talk about your experience. Are you describing features, or are you talking about the benefits? Don’t just list outcomes; talk about impact. You need to show that you can think bigger than what you’re building and understand how it fits with larger organizational goals. The power of showing up William urges job seekers to spend real, face-to-face time in the Salesforce community. At this point, everybody has shiny, AI-polished LinkedIn profiles and resumes. But meeting someone and making a connection with them can be so much more powerful than sitting in front of your computer mass-applying to every job opening you come across. “This ecosystem is super welcoming, and everybody wants to see everybody succeed,” William says. “So go to some user groups, some local events, and you'll see how quickly people around you start to root for you and start to put your resume in front of the people they know.” Maria and William have a ton of great tips for interviews and navigating the Salesforce Admin job market, so make sure to listen to the full episode. And while you’re at it, subscribe to the Salesforce Admins Podcast to catch us every Thursday. Podcast swag Learn more Salesforce Admins Podcast Episode: Salesforce Admins Podcast Episode: Admin Trailblazers Group Social Full show transcript Mike: The Salesforce admin job market looks a lot different than it did a few years ago. So, what are employers actually looking for right now? And how do you make sure your resume, experience, and interview skills line up with that? Well, today on the Salesforce Admins Podcast, I'm talking with Maria Alvarez-Zarrilli, founder of Throughline HR, and William Walsh, who leads Salesforce and AI recruitment at Harvey Nash. We get into why certifications alone aren't enough, how industry experience can help you stand out, and why curiosity and communication matter so much once you get into the interview. So, whether you're looking for your first admin job or your next admin, we're also going to tell you about where it's worth spending your time. With that, let's get Maria and William on the podcast. So, Maria and William, welcome to the podcast. Maria Alvarez-Zarrilli: Thank you so much for having. William Walsh: Thank you. Thank you for having us. Mike: This is going to be exciting. I have not had two people on in the job space ever, so I go from zero to two, which is smart. But Maria, let's start with you. Tell us a little bit about what you do in the job recruiting, job placement space. Maria Alvarez-Zarrilli: Absolutely. Well, thanks so much for having us. My name is Maria Alvarez-Zarrilli. I am the founder and CEO and principal consultant for Throughline HR LLC. And very much in the vein of what we're talking about, this is my new solopreneurship venture launched in the last two months in response to everything that's happening in the job market. I've done every side of the recruiting, staffing, hired and being hired from doing Salesforce recruiting at Robert Half, supporting them, Protiviti, staff augmentation to going in-house with Vicasso, formerly Internet Creations, helping build both professional services and their ISV side. I worked at Salesforce directly in workforce development in Salesforce Talent Alliance under alliances and channels and helped get employer commitments to continuing to grow the ecosystem, investing in that top of the funnel Salesforce talent, building programs to help bring people in, admins, BAs, developers. And now I am working all different roles, but still very much in touch with the Salesforce ecosystem, still working with so many of the amazing partners that I've built relationships with over the years, supporting outsource hiring, staffing, job coaching, and career guidance. Mike: Wow. So, a few things. Maria Alvarez-Zarrilli: Just a couple things. Mike: William, how about yourself? William Walsh: Yeah, I don't know if I'm as impressive as Maria, but I'll try to keep up as we go along here. But I lead our Salesforce and AI recruitment practice at Harvey Nash. So, here, what I basically do is work with companies across not only the Salesforce ecosystem, but multiple CRMs as we continue to grow. And that ranges to help them build out their teams of admins, business analysts, all the way up to architects, AI specialists, data focused people and leadership roles as well. The neat thing about what I do is I work really closely with both sides of the market. So, I'm talking to not only hiring managers for what they need for their teams, but also speaking with Salesforce professionals every day on what they're seeing in the market and where they want to take their careers next. So, I think I get a pretty unique view of the market from both the employer and candidate side. And a big part of my job is understanding obviously where those two things line up. So, hope we can give everybody some good information today as to what employers are really looking for and how to stand out in this ever-changing job market. Mike: Yeah, I think that's why I was so excited. Shout out to Umer who was on the podcast a long time before he even joined Salesforce that connected all of us. But I love that both of you had the same but different lenses into the job market. And William, you set me up perfectly. So, I mean that's the first question on my list, which is when you look at the Salesforce job market right now, specifically for the admin role, what are you seeing? William Walsh: Yeah, I think it's definitely a more competitive market than it was a few years ago. I think there's a lot of really good admins out there. So, just being that Salesforce admin and having a few certifications on your resume isn't really necessarily enough anymore. What I'm seeing clients respond to is admins who really understand businesses behind the platform, whether it's sales, service, operations, data, which I'm sure we'll talk about a little bit more, but really admins who can show they've solved business problems in Salesforce are the ones that are standing out currently. People that can, again, not just be that general admin, but can differentiate themselves with whether it's an AI tool or a specific industry, that's kind of been the biggest thing that I've seen change. It's become a much broader role. Again, a company would just look for someone who was able to manage users, build reports, handle workflows, keep the org up and running. Now they really want someone who can be a real business partner for them, understand the data and automation integrations. So, I don't think the admin role has necessarily become much of a different role, but it's definitely, you want to add some more skill sets to just your generalist admin at this point. Maria Alvarez-Zarrilli: Absolutely agree. I think we're seeing a really important evolution and one that really follows a lot of what we've seen before in ERP and MCSC before where you're getting a role that used to be about just configuration, build this, set this up. You had a lot of single seat admins that assist admin, a lot of people didn't even call themselves Salesforce admins when I first started recruiting in this space, which is what made it so difficult. And now there's this concentrated branding and it's evolving into this governance and you really need to be able to stand out in ways that say, to William's point, this is an outcome I can provide, not here's the number of seats I can manage, but this is what I'm able to do in terms of business impact. I understand how this is going to affect what the top line is for the company, how this evolves into the mission. People need to understand the actual companies, not just the platform itself. Mike: Those are really good points, I think. And that's one thing to jump off of too is so broader, I heard partnering with the organization, not just managing. Over the last few years then, what kind of roles or skills have changed or grew in terms of what employers are looking for in Salesforce admins? Maria, I'll start with you. Maria Alvarez-Zarrilli: Absolutely. One of the things I've seen the most is really that requirements literacy, not just being able to take a set of orders and execute it, but really be able to fine tune that, push back, make recommendations, be in front of what's happening and have that longer future vision knowing that so many of these runways are going to be short with AI. Things are going to continue to change at such an insane pace that's not going to slow down. It's not, well, after this week, after this cycle, after this next set of release notes, things are going to calm down. They're just not. And that resiliency means that when an admin has a set of requirements, they need to be able to show judgment and wisdom, not just knowledge holding. Mike: William, you mentioned in yours that there was a certain set of things you kind of look for, things that are changing. Could you expand on that? William Walsh: Yeah, absolutely. I mean, we all know AI has been the big point as of late over the last few years, and I think data is kind of the big one, right? You can have any AI tool in the world. If your data isn't clean, it's not going to work correctly for your business, right? And so, I think data's a big one, automation's a big one. And as we see AI show up more and more, you're seeing a lot more demand for admin to have the experience with your specific industry clouds as well, your specific Salesforce products. And I think that people would honestly rather hire admin to understand, again, how to use Salesforce to improve business process rather than just someone who has that long list of certifications. I think when people first get into Salesforce early on, at least back in the day, it was, "Hey, get as many search as possible." And search are great. They get you in the door, but the real world experience is kind of what gets you over the finish line. And I think that's super important for people to understand. Mike: So, we've danced a little bit on industry and William, you brought it up. I think Maria, your answers have alluded to it. If I'm a Salesforce admin or looking to become a Salesforce admin, and I have a lot of a certain industry perspective, let's say Finserv or banking or automotive, I'm picking the big categories, should I really lean into that or should I just look for an admin role in any industry because I know Salesforce administration? William Walsh: Yeah, I would say either or, right? I think it totally depends on if you surely have a true love for that specific industry and working in that industry, you can definitely stick with it, but you just have to, again, not just be a generalist admin. I think within that industry, then you have to start diving a bit deeper into, again, if it's Finserv, say specifically Revenue Cloud and more that you can do within Revenue Cloud and CPQ. And again, learning more AI integration tools that'll help your specific business within that industry. Again, it's like I said, not just being that generalist admin I think is the main part, but I also find that sometimes you can get yourself into a spot where I feel too niche, right? And when I'm looking for a role, I can only go for roles in this specific industry because that's where my experience is. And so, I can see where people have those pain points. I think, again, if that's what you would really enjoy to do and that's your passion, stick with it and just broaden yourself within that industry. Otherwise, it's definitely, I always find being at a consultancy or being at a partner is always good because you get to have your hands on a few different platforms at once or get to be in a few different engagements to where you can really work on a Sales Cloud environment here, but then be in a Service Cloud org over here. And so, you get your hands on multiple different things and continue to grow your skill sets, not only in one specific industry, but all throughout all the Salesforce clouds. Mike: Maria, I'd love your thoughts. Should I lean into my industry first or should I lean into my admin skills and apply across the board? Maria Alvarez-Zarrilli: It's a very tricky question because ideally it's one of those, well, it depends, the lawyer answer. On the surface level, I would say yes, lead into the industry because of how that supports the differentiator of understanding the business outcomes. If you are coming from banking, if you are coming from healthcare, if you are coming from education and re-skilling into Salesforce, you're going to be able to speak more intelligently, especially at some of these, I'm going to use this phrase lightly now, entry level roles because you don't have entry level understanding of what the company is trying to do, what kind of outcomes they're looking to drive. And that's going to really support what I said about that requirements, scrutiny, the wisdom, the choices that you're making, and that's going to be an important differentiator. However, in today's job market, I would not tell somebody to limit themselves to only applying to jobs inside of their industry because there is a transferability, there is a lot of change happening inside of all of these industries, and people at the end of the day need to pay their bills. And sometimes, there just may not be enough opportunities in a given industry that makes sense for them when they're looking at jobs that are either available for remote, that are in their geographical area, if they're looking at companies that are pushing RTO, et cetera. So, if somebody really had a passion to what William and I believe you alluded to earlier about an industry that maybe they don't have deep experience in or maybe they don't have a lot of career experience at all, finding ways to stand out and deepen that industry knowledge so that you can stand out, I think is just as important as having that deep industry experience and figuring it out. Mike: Again, you set me up perfect for what I was thinking because I was kind of hovering around this question, but let's jump into this part of it. For each of you, when a candidate lands on your desk, what is it that makes them stand out versus others? William Walsh: Yeah, so I can start. I mean, like I said, I think for me, certifications matter. It shows commitment, it shows employers that they've got some confidence in your technical foundation, that kind of stuff. But what's really important to me is when I sit down, not only look at a resume, but when I speak to someone, can they walk me through three really impactful, at least three really impactful kind of projects that they've delivered? And nine times out of 10, a client is going to want to talk to someone who can walk them through really impactful projects they've been able to deliver rather than someone who's just got a list of certifications on their resume. So, I think that's super important. Another thing is having a bit of technical ability as well. Again, having that crossover, differentiating yourself from just your generalist admin, someone that can. Again, when I say technical sales, I do not mean coding Apex, but more so building and configuring and being able to do a lot of work with workflows nowadays. And again, having some AI focused tools that you've worked with in your current role. Most clients now are using AI one way or another, and when they're hiring an admin, again, they want that person. A lot of times they are taking on the headache of trying to integrate that tool correctly, and it's probably not their role. And so, they want to have someone that they can bring in right away and understand what exactly is going to work for their business and how they can best get their platform to where they need it to get to. So, like I said, I do look for certifications, they're great, but at the same time, it's really about real life impactful projects you've been able to deliver on and what your role was in those projects. If you're able to get a bit more technical and tell me you did some of the configuring yourself, that goes a long way when you put it in front of a client rather than, again, I was just kind of creating dashboards and all the other generalist admin stuff that we would usually look at five, six years ago. Mike: Yeah. Maria, I'd love your perspective on what makes a candidate stand out to you. Maria Alvarez-Zarrilli: Yeah, I think there's a handful of things. One, just being completely candid, that they look like a real candidate. The fake candidate's a real thing now, that they have verifiable information that they are active in whether it's LinkedIn, the Trailblazer community. I'm seeing posts that look like they're written by a real person. I've seen a resume that looks like it's written by a real person, just really to start at the surface level. And that can be really tricky because I have seen profiles, LinkedIn profiles, resumes, emails, communication, LinkedIn posts that because of trying to demonstrate this very, I think, professional demeanor and best practices, sometimes it can come across so boilerplate. My spidey sense tingles for a second and I catch myself going, "Is this person real?" And that is a real risk that people run now in polishing their information off. So, I'm just going to start at that surface level. Once we're actually interacting with a candidate and we verify this is a real person, not a bot, what really looks is that what's driving a person's? Where is the learning resiliency? Where is the resiliency within the stories that they are telling, not just the polished, "I was able to increase this by this percent and that percent." That's wonderful. Having those numbers is great. That is now the bare minimum. When somebody can say, "But," adding to the star method, that an extra R, that reflection, "But now with this new technology, I would do it differently. But now knowing how our customer base changed six months later, I would do this. But now knowing that more and more companies are going to be absorbing other companies, I would approach this slightly differently." Right? That...
/episode/index/show/buttonclickadmin2/id/42842975
info_outline
Security Center Essentials: What Admins Need to Know Now
09/03/2026
Security Center Essentials: What Admins Need to Know Now
Today on the Salesforce Admins Podcast, we talk to Sabrina Simeroth, Product Manager on the Salesforce Security Product Team. Join us as we chat about the new Security Center Essentials feature and how to work security reviews into the rhythm of your organization. You should for the full episode, but here are a few takeaways from our conversation with Sabrina Simeroth. What is Security Center Essentials? The last time we had Sabrina on the pod, we were talking about Health Check scores. However, as she explains, that number is meant to be an assessment of your organization’s security at a single point in time. But what about continuous monitoring? That’s where Security Center Essentials comes in. “With Essentials, we’re trying to give a broader and more ongoing visibility,” Sabrina explains, with a focused set of security metrics you can monitor over time. It makes it easy to see things like what managed packages are supported, which third-party platforms have access to your data, and who in your organization made changes. In other words, Security Center Essentials gives you a map for how your org is structured, making it easier to spot potential problems and make sure your security and governance are aligned with your business goals. Two questions to ask for security reviews So how do you get started with Security Center Essentials? For Sabrina, it’s all about context. Once you’ve run Health Check and dialed in your security settings and policies, you want to use the metrics on Security Center Essentials to get context for how things work in your organization. From there, Sabrina recommends asking yourself two key questions: What should be in my environment? Who owns this managed package? Who installed it? Who is using it? What has changed most recently? Were you expecting it? Who did it? How does it affect your business processes? Sabrina recommends establishing a monitoring cadence around regular business process milestones. If something is updated every Tuesday, check before and after to make sure everything happened as expected. As an admin, you have the best operational context to flag potential problems and bring them to your security and governance team. Why you shouldn’t chase a perfect Health Check score While your Health Check score is helpful for giving you a general understanding of how your security standards compare to industry best practices, Sabrina urges you not to chase a perfect score. “Your Health Check score should begin a security review, rather than ending a review,” she explains. It’s there to flag areas of your org that need a closer look, so you can make decisions about how much intentional risk your business needs to carry. The most dangerous security threats are the ones you don’t know about. It’s OK not to have a perfect Health Check score, as long as you know why you’re doing it. Make sure to listen to my full conversation with Sabrina about how to use Security Center Essentials and Health Check. And don’t forget to subscribe to the Salesforce Admins Podcast so you never miss an episode. Podcast swag Learn more Salesforce Help Docs: Salesforce Admins Podcast Episode: Kate Clicks Through It: Admin Trailblazers Group Social Full show transcript Mike: Security is one of those things where it's really easy to look at a score and think, "Great. I'm done." But your Salesforce org doesn't sit still and neither does your security posture. Today I'm talking with Sabrina Simeroth from the Salesforce Security product team about Security Center Essentials and how admins can use it to understand what's connected to their org, what's changed, and what deserves a closer look. We talk about why getting a perfect Health Check score isn't necessarily the goal and how to work security reviews into the rhythms of your organization. So if you've ever opened up a security dashboard and wondered, "Okay, what am I actually supposed to pay attention to?" This episode is for you. Let's get Sabrina on the podcast. So Sabrina, welcome to the podcast. Sabrina Simeroth: Thank you. Thank you so much for having me back. Mike: Well, it's worth talking about because security is always top of mind for Salesforce admins. And the last time I had you and Laura on, we were talking about Security Center Essentials. And I think if memory serves me right, people now have that available to them and admins can start getting in touch with it, right? Sabrina Simeroth: Yeah. Absolutely. So that has been launched and it is fully rolled out. They should be able to see that in production orgs and some sandbox orgs as well. Mike: Sweet. So you're integral part of security at Salesforce and you do a lot. Refresh my memory, what's your domain and what do you handle at Salesforce? Sabrina Simeroth: Yeah, absolutely. So I sit on the product management team. I support our security center product and that also incorporates the Essentials product that we just launched and some of our other free tools like Health Check in setup. And then I actually work really closely with a few other PMs that support other features of the premium products like our agentic features and work really closely with the Shield team as well. Mike: Shield. Sabrina Simeroth: Yes. Mike: Yes. Sabrina Simeroth: All security, all the time. Mike: Our secret MCU product. So let's talk about Security Center Essentials and actually Health Check. I'd love to know, and probably admins too, we love when we get these features, but what exactly were you trying to solve with Health Check? Sabrina Simeroth: Yeah. So Health Check is a really valuable ... I would call it a point in time assessment of some of the critical settings that we find in setup. These are your security configurations. Oftentimes if you've been to any events, you hear them called configurables. So these are settings like your password policies, your session settings, some of those toggles that you can turn on and off. But with the Essentials, we're trying to give a broader and more ongoing visibility. So it's not just a point in time, this is something that extends that capability. Health Check is still really valuable and it is a collection of these configurations that are set against a baseline or a set of standards so that you can see where your posture is at at any given time. But we really wanted to extend that and allow admins the ability to see how changes in their system, how changes in their configuration occur over time, as well as broaden the view of what they're actually looking at. So not just those toggles. Mike: I always liked Health Check was like right now, here's where you're at with links to open things. So that makes sense. It's making the dashboard a little bit bigger. I think for a Salesforce admin who just opens Security Center Essentials for the first time and they have a whole bunch of different metrics looking back at them, where should they focus? I think of a car dashboard. Well, if I start my car and the fuel light comes on, probably the most important thing to pay attention to. But as an admin, depending on the level of security awareness that I have, I may not know what number is the most important number. So help me walk through those different metrics that they're seeing. Sabrina Simeroth: Yeah. You are so spot on. So I think there's a tendency to want to stack rank, which is the most important thing to look at. If I could put it very simply, so we started with a very narrow scope of, let's call it metrics. So we wanted to extend the capabilities of Health Check. We wanted to give a broader view and give admins access to what does the actual state of your org look like? What are the things that are connected to your org? What are the managed packages that are being supported? Where are your access points? Those types of things. These are all really critical things for admins to be aware of because it's basically how is your org structured? So I think that that's the key. It's not that you should focus on or stack rank immediately any one metric in Essentials. It's more around let's figure out what our baseline is and what is the actual standard for our environment. So I would resist saying one over the other. Obviously, I think the tendency is to lean towards let me look at the thing that has a score. Let me look at Health Check. I would actually say, ask yourself two questions as an admin. What looks unfamiliar to me? So look at the seven metrics. And I apologize in advance because come Dreamforce, we're extending that seven metrics to 14 metrics, but we're still keeping the scope very narrow. Mike: It's no like Salesforce to just double anything, right? Sabrina Simeroth: No. Not at all. But we're trying to bring the most critical things for you to pay attention to the forefront and just keep it narrow so that you have a really, really solid idea of what should be in my environment and then what has changed most recently. Those are the two things to be really looking at so that you can start asking yourself questions. Does this actually make sense? Should it be here? Is there an assigned owner? These are the types of questions. It's really about laying out a map for the admin to start getting the right context about how the org is configured and then start evaluating is this good or bad and does it align with the business needs? So that would be my advice using essentials. Mike: Yeah. No. It makes sense. And I think you pointed out that what's really nice is you're not just seeing today's configuration, you're seeing how things changed and that if you're a Salesforce admin, whether you're just getting started in a new org, you can watch that progression. Or if you're coming to a fresh org, if you just got hired, that was always, and I still think is top of mind for a lot of admins. "Hey, when I parachute into a new company, what do I do to look at an org that I'm inheriting?" And so I think let's apply security center essentials to that and say, "If I inherited an org tomorrow, how could I use that to see how things are changed or understand a little bit more about the org that I'm working in?" Sabrina Simeroth: Yeah. That's a great question. So if we look at the metrics that are included in Essentials, it's things like what types of packages do I have installed? What type of connected apps? So how is data interacting with third party packages? How is data interacting? And the great thing about these metrics is we're giving you visibility into who actually installed these packages? So is that normal? It's that type of context. First take inventory, see what's connected into your apps, see what IP ranges you have associated with your different profiles. What are your trusted IP ranges? Take a look at your security configurations through the Health Checkout. Are you using any baselines that were already set up? So if this is a new org did somebody already have a baseline, have they already done a security review? Check those things first and then start establishing your context. So the metrics do a really great job of showing you who may have been the owner of those, who may have installed or made specific changes at any given time. So use that as your starting point and start to do your own investigation, building context around which teams are using this? Who is the true owner at this point? Does this make sense? Is it still actively being used? That context is going to be really helpful when you start to get into the monitoring piece, which is when changes are made, then an admin can more easily flag like, that doesn't align with what I'm expecting. Does that make sense? Mike: Oh, absolutely. That whole connected apps and packages part is ... If you're working with people in a larger team or ... Boy, I got to tell you, I've done this accidentally where you set up a user and you forgot to deny them access to install packages. Sabrina Simeroth: Oh yeah. Just delete access. Mike: And I remember I had this power user. I found this whole app exchange and we can download apps. And my face just went white. Because I was like, "But you couldn't do that, right?" And they're like, "Oh no, I did totally." "Oh, well, you're not going to be able to after I finish my salad." Sabrina Simeroth: Yeah. And that's so true. It's very hard when things are scattered all over the place to maintain that. It is a very complex platform for a reason. It provides so much flexibility to the users to really align with business. The challenge then becomes like, okay, how do you make sense of that to make sure that you're doing the right things as it relates to security? And so that's the whole goal. It's let's bring some of those key elements so that you can quickly identify where those changes, those missteps, they always happen. They're not going to be able to be avoided. But how quickly can you evaluate and then shift and make changes to address any gaps or concerns or what we consider gaps in your posture? Mike: Right. Right. One thing that I loved about Health Check was it gave me a score and admins love score, got to get perfect score on everything. The idea of making it to a hundred on Health Check being perfect as a goal, is that really a goal or how should admins think about that number? Sabrina Simeroth: That is such a good question, and this is so common. So I was a part of the Own acquisition. I've been working with Salesforce security products for the past 10 years. And in that previous role, I actually helped customers implement their security programs and implement their security tooling. And we would get this all the time, customers just really wanting to reach 100. There is this- Mike: I want to be perfect. Come on Sabrina. Sabrina Simeroth: Strive for perfection. It's so common. And when it comes to risk scoring, the desire is always to reach perfection. Here's how I would look at it. A higher score is a very useful signal. A low score is a very useful signal, but 100, I would say, should not become like a trophy or the end goal without very valuable context. So context really matters. So Health Check compares settings with a standard baseline, but every organization can have very legitimate reasons for different settings or the need to actually carry some risk in their system in order to be able to operate the business. So not every setting makes sense for every customer. So the score should really begin a review rather than ending a review. It really needs to be treated more of ... We were talking about the car. It's more of a gauge. It's not like a report card that tells you you're good or bad. It is telling you where to look so that you can actually evaluate and get the right context to say, does it make sense for our business to actually secure this or remove this or lock this down, restrict this? Because there will be some legitimate reasons why you don't want to align with that. There will be impacts to the system or things that are restricted from users that need access to sensitive data in order to do their job. That is acceptable risk if it's well documented, if it's intentional, if it makes sense for the organization. So a hundred I would say is not the goal. You can always reset a baseline in-house check so that it makes sense so that you can reach that 100 state. But I would definitely use it more as a signal to review what's going on and to provide awareness of your configurations rather than the end goal. And don't ever think like I've reached a hundred, I'm perfect, I'm going home and I'm never looking at this again. A system is always changing, it's always evolving. And so a regular review is really critical. So that would be my advice there as it relates to a score. Mike: Yeah. Well, I got to ask, often admins will have governance. They'll hold monthly governance meetings or quarterly. You can refresh Security Center Essentials a lot. What is the pattern that you would suggest admins do a data refresh on that? And then part two of that, because I'll just make the question harder, how would they work that into a governance meeting? Sabrina Simeroth: Oh gosh. So now see, you're putting me in a corner because I always give a soft answer on this one, but let me try to be really practical because I want our customers to really have a clear idea of how to manage this. The cadence that we've set for in the background running these metrics is once a week. So use that as the baseline. Once a week gives you plenty of time to see actual changes in the environment, but that's not to say that you shouldn't do these manual refreshes so you can manually update these and do more targeted. What I would say is avoid just every hour, update, update, update. That's excessive. And if it doesn't align with your actual business cadences. So it's going to be different for every customer, but try to align it with known milestones or known practices. So these are things like your development life cycle. When are your planned releases? When do you traditionally install new packages? Are there large onboarding events? Do you have regularly scheduled security reviews? And this is why it's a fuzzy answer where it's like it's going to be different for every customer. But as an admin, if you know that you also have an internal regular cadence ... Maybe you're doing a security review at the first of the week every week, maybe then you do deployments on Thursday every week. I would actually align the update cadence to those known activities because then you have context. It's a starting point where you say, "This was an expected activity and here's the changes that I saw." I also saw changes outside of that activity. And so that's a really good point when you talk about bringing it into a governance meeting. When you are speaking with security folks, when you're speaking with compliance folks, it's incredible context to be able to say, "Hey, I was expecting this activity. I was not expecting anything on this date. Is there anything in your world that would indicate that this is actually an appropriate action that was taken? Should we investigate this further?" And that's a really clear starting point given the context of I'm an admin, I have a lot of the operational context of how we're operating our business and here's that context. And this from my perspective sits outside. It's a little bit anomalous to what we would expect in terms of our own personal cadences. So I can't tell you it should be every day, it should be every five hours. That's really challenging. But it should try to align with some known milestones, some known events that you have going on in the business. Mike: That makes sense. You don't want to refresh it every day if once a month you make your changes and you're getting the same number day after day like, okay, well obviously it's expected. Sabrina Simeroth: Right. And then you become numb to it a little bit. You're just like, yeah, okay. Mike: You do. And then a number of changes, you're like, wait a minute, should that have been up or down? And you forget. So I get that. Let's talk about Security Center as a whole, because Essentials is the starting point. And I think for a lot of the admin work that I've done, it sounds like it more than fills the bill. But Security Center, you've got multi-org, you've got advanced capabilities. At what point would an admin look at Security Center Essentials and say, "Not enough. We need more." Sabrina Simeroth: Yeah. Yeah. It's a great question. I think everybody leans towards it's when it's multi-org. I think that's the default. Everybody says, "Okay, well the premium products, that's for multi-org, that's for these massive organizations." I would avoid thinking that way. For me, it's more around, let's call it organizational or operational complexity, and this can mean many things. So if you are starting to have more frequent changes like adding users, your company is...
/episode/index/show/buttonclickadmin2/id/42720670
info_outline
What Does the Salesforce Platform App Builder Certification Prove Today?
08/27/2026
What Does the Salesforce Platform App Builder Certification Prove Today?
Today on the Salesforce Admins Podcast, we talk to Alexis Kingma, Senior Certification Developer at Salesforce. Join us as we chat about the newly updated Salesforce Certified Platform App Builder exam and the best way to prepare for certifications. You should for the full episode, but here are a few takeaways from our conversation with Alexis Kingma. The Salesforce Platform App Builder Certification gets a refresh The Salesforce Certified Platform App Builder exam has been updated, and the process is more complicated than you might think. This week, I’m talking to Alexis Kingma from the Salesforce Certification team to find out what’s changed, why it matters, and how to best prepare for an exam. Whenever Alexis and her team are doing a refresh for an exam, they start by interviewing a range of subject matter experts working in the real world. For the Salesforce Certified Platform App Builder exam, they’re trying to answer a simple question: “What is the industry saying is most important if somebody's looking to hire an app builder?” Alexis encourages you to think of a certification exam as a validation of your knowledge. In other words, it’s proof that you have the expertise to build cutting-edge apps and implement them in your organization. Shifting the focus to Flow and Agentforce So what’s changed? The focus is on automations with Flow and Agentforce. As Alexis explains, if you’re looking to hire an app builder, you’re looking for someone with a deep understanding of Flow. Do you know which flows are best for which situations? Can you troubleshoot them? Can you maintain and monitor them? They want to make sure that anyone who passes the certification exam has the Flow expertise they need to hit the ground running. The other change is including Agentforce as an automation tool for app building. While you don’t need to be a power user (there’s another certification for that), Alexis and her team want to make sure that you have it as an option in your toolkit. How to prepare for Salesforce certification exams According to Alexis, every Salesforce certification serves as a gauge for your practical, on-the-job skills. This means if you are currently building applications for your company, you are already ahead of the curve. To support the recent updates, her team has curated a specialized Trailhead trail that features interactive badges, allowing you to practice directly within a sandbox environment. Alexis also highly recommends taking a close look at the exam guide for any certification you’re going for. They’re written very intentionally, she explains, to give you a very specific idea of what level of understanding they’re asking for on each topic. Words like “create” or “configure” are asking for much more in-depth knowledge than “describe” or “understand.” Finally, if you’re attending Dreamforce, Alexis wants to remind you to schedule your free certification exam. Make sure to listen to the full episode for more about the Salesforce Platform App Builder certification exam. And don’t forget to subscribe to the Salesforce Admins Podcast to catch us every Thursday. Podcast swag Learn more Exam Page: Trailhead: Dreamforce: Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins Podcast, I'm talking with Alexis Kingma from the Salesforce certification team about the newly-refreshed Salesforce Certified Platform App Builder exam. We're going to get into exactly what changed, why Flow now has a bigger role on the exam, and where Agentforce fits into the app builder skillset. So whether the Platform App Builder is your next certification or you just want a better sense of where admin skills are headed, this episode is worth a listen. Now, before we get into it, be sure to subscribe and share it with any other admin who's thinking about their next certification. So with that, let's get Alexis on the podcast. So, Alexis, welcome to the podcast. Alexis Kingma: Thank you so much for having me. I'm excited to be here. Mike: Well, I am a huge fan of our exams and certifications. And you can take one, you don't have to have the other, and I like to have both. But I love that we have a lot of exams and we redo them, we update them, we refresh them, at least we try to. I feel the product now is changing super quick. But before we get into all of that, Alexis, tell us a little bit about your history and how you came to Salesforce and what you do at Salesforce. Alexis Kingma: Absolutely. So I am on the Salesforce certification team. We are a team of Salesforce employees who are solely dedicated to creating and updating the whole suite of Salesforce exams. So, historically, I come from a certification industry background. I've done software certification my entire career. And I came to Salesforce about two, two and a half years ago and just hit the ground running. I joined the team updating and creating new Salesforce certifications. So I actually started with the Tableau certifications and have since moved over into my latest, which is refreshing the Salesforce Certified Platform App Builder exam. Mike: Ooh, yes, app builder, that's something all of us admins are near and dear to our hearts on. And that's cool. I mean, I guess there's enough tech out there in the world that there's enough people that need to write certification exams for all of it. Wow. This is one of those ideas of, I bet 20 years ago, that job maybe didn't exist, but it exists now. Alexis Kingma: It's funny, certification is such a rich industry, it's one of those jobs that I feel like nobody knows it exists until you have that job. Nobody grows up saying, "I want to write tests," but now it's all of our favorite things to do. Mike: No, I mean, you're exactly right, nobody sits down and, "What do you want to do when you grow up?" And it's, "I want to sit down and write really hard software questions for people about a cloud-based platform that they can configure declaratively." Alexis Kingma: Right. Mike: I think if you would've answered that, your teacher would've been, "And you're an astronaut today." Alexis Kingma: But it is interesting, the same principles that we use to write Salesforce software certifications are the same principles that are used for the medical boards, for firefighting certifications, for airline certifications. And so when we come together at certification industry events, it's a whole gamut of industries coming together to talk about the same certification principles. So you get to meet a lot of interesting folks. Mike: I mean, you don't ever think of that, but that is really... Wow, I bet that's really interesting to sit across the table from people that write certifications to be a rocket scientist. Alexis Kingma: Absolutely. Yes. A lot of these certifications, like for a professional roofer, that's a high-stakes certification, or an architect. So it's interesting to hear how all these different industries approach the same problems. Mike: Yeah. Well, we're still high stakes too. Alexis Kingma: Absolutely. Mike: So you mentioned Platform App Builder exam. It got a refresh, which it's probably needed, I mean, every few months, right? But I think before we get into that, what does it mean to refresh an exam? Alexis Kingma: So the Platform App Builder exam has been around for over 10 years. It predates me at Salesforce by far. We're actually in our 11th year this year, which is awesome. And so it's been around for so long and the role changes and evolves so much in that time. And so it's important for us to look at the role, look at the requirements in the industry, what are admins doing, what are app builders doing, what are architects doing, what is the most important knowledge that those roles need, and how does our exam align to that? And making sure that the things that we're testing out on the exam are actually things that are the most important for these roles in the real world. Mike: Yeah. I mean, that was always one of the hard parts, I remember, when I first got one of my certifications. At the time, we didn't use a lot of Service Cloud, Agentforce for Service, I think now, but I had to go out and learn it because it was part of the certification. And I thought, "Oh, why should I have to learn that?" And I thought, "Well, just because you don't use it or your company doesn't use it, doesn't mean it shouldn't be part of that certification as well or that exam." Alexis Kingma: Absolutely. And so when we approach doing a refresh like we did with app builder, we try to include subject matter experts from a whole range, internal Salesforce employees, external Salesforce users, a wide breadth of roles, admins, people who are solely app builders, architects, to try to say, "Okay, Salesforce might say these topics are most important, but what is the industry saying is most important?" If somebody's looking to hire an app builder, what does that person expect the app builder brings to the table and what knowledge should they already have when they start the job? And so we rely on our subject matter experts to say, "What are those most important concepts, and how do we make sure that they're reflected on the exam?" Mike: Makes sense. I mean, that's the part of getting dialed in, to me, that I think is the most important is, one thing for Salesforce to think this is important, but where does that fall in terms of your responsibilities and what you're seeing day to day? Well, let's talk about this new exam, because Platform App Builder, I believe if you said it was been around for 10 years, then I've been at Salesforce when it was launched. What did it originally... Not originally, back in the day have, but what were you refreshing from and really refreshing to? Alexis Kingma: I'll say the biggest change between the previous version of the exam, which had been refreshed maybe one or two years ago, to this new version of the exam is really increasing the emphasis on Flow on the new version of the exam. In talking to our group of subject matter experts, hearing from the community, we just continue to hear Flow is such an important piece of being an app builder and being able to do that role, that it needs to be tested. And we actually added it to the exam with quite some depth, not only testing can you create flows, can you choose which flow for which situation, but also can you troubleshoot flows? Can you maintain and monitor them? Really asking the app builder to get deep into flows and making the assertion that flows are a key piece of being an app builder at Salesforce. Mike: I mean, that makes a lot of sense. It's funny, I'll ask you later, but I'll be curious to see your answer on it. I mean, when I think of app building, it's a collection of stuff and then there's that automation piece. But also, really diving into Flow like you did really helps set the admin up for being an agent builder as well, right? Alexis Kingma: Absolutely. And that's another change we made to the exam is adding Agentforce, specifically how you can use Agentforce as an automation tool on the exam. So I don't want to say you must be an Agentforce superuser to be able to take that exam. That's absolutely not the intention. We have an Agentforce specialist exam for that. But really just more about knowing that Agentforce is a tool in your tool belt that's available, and when might it make sense to reach for that tool. Mike: So I'll come to that question now that I get asked, and you can decide if you want to answer it or not. But I was asked last week, do admins still build apps? Alexis Kingma: Yes. I'll say, from what I've heard, yes. We, as part of this refresh, go through the roles that this exam most aligns to, and Salesforce admin was the number one. So when we got our group of subject matter experts together and asked, "Who is taking this exam? Who should be taking this exam?" Salesforce admins was the number one thing that people said. Mike: Yeah. No, I agree. I think it's interesting to live in the time we do now where, I mean, I had somebody send me a link the other day of a dashboard that an agent had coded for them. And it was kind of temporary. It wasn't meant to be any kind of source of truth. But when you think about it, sometimes the permanency of the app, I think that's where that question was going. And I still very much believe that it's the agent that jumps in and adds the additional layer that perhaps goes across apps. Alexis Kingma: Agree. I hear from our community over and over that knowing how to get in there and actually build the flows and customize and all the checkboxes, and what they do and what they mean and what they cause is so important and continues to be important even with the new agentic world that we live in. Mike: Right. And you mentioned part of the refresh process is also gathering a lot of feedback from not just admins, but customers and employers that hire admins. What were some of the things that they pointed out as admins still need to understand these things? You refreshed it for Flow and Agentforce, but that's not the whole exam, right? Alexis Kingma: Correct. And you'll see, it's funny, we still kept Salesforce fundamentals and we still kept user interface. And the funny part is that I was actually looking at much older versions of this exam through this refresh process, and those are the same topic areas that have been around, I don't want to say since the first version, but that have been around since the beginning. And it's because they continue to still be important. Every refresh, we pressure test and say, "Okay, do you still need to know object record and field access? Do you still need to know reports and dashboards?" And the answer continues to be yes. And so those will continue to live and be tested on this exam because they continue to be important. Mike: Yeah. Now, from your advice, if a Salesforce admin's listening, maybe they don't have a certification yet or they haven't taken any of the exams, what would you advise in terms of preparation to get ready for this exam? Can they come out of the gate and take it or is there kind of understood prerequisites to this? Alexis Kingma: All Salesforce exams are designed to test your hands-on experience. And so they're designed so that, yes, you can read documentation, but they're testing that you have some hands-on experience going into the exam. But, that said, that's where Trailhead becomes a huge asset if you may not have had access to actually get into a sandbox and play around with all these different topics. So exciting for this refresh, we created a brand new exam prep trail. We had existing prep trail badges before, but those have been retired in favor of this new exam prep trail. And what's most exciting is it does prioritize the hands-on badges available on Trailhead. So there's opportunity within each section to get in there, spin up an org, and actually play around with the types of topics that are being tested on the exam. So if you don't have the opportunity to get hands-on experience with every single thing tested, this trail is an excellent opportunity to still be able to prepare for the exam and take the exam regardless. Mike: That makes sense. I mean, I think that's always the biggest question I get asked when I'm at user groups or at an event is, "What should I do to prepare for this?" And it's one part just learning. You don't want to study for the test, as they say. You want to study to learn it and understand it. I think that's why the practical hands-on part of it, really what can they build is important. Alexis Kingma: And I'll say too, a tip that all of us on the Salesforce exam development team share when we can, is every exam, this one included, has the exam guide, and there's really a lot of information and clues within that exam guide. We list all of the exam objectives, what we call them, all the different content areas tested on the exam. And they're really written very intentionally and with a lot of detail in mind. So thinking about if an objective says, "Create and configure flows," we're not just asking you to describe them or have a high-level understanding of what they are or when to use them. We're really asking, can you get in there, get your hands dirty, create and configure them? And so that's kind of a clue, "Hey, I should be getting in there. I should be clicking around. I should know what each of these buttons, each of these checkboxes does," because that's the kind of question that's going to be asked on the exam. Whereas something like describe or understand, maybe that is more of a high-level just, "Hey, can you explain or describe, but maybe not necessarily get in there and do?" So I think paying attention to that can help direct how you study for each of these objectives. Mike: One thing I thought of, and this was back when I was getting my admin certifications, was describing the value of it to my manager and to my users. And I won't tell you my answer because I want to hear your answer first, but if you were to put yourself in the seat of a Salesforce admin listening to this podcast that's like, "I really want to go and take that exam. I really want to get that certification." How do I justify that or how do I make that case to my employer and to my users that this is worthwhile and worth my time? Alexis Kingma: It's such an important question, right? Because that's the big question is how can I get buy-in to study for this, to get support to take this? I think the biggest one is that a certification at its core is a validation of knowledge. A certification is a statement that you possess the knowledge and have the skills and abilities that are tested on this exam. And so for Platform App Builder, these are the knowledge, skills and abilities that not only Salesforce, but the industry in the group of subject matter experts that helped develop this, this is what the industry is saying is most important for an app builder to know and be able to do in the market right now. And so by earning the certification and saying, "Hey, I have the knowledge, skills, and abilities that are most important for an app builder," you're bringing a lot of value to your team. You're bringing a lot of the learning that you gained through studying. You're bringing a lot of expertise to your team to be able to bring back and show what's the latest and greatest that Salesforce is doing now, and actually be able to implement it. Mike: No, spot on. I would also just add one word, confidence. Alexis Kingma: Yes. Mike: I walked on water the day after I passed my admin certification, because I finally felt like everything that I thought I knew, was verified. I don't know what the right word is. Verified comes to mind, but it's probably not the right word. And I was like, "Yes, that feels right to me." We talked about the prep trail, which I think is important because, boy, for a while there, preparing for a certification was reading some sample questions and hoping you kind of had your bases covered. I think that prep trail is really, really good to help get you hands on. Now, I'll say this because I think I know the answer, but I want to make sure. Even if I complete that prep trail, that doesn't mean I'm going to pass the certification exam, right? Alexis Kingma: I'm so glad you asked. Mike: Yeah. Alexis Kingma: The prep trail is one piece, but I think there's no guarantee, to be honest. There's no way to say with 100% certainty, "I will pass this exam." I think the prep trail is one piece. Like I mentioned, the hands-on component or experience is really important. And so, in addition to the prep trail, I think the best way to assess your level of readiness really is to go through that exam guide and those objectives on it, and just kind of do it a little self test, "Hey, let me read this objective. Is this...
/episode/index/show/buttonclickadmin2/id/42568620
info_outline
How AI Could Change the Way Admins Set Up Salesforce
08/20/2026
How AI Could Change the Way Admins Set Up Salesforce
Today on the Salesforce Admins Podcast, we talk to Khushwant Singh, SVP of Product Management for the AI Application Development Platform at Salesforce. Join us as we chat about how rethinking the Salesforce stack for AI with Headless 360 will change the way admins set up complex systems. You should for the full episode, but here are a few takeaways from our conversation with Khushwant Singh. Opening Salesforce to AI agents AI is changing more than how we find information or generate content. It could also change how Salesforce Admins configure the platform itself. I sat down with Khushwant “Khush” Singh, to learn about Headless 360 and the work happening behind the scenes to make Salesforce accessible to both humans and AI agents. “Headless 360 is about bringing Salesforce to wherever you need it,” Khush says. In a headless platform, he explains, the frontend is separated from the backend. So you can use Salesforce data and visualizations on your website without changing the design, or change records in Slack without having to open an extra tab. But Salesforce Headless 360 is about more than portability. Khush and his team are translating the entire platform into a set of model context protocols (MCPs), skills, and metadata that can interface directly with AI agents. And that opens a world of possibilities for what admins can do with conversational tools. What if setting up Salesforce became a conversation? “For the last 27 years, layers that make up the Salesforce platform have been put in place for a human,” Khush says, “so we’re trying to open this up for both a human and an agent, so the agent can do that work on behalf of the admin.” Setup with Agentforce, which streamlines configuration for admins with the help of an AI assistant, is a great example of what Khush is talking about. You can use natural language prompts to create objects, Lightning pages, and flows; manage users and user access; and troubleshoot formulas. Headless 360 lays the groundwork for a future where setting up Salesforce becomes a conversation about your business goals and processes. No coding required. Admins still stay in control None of this removes the admin from the process. Khush is quick to point out that the goal is for agents and admins to work together, with humans still initiating actions, validating results, and providing governance. His advice for admins right now is simple: try Setup with Agentforce and start getting familiar with what this new way of working feels like. Because the biggest shift may not be AI helping you use Salesforce faster—it may be AI changing how you build Salesforce in the first place. Listen to the full episode for more from Khush about Salesforce Headless 360 and how AI could change the way we set up our orgs. And don’t forget to subscribe to the Salesforce Admins Podcast to catch us every Thursday. Podcast swag Learn more Salesforce 360 Blog Post: Salesforce Admins Podcast Episode: Salesforce Admins Podcast Episode: Salesforce Help Article: Salesforce Admins Blog Post: Salesforce Admins Blog Post: Trailhead: Admin Trailblazers Group Social Full show transcript Mike Gerholdt: This week on the Salesforce Admins Podcast, I'm joined by Khushwant Singh to talk about what happens when Salesforce stops just being a destination and starts becoming part of every system your business already relies on. That's right, from Headless 360 to Setup with Agentforce, Khush breaks down how admins are moving beyond configuring features and into orchestrating how data, AI agents, automation and people work together across the business. Now, we're going to dig into what Headless actually means for admins, why governance and trust matter more than ever in an AI first world, and how Salesforce is building toward a future where setting up complex systems really becomes more of a conversation than a checklist. This episode is really about systems thinking, how admins can connect experiences without forcing teams to rebuild everything from scratch. So if you've been trying to figure out where AI fits into your role or how your role is evolving alongside it, I promise you this episode gives you a practical look at what's already happening and what's coming next. So be sure to hit that subscribe button. Share this episode with your favorite architect or admin friend, and let's get Khush on the podcast. So Khush, welcome back to the podcast. Khushwant Singh: Thank you for having me back, Mike. Mike Gerholdt: I say that because I had to look and it was 2022 back in the day you were talking Experience Cloud when we last had you on. You've since moved on, moved up, had your hands in a lot of things, did an admin keynote with me. So let's start there and let's kind of catch everybody up on some of the products you've been working on, and then we're going to talk about the newest one that we launched at TDX this year. Khushwant Singh: Yeah, happy to. And again, great to be back. I think back in the day, started obviously with Experience Cloud. Experience Cloud really was building a product that is external-facing and again, it's built on the same platform. And again, as we looked at the product portfolio, it just made sense to start to bring things together. So we've actually sort of rolled and morphed into the application development platform, obviously within the platform organization, everything pro-code, low-code, desktop, mobile. And so there've been quite a few products leading up to here, anything from our delivery on mobile, mobile offline, the Salesforce mobile app, all the way to Agentforce Vibes, the Agentforce Experience layer, obviously a fair amount of work on the Headless side of things. So yeah, it's been quite a journey to this particular point, Mike. Mike Gerholdt: Yeah. I mean, it's actually hard to point out things that aren't admin-friendly that you've had your hands on because you've always kind of championed everybody being able to build on our platform. So let's talk about TDX this year because we launched Headless 360. Khushwant Singh: Oh yeah, we did. Mike Gerholdt: By the way, in case you forgot. Khushwant Singh: Yeah, it was a massive announcement. I think, look, as you think about what's happening in the market right now, you've got customers engaging through many different surface areas. We've got customers on ChatGPT, on Claude, on Gemini, Teams. At the same time, you've got developers also using a variety of different tools, different IDEs, different coding agents. And so I think Headless 360 really is a testament to acknowledging this change in the market in the industry and trying to meet the customer where they are. The customer being an end user or the customer being a developer and admin, just meeting them where they are in whichever tool, whichever interface they might be. Mike Gerholdt: Yeah. I mean, do you recall ever a time in technology when it was, I hate to use the euphemism, but like the Wild West where I feel like there's so many choices for what you can do just in regards to AI? Khushwant Singh: There is. And there is obviously a good side to it. There's also a downside to it. The good side is really your [inaudible 00:04:31] for choice. There is innovation that is helping you drive productivity day in, day out. The downside of this is you just have to be really careful about quality, about trust, about governance. And you have to ensure that while you're going fast, you're not sort of compromising on that trust aspect of things. And that's what we're trying to do here at Salesforce and just trying to be a little bit more thoughtful in our approach over here. Mike Gerholdt: Yeah. So my developer friend, Josh Burke, who comes on the podcast, usually has to explain things to me every now and then. I think developers are very familiar with the term headless. Khushwant Singh: Yes. Mike Gerholdt: I'm not sure outside of Headless flows, which I know what those mean, I'm not sure admins could understand or could confidently buzz in on a game show and answer what is Headless 360. So can you help them kind of understand what is Headless 360 if they had to tell their manager? Khushwant Singh: Yeah, sure. So one way to think about it is, let's say you're a customer and you've got your own website, it's built out of React, it's not built on the Salesforce platform, but there is so much of your goodness and investment that you have within the Salesforce platform that you want to be able to easily reuse in the context of this other website that you have, portal that you have, mobile application that you have. All of that may not be built on the Salesforce platform. You want to be able to reuse your investment seamlessly. And so Headless 360 really is about how do we empower you, the customer, to be able to easily use those assets, those investments within the Salesforce platform in that surface area that you've got that may not be on the Salesforce platform. So it's really about giving them that flexibility so that they can easily reuse their investments in all of these various surface areas and just meet their customers wherever they are versus bring their customers into Salesforce. Mike Gerholdt: Yeah, I think it makes sense. I mean, I was a customer way back in '06 when I remember it was like transfer and move to Salesforce, and everything was "have it on the platform, have it on the platform." And then shortly thereafter it was kind of like almost the realization that we had was, "Well, it's a lot of friction to constantly move platforms. What if companies just integrate and we become that connector to everything?" And I feel the same way with this. Khushwant Singh: 100%. And you know what? Look, I think the one example is if you go into the Williams Sonoma website, right? Williams Sonoma website, it's not built in Salesforce, but if you use their sous chef AI, I think... I'm not sure what they call it, but- Mike Gerholdt: I'm sure it's something really, really snappy and small. Khushwant Singh: Olive. Olive. There you go. Mike Gerholdt: Olive. Yeah. See? Khushwant Singh: A snappy name right there. That agent is an Agentforce agent, right? So that's on example where Salesforce is being used in whichever head that you'd like us to be in. And so in this particular case, the Salesforce agent is in the Williams Sonoma website. So that's just one example where we are trying to make it easier for this integration to happen through the Headless 360 platform. Now that's one view. And that's the view, I would say, an easy way to try to understand what it means for Headless 360. Mike Gerholdt: Yeah, because then as an admin, as a developer, you're not having to sit down and say, "Okay, well, if we move to the Salesforce platform, we have to deprecate everything that we just spent the last two years building on our site." Marketing's like, "No, no, we just got the site pixel perfect the way we want it. Now we can integrate best of everything that we want." For admins who aren't thinking of maybe websites, how does Headless 360 play into other integrations that they may talk to IT or internal stakeholders about? Khushwant Singh: Yeah. So for example, when admins are chatting with their other internal team, they may have a custom application that they already have in place and they want to be able to have Salesforce data, Salesforce visualizations surface in whichever application they may have already, right? That's one example. So again, it is about bringing Salesforce to wherever they may already have. So for example, an admin may have a business application that already runs within ChatGPT. So ChatGPT, for example, it allows companies to create bespoke applications. And if you want to be able to integrate Salesforce into that application, that's doable as well. It doesn't have to be in ChatGPT. It could be in any other existing non-agentic application as well. But it's about that, look, you don't have to rebuild everything. Wherever you are, you've got an existing application, we'll find a way through Headless 360 to be able to bring Salesforce to it. Mike Gerholdt: Yeah. No, it totally makes sense. I mean, in that way we can really think about how are we making sure that the departments have the software and the tech that they want, but also access to all of the information that they need to do their jobs the best. Khushwant Singh: Mm-hmm. Mike Gerholdt: So Headless 360 is a big thing we talked about. I also know I saw you in some True to the Core and True to the Core Deep Dive stuff. Was there some features you were talking about in that that possibly play into what admins are going to be working on for the rest of this year? Khushwant Singh: Well, yeah. I mean, a few aspects as we think about Headless 360 that would be of interest to admins. So first and foremost, you've all seen the stack diagram of the Salesforce platform. You've got those four layers. You've got your layers of engagement, you have layers of context, you've got the sort of our data foundation, et cetera. So you've got those layers that make up the Salesforce platform. For the last 27 years, those layers have been put in place for a human, right? And now what the product teams and the engineering teams are doing are going back and saying, "How do we now open this up both for a human and an agent so the agent can do that work on behalf of the admin when the admin sort of wants a task to be done for that particular reason?" And so what that means is that we're translating our entire platform into a set of MCPs, a set of skills, a set of metadata that is grounded so that these agents can do the work on behalf of the admins. So one good example is the setup with Agentforce, which is so far so good. We've gotten great feedback on it. Now behind the scenes is a set of skills, a set of MCPs that are firing off to be able to get their tasks done. And so that's one thing that I think our admins can look to benefit from. The other piece is I know we have some admins who are familiar with some of these IDEs that we have out there. They use Cloud Code quite a bit. They use Vibes quite a bit. It may not be the entire admin audience, but for those audiences, again, the ability to be able to use all of these MCP skills in these development environments is another thing that our admins can really look forward towards. Now the other thing that we've also worked on is, over the last few months, the foundation for these skills, these MCPs, this Headless 360 foundation has been very sort of focused on how do we unblock these pro-code use cases, whether that's in Cloud Code, whether that's in Vibes, et cetera. But this is the same foundation upon which as we speak in safe harbor, I share that we are building what we call our no code offering as well. So how do you go about in an unintimidating sort of type of interface, have this conversation with an agent, which behind the scenes is interacting with that same Headless 360 layer to help you build out your agents, your applications, to help you augment your existing agents and applications, help you set up provision, configure Salesforce from a zero to one point of view, because we all know how setting it all up is quite a taxing task for our admins? So that's the potential I see for Headless 360 for our admin personas. Mike Gerholdt: Yeah. I mean, to go back on some of the stuff that you were mentioning, I remember the first time I thought, "Hey, I could have ChatGPT rewrite ChatGPT's instructions." And I remember thinking like, "I'm so far ahead of the curve, man. I'm making AI rebuild AI." And then it was only a few weeks later that Cheryl was demoing Setup with Agentforce and I thought, "Oh, that makes so much more sense because all of the things that you were having that setup agent do are things that not necessarily admins don't like doing. It's like paper cuts." It's the little things that take 20, 30 minutes out of your day when you really wanted that solid hour to build that application kind of start to finish. Khushwant Singh: Indeed. Indeed. So we really viewed Headless 360 as the foundation upon which agents can work on behalf of the admins. And again, look, this is agents and admins working together because again, we've got to have the human presence to be able to validate, to be able to interrupt, to be able to initiate any actions that are performed by the agents. And if these agents can help drive greater productivity, then it's a win-win while at the same time having governance by humans over it. Mike Gerholdt: Right. Absolutely. Do you envision us being at a point where all of setting up Salesforce could just be a conversation with an agent based on the business and what they're trying to accomplish? Khushwant Singh: We are trying to do that. We are trying to do that. Now, I'll give you a view into our approach over here. We're taking a steel thread approach here where just trying to, for example, set up a customer service agent. That cuts across Service Cloud, cuts across platform, cuts across Agentforce, cuts across Data Cloud. So we've got to take a system view, an end-to-end view versus a feature view because that's what our admins go through. That's what a practitioner goes through. They look at it from a steel thread point of view, and that's what we as product teams have to do. And so as we think about using agents to go ahead and help provision, set up, get Salesforce up and running really quickly, that's the new strategy that we are taking over here, a steel thread view so that we can look across the board and say, "Look, which MCPs are missing? Which skills are missing? Which APIs are missing? Which metadata needs to be grounded? How do we ensure that across entire steel thread, quality is being ensured, governance is being woven into?" So we are starting that way and we want to scale that way as well. So my hope is that come Dreamforce this year, we'll be able to at least have a sizable number of steel threads that we feel really, really confident about on Agentforce really helping and agents helping in this particular side of things. So yeah, that's the approach we're taking, Mike. Mike Gerholdt: Wow, that's going to be amazing. Every time you think, "Oh, we've probably invented everything," technology just comes along and pulls the rug out from underneath of you and says, "Haha! There's new stuff. You got to figure this out now." I'd be curious, you're so ingrained in a lot of things that admins do on the platform, a lot of things developers do on the platform and then also having to keep up with AI. What is a piece of advice you could give people for how you personally keep up with the newest news and innovation on what's going on with AI? Khushwant Singh: Wow, that's a good question. I think first and foremost, I spend a lot of time just looking at reading publications like what's on TechCrunch, what's on Techmeme, trying to just understand how are technology providers adapting, how are companies using AI. That's one. The second one is actually you learn a lot via speaking with others in the community, right? Mike Gerholdt: Mm-hmm. Khushwant Singh: You talk to customers, you talk to other admins, you talk to other developers and you get to understand there are use cases that they're working through and some of the very many innovative workarounds or users of AI that they're applying. And then you're thinking about this that, "Wow. There's a trend here, there's something that we should be backing up and maybe providing out of the box within the product." And so I think that community piece speaking with other customers, with your peers, your colleagues from...
/episode/index/show/buttonclickadmin2/id/42490025
info_outline
Stop AI Hallucinations with Better Salesforce Metadata
08/13/2026
Stop AI Hallucinations with Better Salesforce Metadata
Today on the Salesforce Admins Podcast, we talk to Skye Tyler, Principal Solution Consultant at Beyond the Horizon Technology. Join us as we chat about why clean metadata is crucial for getting the most out of AI. You should for the full episode, but here are a few takeaways from our conversation with Skye Tyler. Why metadata is your training manual for AI You’ve done it, I’ve done it. Sales wants a name changed on a report, so you just change the field label rather than create something new and mess with the integrations. Or maybe you have four different dates, but your marketing team knows which one they’re actually looking for. What’s the big deal? The problem is that while humans can get by on institutional knowledge, AI agents need a bit more help from your metadata. As my guest this week, Skye Tyler, explains, you should think of AI like an overenthusiastic intern with short-term memory problems. It really wants to answer your question, so if it sees four different dates, it’s going to take a guess. Think of metadata like an onboarding manual for AI. With clear field descriptions and help texts, you can point your agents in the right direction and prevent hallucinations. How to get started with metadata cleanup Obviously, cleaning up your org’s metadata is easier said than done. However, Skye has some great tips for how to get started. If your business has busy periods and slow periods, you might be able to schedule time specifically to work on your metadata. But for the rest of us, Skye recommends a clean-as-you-go approach. Any time you update an object, set aside some time to review all of the related metadata and update the description. Similarly, any time your organization is building a new business process that includes AI, you need to clean up any metadata an agent could interact with. As Skye points out, while you don’t necessarily have time to deep clean your house every week, a little spot cleaning can go a long way. Skye’s Salesforce journey and the value of sharing what you know We also took some time to talk about Skye’s career path from nonprofit arts and what advice she has for folks who are new to the Salesforce ecosystem. AI is changing things fast, and that means there are more opportunities. “With all of these newer technologies and tools, anybody who's looking to come into the space today is learning the same things that I'm learning, having been in the space for a decade,” she says. The Salesforce community is incredibly supportive, and Skye recommends putting yourself out there. You never know who you’ll meet at an event, and where those connections could take you. “No matter where you are in your journey, you know something that other people don't,” she says, “put yourself out there, and I guarantee you someone's going to appreciate it.” Listen to my full conversation with Skye for more on how to clean up your metadata and stop AI hallucinations. And make sure you’re subscribed to the Salesforce Admins Podcast so you never miss an episode. Podcast swag Learn more Salesforce Admins Podcast Episode: Salesforce Admins Podcast Episode: Salesforce Admins Blog Post: Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins Podcast, I'm talking with Skye Tyler about the part of AI readiness that, well, it's easy to overlook. That's your metadata. We all know that clean data matters, but agents also need clear field descriptions, documentation, permissions, and context to understand what your business actually means. Skye explains why metadata acts like onboarding for an enthusiastic new employee and why a confident answer isn't always a correct one. We'll also talk about practical ways admins can improve metadata without trying to clean the entire org overnight. So give this episode a listen, subscribe wherever you get your podcasts, and of course share it with an admin who maybe has prepared their platform for Agentforce. And with that, let's get Skye on the podcast. So Skye, welcome to the podcast. Skye Tyler: Hi, thanks for having me back. Mike: I'm excited. Going through everything that we're doing to prepare for Dreamforce and admins are preparing for the agentic future, which is coming faster than eve, I stumbled across your session. And I thought, hey, before we get into Dreamforce, maybe we can dive into all of the stuff that you might not be able to cover in your 40-minute breakout session. So we'll talk about that because it's data related and data related is agent related. But before we get started, can you just refresh everybody on how you got started with Salesforce and what you do in the ecosystem? Skye Tyler: Oh, I'd love to. So I've been fortunate enough to be working in the Salesforce space with the nonprofit industry for a little over a decade now, and started off doing implementation work with nonprofit arts organizations, doing ticketing and donation. And then I've moved in and through the consulting space. Again, focusing primarily on nonprofits with a little bit of dipping into education along the way. And over the course of that decade, I've been fortunate enough to meet some amazing folks, yourself included, that has given me an opportunity to have the chance to share not just my journey, but my experiences, my struggles, successes, failures. And some of those avenues have included things like coaching and mentoring with super moms and the Salesforce military program, and then also just being really honored to be able to speak at community dream and events and events like Dreamforce and Trailblazer DX. Mike: I mean, that's a great answer. You know what's funny is so many people ask me, "How do I get started in the community," or, "What should I do?" And I feel like now I'm just going to point back to your answer because what you said was just perfect. Well, don't be afraid to share what you've learned, or what you're learning, or how you've learned it, or things you're working on because that's what people love to see. They love to see how you're doing it so that they can get an idea for how to do it. So thanks for answering a question I didn't have. Skye Tyler: Yeah, absolutely. I also just want to throw in, and I say this at many of my live sessions, that no matter where you are in your journey, you know something that other people don't. And everybody learns more when folks show up, and are vulnerable, and are willing to share those things. So definitely just give it a try. Put yourself out there and I guarantee you someone's going to appreciate it. Mike: Yeah, absolutely. Plus the thing I add to that is there's probably somebody out there like you that really needs to see somebody like you on stage. Skye Tyler: Yes, absolutely. Mike: So we talk a lot about data with agents and cleaning data, making sure your data's up-to-date, making sure your data's fresh, which every time I use the word fresh, I always think of how that plastic comes off an iPhone. I don't know why, but that's where my brain goes, because agents and AI and LLMs do a really good job of consuming a vast amount of information and giving it back to you in what you asked for. I think one of the things that we talk less about and that I want to talk to you about is your metadata, because I'll be honest, I pay attention to my metadata for five seconds when I'm creating the field. Skye Tyler: I'd say that's four seconds more than most people. Mike: Right, because all you got to do is click outside the box and it fills in the developer name, so I'm good. And description, ah, fill it in later. Skye Tyler: Yeah. And for the longest time, that's been really standard. And again, working across several consultancies and with lots of different works, people assume, well, we know what this field means. You give it a field name, the team knows what this means. I don't need to fill in description. I don't need to fill in help text. It's fine. And again, for the longest time, that institutional knowledge was enough of a stopgap that it was fine. Nothing was going to break or go horribly wrong if you left the description field empty. But all of that changes when you start introducing agents. And an example I may reference a couple times on this podcast is, I don't know if you've ever heard this, but the idea of thinking about your agent as a really enthusiastic intern with short-term memory problems. Mike: Like memory of a goldfish. Skye Tyler: Yes, exactly. So if you've got a new intern and they don't have deep industry experience, or they don't have longer term institutional memory within your organization, and they come on site, they're excited to be there, they're energized, they're probably young and enthusiastic, and they're going to sound really confident. You're going to ask them a question. They're like, "Yeah, absolutely. I can absolutely do that." But there's a difference between sounding confident and actually knowing the answer. And where AI gets really tricky is not only does it sound confident, it usually has a certain level of fluency to it with the amazing jumps in natural language processing over the past few years, it sounds both confident and right because it's just a well-structured sentence. And there's a huge gap between the structure of the sentence and the actual understanding of the data behind it. Mike: Right. It reads to us as so confident in its own answer that we would be silly to think it's wrong. Skye Tyler: Oh, absolutely. It would be a waste of time to go back and check it because look at how confident it is. Mike: Yeah. And look at all the part that I always think of is look at all the information it gave me. I asked it two sentences and it gave me four paragraphs of an answer. It must be right. Skye Tyler: Yes. And of course, don't forget that at the beginning, it also flattered you and said, "Oh, Mike, that's a great question. Let's dig into that." Mike: Yeah. You sound just like my AI. Skye Tyler: Exactly. Mike: "Of course it's a great idea, Mike. You should totally do that. Everything's a great idea." So when we think about that though, why is it making those mistakes? Because if we're paying attention, and I mean, I was even working on some content today that's like, got to keep your stuff fresh. If you're going to do call notes or have a summary agent, then make sure your salespeople are doing call notes and keeping it up to date or keeping the data up to date. Then why is it so confidently giving us, I don't want to say the wrong answer, but confidently providing us with information that it thinks is correct, but isn't? Skye Tyler: Yeah. So a big part of this comes down to the difference between how humans think and form answers and how the large language models do it. And one of the real risks around this false fluency framework is that you pose a question, you ask a question, and first there's the basic understanding that the agent, whichever model or system you're using, their goal is to accomplish the thing that you asked. So the first thing is getting really careful about how you ask your questions so that you're not sort of setting it up to just affirm the thing that you have asked. But then beyond that, the way that these LLMs, these large language models work, is it's basically a really complex pattern completing process. And so you mentioned peeling that plastic off of your new iPhone. How many times are you typing a text message on your iPhone and it has that auto recommend that comes up right above your keyboard? Mike: Yeah. Skye Tyler: So that's a good example of a simple version of this. So depending on how often you type in "Oh my," and then it's going to recommend a couple of different things that often come after "Oh my" in the training data. When we're thinking about this in the context of asking an agent something in Salesforce, the way that it identifies what to propose for an answer is not looking at just the data in the field, it first has to go look and see what information is available and that's when it dips into the metadata. So if you've got four different fields that have very similar field names, but have no metadata to tell the agent field one means this, field two means that, field three means this, and field four means this completely other thing, it's just going to guess. Mike: So if you had four dates on a record that were, I don't know, draft dates because it ties to a contract or something, and it's draft one, draft two, draft three, draft four, and you know as the user, those are the dates that you completed those drafts, but your metadata just shows four draft dates and there's no explanation for the agent. So the agent's like, "Here's when all the drafts were completed." Skye Tyler: Right, it's going to guess. And because it's non-deterministic, it might guess right the first time you ask it a question. It might guess right the second, third, fourth, fifth, 20th time, and then the 21st time, it guesses wrong. Mike: But confidently. Skye Tyler: But confidently wrong. Mike: Confidently. Right. Skye Tyler: Right. And so when we're thinking about how to support our agents, if we go back to that analogy of the over-enthusiastic summer intern, the metadata is effectively the onboarding process for that new intern or a new employee. It's the manual about what your data means, and it's the context that the agent can use to give you more consistently reliable, correct answers. Mike: Love it. So I remember, I think it was TDX two years ago, we were talking kind of on this subject. And whenever we roll out a new feature, it's here's the things you need to do to prepare. And I remember getting up and talking with a lot of people of like, "Hey, it's more than just the data that's got to be cleaned because there's a lot of data cleaning services and hopefully you have a lot of validation rules and stuff in place, but also your metadata needs to be cleaned as well." And I looked over in the audience, I felt this guy just shrug his shoulders and just kind of turn a lighter shade of pale, I'll say. And I walked up to him afterward and I asked him, I was like, "Are you okay?" And he's like, "Yeah, your words just hit me really hard. I was thinking of all the metadata I have to clean up." So obviously it would be awesome if every day people woke up and you cleaned your whole house. But let's be honest, you don't have to wake up every day just to live in your house to clean your whole house. What is the approach that an admin should think of in terms of getting their metadata to that next level and to prepare for an agent force implementation? Skye Tyler: Yeah, I love the analogy of cleaning your house every day because I'll tell you, I do not wipe my baseboards every day. Mike: oh, man. I would pay somebody to come once a week to do my baseboards. It would be awesome. Skye Tyler: Yeah. So there's a couple of ways that you can look at this. The first one is figuring out within your workflows, your day-to-day and annual workflows, where you can build metadata maintenance into your process. And so what this might look like for admins is the next time someone on your team asks for an update on an object, whether it's a page layout, or some new fields or what have you, taking and building some extra time into however long you budget or allocate for that task to include reviewing related metadata. Every time you need to update a flow because the business process has changed and you say save as new version, as soon as you click save as new version, update the description of the flow. That's the first thing that agents are looking at to be able to figure out what automations do I call, what automations are related to a process, et cetera. So building it into the workflow of what you already do is one avenue to consider. If you have an amazing organization that lets you do proactive maintenance, working that into your project plan and saying, "Hey, this is a usually kind of quiet time of the year for new admin requests. Let's go ahead and block two weeks or three weeks and do a more thorough or a deeper dive into updating the metadata." If you work at one of those organizations, let me know, because I've heard they exist. I haven't encountered one in the wild. But then lastly, when you have any new agent related process, it should be considered mandatory as part of that project to do a metadata review of every aspect of metadata that that agentic process is going to interact with. Because one of the big challenges that organizations have been seeing is they're putting a lot of time and resources and money into creating agentic solutions, but the research and the data is just not showing the level of return on investment or the level of success that people are expecting. And one of several underlying factors is you're not setting your agents up for success. You've got this new employee, this new agent employee, but you didn't onboard them. You didn't provide them with adequate institutional knowledge and training. You gave them some direction. But if you think about it, Mike, when you've got a new employee that comes on and they go to that podcast or that blog record for the first time and they see your four review dates and they don't know, they stop and ask someone. They ping you on Slack and be like, "Mike, can you explain these four review dates to me?" Your agent can't do that. So set them up for success with that onboarding through the metadata updates. Mike: And I think that also, I mean, I really like how you approach that. I think that's also a funnel or a pathway that you could flip. So you don't have to think of, I have to tackle everything and clean all my metadata first, as opposed to, well, if we're going to roll out an agent and it's going to touch these three objects and these 15 fields, then that's where you start. Skye Tyler: Absolutely. Mike: Because then that will help you set up a plan for here's how we're going to tackle this part of it. And then as the agent responsibilities or you build additional sub-agents expands, then you can tackle two or three more objects that maybe that sub-agent has to talk to as opposed to, okay, we're going to wake up at 3:00 AM, clean the whole house just to live in it, which is a good idea. I think sometimes readiness to the extreme can feel overwhelming. Skye Tyler: Right. And if it's overwhelming to the point where you don't make any progress on it, then it's not useful either. So definitely thinking about what's within scope. Where I would challenge that a little bit though is unless you have put very firm guardrails on your agent, there's always the possibility that it's going to get creative. So you might intend for that agent to only look at these four fields, or these 15 fields, or these two objects, but if you don't actually instantiate that guardrail or that limit into how you build the agent, it could start to be like, huh, I wonder if this related record might impact me being able to answer Mike's question better. Let me just go take a look at that. And that's where we could get into some of the more deeper technical things, but the idea that authentication is not the same as permission. And so making sure that each of your agents has very clearly defined, and that ties in with the metadata too, because all of those settings in Agentforce and Agentforce builder are set up, the sub-agent descriptions, the scope, all of those things are metadata around your agents. Mike: And I think there's downstream effects to this that are also positive too. I'm thinking of all of the reports that you're dealing with that will suddenly get better because I know you're always building reports, sometimes not off of the report label. So help me through this. You've got an implementation and you have an integration with another system and you change metadata descriptions or field names. How do you need to...
/episode/index/show/buttonclickadmin2/id/42412745
info_outline
From Inbox Requests to a User Management System
08/06/2026
From Inbox Requests to a User Management System
Today on the Salesforce Admins Podcast, we talk to Michelle Wolfe, Platform Engineer. Join us as we chat about how she built a Flow-powered user management system to handle requests, approvals, user creation, permissions, communications, and even onboarding. You should for the full episode, but here are a few takeaways from our conversation with Michelle Wolfe. Streamlining change requests with screen flows It’s a good thing when your organization is growing, right? For Salesforce Admins, however, new hires need new accounts, and that means approvals, permissions, and onboarding. My guest this week, Michelle Wolfe, found herself in exactly this situation. She turned to Flow to build an automated user management system with no code, and she’s here to tell us all about it. Michelle’s company was bringing in 80+ people per new hire class, but the account creation request process was a mess. Managers would email a random member of the three-person admin team, and then they would manually create the account. So the first step was to wrangle the business process with a screen flow to get the correct information into Salesforce and create a case. But Michelle was just getting started. Now that everything was in Salesforce, she knew that she could use Flow to automate the rest of the process. New account creation with autolaunched flows Once the new user’s information was approved by their manager, Michelle set up an autolaunched flow to spin up the account. This took care of data validation, configuring the correct permissions, and creating a username. Finally, a second autolaunched flow would close out the case and send two email actions: one to confirm the request, and one to welcome the new user. With help from Flow and Einstein Copilot, Michelle transformed a complicated manual business process into something streamlined, simple, and scalable. Partner with your training team for a fresh perspective on your org Michelle credits her success with how closely she works with her training team on enhancements. “Because they interact with new employees, they see things differently than someone who’s been here for years and knows how we use our Salesforce,” she explains. That fresh perspective helps her identify improvements she might otherwise miss. Listen to my full conversation with Michelle for more on how she used Flow to automate user management—we really get into the weeds. And make sure you’re subscribed to the Salesforce Admins Podcast so you never miss an episode. Podcast swag Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins Podcast, I'm joined by Michelle Wolf to talk about what happens when user onboarding stops being a string of emails and becomes a real platform process. So Michelle built a Flow-powered system that handles requests, approvals, user creation, permissions, communications, and even offboarding, while keeping the admin team in control. We're going to talk about the automation behind it, but also the process decisions that make it accurate, secure, and useful for her business. Now, because when admins design access and onboarding well, they're not just saving time. They're protecting trust and helping people get productive faster. So listen in, subscribe, share this episode with an admin who has one too many user requests sitting in their inbox. I'll tell you who doesn't have too many user in requests sitting in their inbox, and that's Michelle. So let's get Michelle on the podcast. So Michelle, welcome to the podcast. Michelle Wolf: Thank you for having me, Mike. Mike: I think this is exciting because I can't recall the number of times I've had people on about onboarding users. And I think it's because whatever cool tool we have come out, it's the second thing people do. They're like, "Oh, I could do this, and I need to figure out how to do X, Y, and Z when I onboard people." Because it was like that with Flow. There was stuff with Chatter when that came out, "How do I onboard people and add them to groups?" And Jennifer Lee was at your session at Midwest Dreaming, and she thought it was just phenomenal. So I had to have you on the podcast to talk about it. But before we get into that, tell me a little bit about yourself, how you got started with Salesforce and what you do. Michelle Wolf: Yeah. So my journey started as a lot of ours as an accidental admin. I was working for a small family-run business who had Salesforce, and they were paying a consultant to basically be their full-time admin. And one day my manager walked into my office and said, "I don't want to pay them anymore. I need you to learn this." And I was like, "Okay." Mike: "I suppose." Michelle Wolf: Yeah. Why not? So yeah, that's what started my journey. And I skilled up on Trailhead and I was on it two, three hours a day trying to figure out how to be an admin in Salesforce. And this was back at the initial transition from Classic to Lightning. Mike: Ooh, fun. Michelle Wolf: So half of my early batches are on Classic. There just wasn't a ton of Lightning stuff out there yet. So I would build a lot in Classic and then flip it over to Lightning to see what it looked like because they did like the Lightning interface, which was great. So that started my journey. And then when I decided to part ways with that company, I took a different position and paused my admin career. And then about five years ago or so, I had an opportunity to be a product SME for Salesforce. And I was like, "Yes, I miss this product. I miss doing this. I miss being able to make things better with just the click of the button. So let's go do this." And I jumped in both feet and never looked back. And so I've been an active admin for a little over five years now. And I'm a Flownatic. Anything I can automate, I am doing it. Mike: I love it. Active admin as opposed to passive. Michelle Wolf: Exactly. Mike: I don't know. So I love when you started because I remember those times and the reason there wasn't enough Lightning things is we were all writing it as fast as we could. Michelle Wolf: Yeah, I know it. Mike: It's kind of like learning to drive with a manual. And then they're like, "Oh, well, here's an automatic." And you're like, "Oh, I already know how to drive with a manual." I mean, if you knew how to do things in Classic, then doing stuff in Lightning was just that much easier, in my opinion anyway. Michelle Wolf: Yeah. I agree. I agree. And the user experience was better for my users. They liked the layout and the feel. It jived with their personalities better instead of that very formal grid-looking everything. Mike: I mean, that was the internet at a certain period in time. And then it grew up and it was like your eyes don't have to squint with white space. Michelle Wolf: Right. Mike: Every field just went from tight polyester pants to sweatpants. And it was like, "Yay." Michelle Wolf: Exactly. Mike: Let's talk about being a Flownatic because I've talked with Jen. I know Jen said she was in your session. I really think, I mean, outside of just it's so incredibly powerful, the amount of things that you can do on the Salesforce platform without writing a single line of code. Flow is one of those. And I remember it was 100 years ago that I saw Flow for the first time at Dreamforce when I was a customer. And I think they called it Business Process Management or something. And it was an app you had to download, and then you had to upload schemas to it. It's since graduated into a much more robust tool. But the nice thing is once you know that, I mean, caveat emptor because AI runs off of all the flows. I mean, if you're good at Flow, there's very few things you can't make Agentforce do. So tell me a little bit about why you built onboarding with Flow. Michelle Wolf: Yeah. The company I was with found themselves in a really big period of growth, which was really amazing. But the new hire classes were like 80 people. And I just could not bring myself to want to spend a week of my life just filling in these boxes to make new users. It was really so time-consuming. And one typo here, one missed field here. My validation rules didn't check out. It was just a pain. It's just very mind-numbing. And I was like, "There has to be a better way." And I went through the different variations of the Add Multiple Users. It's an out-of-the-box function, except I couldn't put my custom fields on there, which means I couldn't save my users because we had validation rules in place. And then I experimented with a bulk upload, but it was such a pain because if I would typo a field, I would mess up my entire formula. Mike: Yeah. Michelle Wolf: And I was like, "There has to be a better way. There just has to be a better way." And- Mike: Plus then all you're doing is just creating the user. Michelle Wolf: Exactly. Mike: With Flow, you can do so much more. Michelle Wolf: Exactly. So by converting it to a Flow, I had a screen. I used my screen flows, and I leveraged the fact that the onboarding team is already putting that information into an email or something. Well, just go here and put it in a case for me. Just hit this button, pull out the fields. Now I don't have to do this. And then I used that screen flow to make a case so I can track my productivity, when the requests are coming in, when the requests are due by, who's doing the request. We started with just managing cases manually and making the users off the cases. And we had built in the approval process to make sure that someone else was double checking the inputs. Did they spell their name right? Did they put in the email right? Because I don't know these people. They're not going to be reporting to me. I'm not part of the onboarding team. I'm just making a user. So we had the managers do the approvals and make sure all that information's correct, make sure they're requesting the right... We use a field called Team Name that we made custom to make sure they're getting put on the right team, the customer service team or senior customer service team, whatever. So someone else is double checking it and then approving it. And I was like, "From here, I have to be able to automate something because the information's already in Salesforce." And that's when I got into utilizing that approval flow to trigger an autolaunched flow to actually make my user and create the alias and create the username and update the profile based off of what was entered on the request form in my screen flow, and just physically make my user. Mike: Wow. We spent a lot of time talking about the tech part of it. I want to dive in because I feel like you conquered a lot, but you probably had to sell it. Maybe you didn't. Tell me about all the non-tech stuff that you had to sell. Who did you have to go to, and what were the people you met with in order to say, "Here's how I'm going to onboard users moving forward"? Michelle Wolf: So the onboarding process had already been moved to our team. And it was just that it was coming to us in a very casual way. We're getting an email request. So it was part of the struggle was they started emailing us individually. We were a team of three, and they would just pick which admin they wanted to work with. Well, if I'm out of office or I have to leave unexpectedly and forget to put my out of office on, then their stuff's getting delayed. And so that was the first big conversation of how do we take out that portion? How do we get them to just put it in so we can decide who does the work? Because if I'm heads down on a project, I don't have five minutes to go make a user. I need to be heads down on my project. Mike: Right. Michelle Wolf: So this allowed us to divvy up work more easily and really even just check our own productivity of handling these types of requests and making sure it's not one person that always gets stuck with the work because they're the one that's always being emailed. So that was the first thing. And so the three of us, we were a really tight-knit group, and we're all very aligned with not wanting to be the only human that was pinged or emailed. And so it was like, let's just get it to a centralized place. And so we just went to our manager and said, "We're going to build this. We need this to be more productive." And they were like, "Yeah, makes sense. Do what you need to do." Mike: I mean, that's awesome. Michelle Wolf: Yeah. Mike: Sometimes when I was an admin would happen and sometimes it wouldn't. But I do think some change has to happen that way of, "No, here's how I'm going to be more productive, and here's what I want to set up." Michelle Wolf: Yeah. Mike: So then were there... I guess what I'm getting at is, for admins that hear this and like, "Oh man, this is me," were there other checks that were already in place that you didn't have to deal with? There was already a check with HR or the person in payroll in terms of onboarding these people. You didn't have to go and say, "Can you..." Because I was the same way, to be honest with you. I would find out when I was an admin, "Oh, so-and-so needs a Salesforce license," two days after they started when HR sent out the announcement of the new hires. And I was like, "Hey, there has to be some process that you onboard these people to the company. Can I be part of that?" And I kind of had to unwind HR and figure that out because they didn't know that Salesforce was a part of this department and they didn't know that people need to be onboarded for it. You sound like you didn't have to deal with any of that. Michelle Wolf: We did not. That onboarding process was already handled by a team. And so when the hiring manager said, "Yes, we're going to offer," and they accept, they already knew what systems, what equipment they need, what systems they need access to, and then what types of permissions they would need to ask for from Salesforce. So like what team they were going to, so that that request could be put in. All that hard legwork was already done. So to those who might not have that, I think the biggest selling point could be onboarding experience. A lot of companies are focusing on what that hiring process, what that onboarding experience is. And as someone's starting a new job, I want to prove myself early on. I want to say, "I'm here, I'm ready to work." And if I can't access my systems, even though it's fully out of my control, I still feel like I'm not doing my best as an employee, as a new employee. So you can leverage just even the onboarding experience that they have, the equipment they need, they have the logins that they need on day one, on the day that they need it. Mike: Yeah. And you don't have to go into detail, but what are the key, I guess I'll call them, milestones in your onboarding flow that the new people get sent? Do you have training materials, or do you have a video that's Michelle being like, "Hi, I'm your Salesforce administrator"? Michelle Wolf: If only. Mike: I know. I always say that and everybody's like, "Oh, that'd be a great idea." Michelle Wolf: It would be. It would be. Mike: "It's just 4,792 on my list of things to do." Michelle Wolf: Exactly. When I have that free minute, I will absolutely get to that next. Mike: Yeah. And also my other two admins, because it can't just be me. Michelle Wolf: Right. "Here's your Salesforce team. We're here to support you." Mike: Yep. Michelle Wolf: So what we built into our process was, in my Flow automation, there was actually a second autolaunched flow that would close out the case. And this did a couple of things. One, it closed out the case so they had a complete close of the loop and updated the reason as completed by automation because a human didn't have to touch any part of this request. Mike: Ooh, that's cool. Michelle Wolf: Yeah. Mike: I like that. Michelle Wolf: Clean reporting. Who doesn't like that? Mike: I mean, for a while, I remember doing approvals or something and somebody asked me, "Well, did you actually do this or did Salesforce, the Flow do it?" And I was like, "Well, the Flow did, but the Flow ran as me." Then it marks that. But I like that you added that completed with automation. Michelle Wolf: Yeah. But we also added two email actions. And one was to the requester. So the individual that opened the case through the screen flow, it sent them an email telling them that the request had been completed. And then the second thing was, when the user record was created, it then updated the Requested For field, which was just a custom field we made on the case for a user lookup with the new user that we'd made. And we sent a welcome email to them and said, "Welcome to Salesforce. Welcome to our company. Here's how you access our org." And it had the link for the SSO. Yeah. Mike: Because at the point that the person's creating the case for you to create the user, they've already had an email assigned to them. Michelle Wolf: Correct. Mike: I like it. That's pretty sweet. Michelle Wolf: Yeah. It was just a nice clean way to close multiple loops that ended up getting started. Mike: So then, not to dig into it, and this is where I wish I should have seen your presentation, do you also have a process for adding them to... I don't know if you guys have Slack or different things like that. How, outside of maybe that user emailing you, do they have not necessarily an open loop, but at least a channel to ping back the admins and say, "Oh, hey, I got everything except this doesn't work, or, "I'm not seeing X," or, "How do I upload a profile picture?"? Michelle Wolf: Yeah, absolutely. So for our new hires, basically all of that was handled in their new hire training, a lot of that initial setup support. However, in our screen flow, we actually made it a full-service utility where when you went to launch the screen flow, you could say, "I need help with Salesforce. Something's broken." Or, "I need a new user." So it was this full access path to us where they could put in multiple requests depending on what they needed. Mike: I like that. And I'm assuming it's not Michelle, but you have people in the organization that do training. How much do you have to keep them updated in terms of, "Here's what the new user experience is like for Salesforce"? Michelle Wolf: As far as? Mike: Just anything. Anything that would change or anything that they may encounter, new features. Michelle Wolf: Oh, yeah. So anytime we would build any type of enhancement, we worked very closely with our training department. We knew if we're going to help make starter material for an announcement for the call center for X, Y, Z enhancement, training's also going to need that material and probably a deep dive hands-on demo so that they can incorporate it into their training materials. So any new builds like that, our training department was really involved even from early-on stages of the development because they interact with new employees, and they see that interaction differently than someone who's been here for five, 10, 12 years and knows how we use our Salesforce. Even just how we design and where we put things on the Lightning page, they would often give us input from a new hire perspective to ensure that we're building good things. Mike: Now, just because we're nerdy here, did you have a way of capturing that? Was that a case as well? Michelle Wolf: That was just conversations. Mike: Oh, okay. Michelle Wolf: Yeah. It was, "Hey, we have this thing. We want a demo for you. Give us feedback," type of stuff. Mike: I didn't know if you were capturing that in terms of tech debt or things we need to build, things we'd like to build, and things we need more money to build. Michelle Wolf: Yeah, depending on what it was. It was just good old-fashioned scope creep. Mike: Okay. Yeah, that usually happens, unfortunately. Michelle Wolf: Yeah. Mike: I've talked about Flow and AgentForce. I've been around now. I remember from...
/episode/index/show/buttonclickadmin2/id/42332050
info_outline
Solving Sharing Mysteries with Setup with Agentforce
07/30/2026
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 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 Learn more Salesforce Admins Blog Post: Salesforce Admins Blog Post: Salesforce Admins Podcast Episode: Admin Trailblazers Group Social 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 with the read action. There is no particular sequence, I would say, but mostly how the sharing is defined is like first we have the OWD, which provides the base access to the records and to the objects. And then comes the role hierarchy, then comes sharing rules, then we have public groups and queue and we have the manual shares. So at each level, sharing opens up the door for more access. So if you're going below the hierarchy, sharing will provide more and more access to the user. And if you want to close that access, it's not easier that one sharing rule will open up the access and then you create another sharing rule to close the access. It's not how it works. So in that case, you need to spend a strategic amount of time thinking how you can revoke that access. And sharing is accumulation of the small, small, small decisions over the time. Sometimes adding someone to the group, for the reorg, you have to do lot of things with the sharing, and every decision gets compound. So I highly recommend our admins to at least spend 30 minutes a month to refresh and reanalyze their sharing configuration to avoid the future problem. So this is basically the flow looks like, but I would say there is any of sequencing which admins should follow. It's pretty much open and admin can ask any question to our agent. Mike Gerholdt: No, I think you're right. I mean, Setup with Agentforce can do a lot in terms of explaining the configuration and then help change it. I think you really touched on that last answer of just slowing down for a second, verifying what the answer is to make sure that you're staying in control. My question to you would be, how should an admin validate what the agent tells them? Nikita Kothari: Oh, that's a good question. So for the read action, the information, we have mostly the links added to our prompts. We call it as a clickable link. So if investigation is saying that Nikita is part of this group, actually, there is a link of that group. So you can go to that group by clicking on that link, and you can actually see I'm a part of that group if you want to re-verify the stuff. So, that will give you more confidence that you know how admin is investigating the information or if admin is saying, "Nikita is part of the sharing rule and you'll have the link for the sharing rule." So you can actually go and verify whether that sharing rule contains the group or the users where it is providing that access. And with the write action, I think more critical is the right action. I mean, you don't want somebody, AI is coming to your system and randomly making changes to your system. So to do that, we have the validation layers. The first validation we generally come up with is for every write action, we explicitly ask for the approval, approval from the person who is making the changes. And we also have the permission boundaries, and if particular user doesn't have the permission to edit OWD, the agent won't be able to edit OWD for that person. And then the last part is the accountability. Every change we are logging into the setup audit trail saying that whether the AI agent did it or actual person did it. And then admin can verify it, whatever changes is made by the AI agent are trustable or not. So we will always advise admin to go and do as much as possible testing on the sandbox before making changes into the production. And another backup system is the Einstein Trust layer. We always say trust is our number one priority. So, Salesforce has built trust everywhere to make sure that we are not blindly making any changes, and as this is a very, very critical domain to our customers. Mike Gerholdt: No, that's great. You talked a lot about sharing, and I always feel like making a change with sharing, you want to make sure that you're doing it right. In your opinion, what is the most important thing an admin should review before making a sharing change? Nikita Kothari: So I would say, as I said before, we have some of the steps that I also wrote in my blog, that we have OWD sharing rule, rule hierarchy, and everything opens up the more access. So to close that access, it's very difficult to go back and fix something. So, I would highly recommend whenever our admins are making the changes, try it out first thing on the sandbox if it is working as expected or not. Or have some verification system or another set of eyes whenever you create some rule hierarchy or you're providing some access to the rule, rather than giving access to all of the user, first try with the minimal set of the user. Try with the one user and see if that user are getting right access to the right record. Because even if you fail to provide a single user a wrong access, that means that you're leaking your data. So having those, another, just starting with a small and then going into the bigger and bigger data, that would really help admin to build the reliable system. Mike Gerholdt: Yeah, absolutely. I think it can do a lot and I've seen it do a lot, but what is something that Setup with Agentforce can help with today that maybe admins may not realize? Nikita Kothari: I feel like still adoption, it's tricky because people are quite a lot thinking that Setup with Agentforce will replace their job. But I would say rather than replacing, it will provide you a lot of capabilities and it will remove a lot of overhead from your day-to-day work life, rather than going and looking into the SQLs or doing everything by yourself, just give it a try. And then you can see how much opportunity it is opening up for you to save time. And that time you can actually use for building a more structural, and because structure mattered a lot when it comes for sharing. How your roles are getting access or how your groups are getting access. And if you're just blindly following the steps and not thinking much, then you are in a trouble. So you can spend more time and thinking about, how can you better make a structure for your organization? And you can get more time to think about your business. And I feel like most of the troubleshooting cases we have covered into the Setup with Agentforce flow. Yeah. Mike Gerholdt: Yeah. You mentioned a lot, admins should get out and use it and try it, and I'm a big proponent of that. So I'll end on this question. What for you is one kind of low risk question that an admin could ask Setup with Agentforce today to better understand their sharing configuration? Nikita Kothari: I think my one of the favorite action among all of it is record access, to ask why this person is having access to this record. And you see how much it can do, it will give you the whole list of the OWD configuration for that particular record, or it will look for the sharing role, it will look for the group membership, it will look for the manual shares. And it will do all kind of investigation for you just when you type a one single natural language to your agent. So you can always think about someone which is having more knowledge about the setup. It's sitting with you and helping you to deal with all of the setup configuration. Because setup, again, we have like 1,300 setup pages, which is lot. And going through all and learning the capabilities of each setup action, it's difficult. So, that's why we built the Setup with Agentforce, which will give you the capability that you don't have to learn everything on the go. And you can start asking question to our bot. If it won't be able to answer, it will guide you in the right direction to help and analyze your queries or your concerns. Mike Gerholdt: Yeah. I am so glad that we have Setup with Agentforce. I feel like I could have used it 20 years ago. I know I had a lot of questions and would have to dig through my notes on org-wide and sharing and group sharing and all kinds of that stuff. So, I appreciate it. And I appreciate the article and you taking time out of your day to talk to admins and share your knowledge about sharing and setup and how we can do things better. Nikita Kothari: Yeah. I think admins are always on the top of our list. I would love to hear from our admins how they like this Setup with Agentforce, specifically with the sharing, how it is helping them or what they are looking forward to, because I feel like most of our critical projects and best solution came up with the admin feedback. And we really want to make admin life easier. We always have meetings internally, our engineering team, our product is always so much focused about thinking about our admins, thinking about the newer way to introduce some more features to make their lives easier so that they can focus on building a reliable solution. So, it was great talking to you. Mike Gerholdt: Yeah, no, I'm glad you could share your knowledge with us today. Thanks so much. Nikita Kothari: Yeah, thank you so much. And one more thing, we will be at Dreamforce. Larry Sherrill is our Product Manager. They're having a lot to share at Dreamforce. So, feel free to stop at user access booth. I'll be there too, so come and say hi and share your feedback. We would love to hear back from you. And we keep making a lot of progress on Setup with Agentforce, so stay tuned, follow our blogs, and it will be something will be really helpful in future for you guys. Thank you so much. Mike Gerholdt: Thanks again to Nikita for helping us understand how Setup with Agentforce can make sharing investigations faster without taking judgment out of the Salesforce admin's hand. And the takeaway is just really simple, use AI to uncover the source of access, validate what it tells you, and test changes carefully before they reach production. Now, if you enjoyed this episode, and I bet you did, I hope you did, you should subscribe to the Salesforce Admins Podcast. Share this episode maybe with your team, fellow team, user group. Oh, I like that, if you'd share it with the user group, that would be awesome. And then, how about this? Start with one low risk question about your own org sharing configuration and ask that to Setup with Agentforce. Until next time, we'll see you in the cloud.
/episode/index/show/buttonclickadmin2/id/42257655
info_outline
Salesforce Superbadge Cohorts Build Skills Through Community
07/23/2026
Salesforce Superbadge Cohorts Build Skills Through Community
Today on the Salesforce Admins Podcast, we talk to Jean Velonis, Senior Technical Program Manager at Salesforce. Join us as we chat about the new Superbadge Cohort Learning pilot program and how you can get involved. You should for the full episode, but here are a few takeaways from our conversation with Jean Velonis. Improvements to Superbadges I have to confess, I’ve always found Superbadges to be a little intimidating. They're locked behind requirements, without clear step-by-step instructions for how to work towards them. That’s why I sat down with Jean Velonis, a Senior Technical Program Manager working to improve the Superbadge experience. The first thing Jean wants you to know is that they’ve overhauled the Superbadge UI. Instead of being locked behind a list of requirements, Superbadges now have a Recommended Learning section. These Trailhead modules and badges are organized into units, giving you a much clearer path to work towards your goal. What is the Superbadge Cohort Learning pilot program? In addition to the UI changes, Jean and her team are launching a new pilot program called Superbadge Cohort Learning. These sessions let you connect with other learners and subject matter experts to work towards a Superbadge together, guided by a facilitator. For now, the pilot program is focused on two of the most popular Superbadges. For admins, the Data Quality and Validation Superbadge gives you the knowledge you need to prep your org for AI. And if you’re a dev or looking to improve your coding skills, there will also be groups for the Apex Callouts Superbadge. They’re running both in-person and virtual versions of these sessions, so look out for them at a Dreamin’ event or community group near you. Volunteer as a subject matter expert or facilitator If you already have these Superbadges, Jean highly recommends volunteering as a subject matter expert or a facilitator. When you’re working with new learners, you’ll run into questions and situations that deepen your understanding of the topic more than you ever thought possible. The other thing about students is that they keep learning. Teaching is an incredible opportunity to make strong connections that will last throughout your career. As Jean explains, two of her former students are now her go-to people when she has code or Flow questions. Make sure to listen to the full episode for more from Jean about the Superbadge Cohort Learning pilot program. And make sure you’re subscribed to the Salesforce Admins Podcast to catch us in your feed every Thursday. Podcast swag Learn more Sign up to be a subject matter expert or facilitator: Salesforce 360 Blog Post: Admin Trailblazers Group Social Full Transcript Mike: This week on the Salesforce Admins Podcast, I'm joined by Jean Velonis to talk about the Superbadge Cohort Learning Pilot and what happens when admins stop learning alone and start solving problems together. We're going to dig into these cohorts and how they bring experts, beginners, and everyone together in the same room to work through real challenges, build confidence, and get comfortable being uncomfortable. Because for Salesforce admins, knowing how to troubleshoot, test, fail safely, and ask better questions matters just as much as knowing where to click. And as AI and agents become part of everyday platform work, well, those fundamental skills help admins validate what is correct, keep data reliable, and make sure that the platform reflects what the business actually needs. So listen in, subscribe and share this episode with an admin who learns best by rolling up their sleeves and figuring it out. Let's get Jean on the podcast. So Jean, welcome to the podcast. Jean Velonis: Thank you so much for having me. I think this is the second time I've been here, but it's been a while. Mike: I know. Well, when you do the podcast for almost 14 years now, I try not to have guests back, only if they're important like yourself. Jean Velonis: Ooh, thank you. Mike: We were Salesforce MVPs together a hundred years ago when the internet was still tubes and wires, and now we're both at Salesforce. And you're on, I would call, what, the curriculum side, the learning side? Jean Velonis: Yeah, I would categorize that. It's more Trailhead, right? So long story short, certification was my jam for so long, and superbadges were part of that. But over the last couple of years, we've decoupled from certification. We're still with Trailhead and we're still considered an assessment, but we don't have all the guardrails of certification on us anymore, which is really exciting. Mike: Gotcha. And just for reference, if anybody thinks they might have met Jean at a Dreaming event or a Salesforce event, you tend to usually have purple hair and a bedazzled Ranger hat. Is that an accurate description? Jean Velonis: These are facts. These are facts. I've had purple hair probably since six months of coming into Salesforce. And if anybody knows the famous Chris Duarte out there, she taught me everything I know about bedazzling. So I made a Ranger hat. Mike: Yeah. A lot of people bedazzle now because of her. Jean Velonis: Yes. Mike: Well, let's talk about this new Superbadge cohort learning pilot that you've kicked off because I think you're trying to bring the best of both worlds together. Jean Velonis: Absolutely. This isn't a new concept either. I'll just throw that out there. We had some amazing trailblazers before the pandemic and even through the pandemic doing Salesforce Saturdays or Salesforce Sundays and they would get together in person or virtually and work on Trailhead. So this is kind of piggybacking off that concept and really bringing some of the community magic to superbadges because I think we can all look at a superbadge and be like, oh, that's kind of intimidating. There's no step-by-step instructions. This looks really hard. There's multiple steps to it, and that just looks hard and I don't want to do it. But the cohort learning brings a facilitator, like a community group leader or a Dreamin event person to come in and help bring people together virtually or in person and work on a Superbadge together. And we've been running a couple of pilots of these. We did one at TDX and WITness Success in Indi. And it's been really successful in person just because you can pair experts and newbies together at a table and make people really uncomfortable, and then they start talking to each other and learning from each other. And I think that's what gets really excited about doing this cohort learning. And then we've done a couple of virtual events as well where we've brought community group leaders, kind of like train the trainer of like, here's how you should run this virtually to be successful, because that virtual is a little bit different beast. It's really easy to hide and stay on mute and turn your camera off where we really try and get people excited to share their skillset with each other. Mike: Yeah. No hiding in the dark corners. So I really like the idea of this. I've always really enjoyed Trailhead because I'm the type of learner that likes to do it at my own pace. Sometimes I even crazily go back and redo a badge just because I feel like if I've rushed through it, did I really learn it or was I just trying to get it done? And when I'm really trying to learn it, I really take my time. I will agree with you, I've written superbadges. I also enjoy the freedom. They're kind of like, "Here, go, do. " And you're like, "Oh yes." It's almost like the days of driver's ed when you get out from behind the desk and you finally get to drive the car in the real world. It's a little more of trying things out. So are these cohorts that you're doing now, are they open to any superbadge or are they just specific ones? Jean Velonis: That's a really good question. We looked at our whole library of Superbadges and we wanted to pick one for admins and one for developers. And that doesn't mean it's just if you have that skill set. It's more of like, here's two of the main roles we see in the community. So we have data quality and validation, which is really for anybody prepping you for this agentic ecosystem that we're in, cleaning up your org. Mike: I mean, to be honest with you, that's what we've needed to do this whole time. Even before AI, it's sweeping the floors, you know? Jean Velonis: Yeah. I mean, it's been that way for a long time. I think I made my whole Salesforce admin career of going in and cleaning up orgs, to be honest. So that was a great place for us to start. And then now we've started looking at the developer side of it and we picked Apex Callouts superbadge for all of our developers. And I was very intimidated by trying to put together a superbadge in a box for that cohort because I'm not a developer. But going through this process, I'm like, "You know what? I think I can actually do this," And that's because of all the great learning badges on Trailhead and being able to go at your own pace. Because that's a whole nother skill set for an admin to try and figure out, right? Mike: Right. I've often thought of, this is just how Mike's brain works. If I had children, I would for sure name one of them Apex because then you just gave them a shout-out. Jean Velonis: That's hilarious. I would've never thought- Mike: That's how I work. My brain today is like, "Oh yeah. Hey, did you hear you were mentioned on a Salesforce podcast?" "Of course I was. I'm an Apex Callout." Jean Velonis: I'll tell you a weird secret. I do put my children's names in superbadge content. All of us over here under the superbadge team put little- Mike: Easter eggs? Jean Velonis: Easter eggs, yeah- Mike: Yeah, I love it. Jean Velonis: ... out there. It's either in the org or it's in the content. We're all moms over here, so we would like to give our kids a shout-out. Mike: Well, I will see your Easter egg and I will call your Easter egg. In almost every admin keynote demo, we have put our pets' names. Jean Velonis: I love that. Mike: So you can go back and figure out whose pets were whom. The only time, the only exception was we had Einstein Voice rollout and my dog's name was yet to be used and we couldn't use it because it wouldn't recognize it. It was too hard to say. And so we had to go with something easy and punchy with hard consonants in it. So anyway, yes. I think there should be, I'm sure there is somewhere, a whole forum of Easter eggs found in Trailhead material. Jean Velonis: 100%. And I think that's what Trailhead is, where it's the weird, it's the hanging out, it's the learning something new, it's the being uncomfortable. Because it really is, learning can be really uncomfortable. Mike: I mean, it exposes a weakness and people don't like feeling weak. It's also the thing I always think about whenever I was doing training because you're changing something. And the person that told me how to do training gave me a very well-rounded, concise piece of advice, which is people don't like to go to work and feel stupid. And when you change something, even in a CRM, that's what that comes from. And people don't like to feel stupid. And I feel that way. You change something, you're like, "Oh, this was here yesterday. Why isn't it here?" And you blame yourself and that's not the point. You do a lot of training. So let's go through just some scenarios of I'm a new Salesforce admin. I stumbled across this podcast. Also, hello. You have a lot of episodes to catch up on. That's okay. You have a lot of time. What should they do to prepare to come to one of these learning cohorts? Jean Velonis: I mean, the easy answer is get on Trailhead and start earning badges, that's number one. Step two is take a look at the new look and feel for superbadges and that will bring you to our recommended learning. It used to be required to unlock the superbadge, but we've just now come onto what I would say the Trailhead UI. Superbadges are put into these units now where the first unit is like, let's get ready. Let's get your developer org. Let's do the recommended learning. Let's connect it to your superbadge now. That's all a little bit different than what we used to do with superbadges. You had to unlock it and then you had to go down all the way to the bottom of the page to hook up your org. Now it looks like a regular module or badge, which is nice because as somebody who struggles with reading and keeping my place on Trailhead, this new guy is really going to help with that. But also doing the recommended learning I think is key even though it's unlocked now and you don't have to do it. I will tell you I am the first person to start doing something and being like, "Oh, I have no idea what I'm doing with this. Maybe I should have done-" Mike: I should have done those recommended modules. Jean Velonis: Yes. And then I will have to go back and learn and figure things out. I did that with the prompt template superbadge. I thought I knew what I was doing. Mike: No. Jean Velonis: I did not. And that's falling, that's failing forward. That's realizing I don't know what I'm doing. Let me go figure this out and then come back to it. So I think that's step number two. Go and read through the superbadges, look at them, look at the recommended learning. And then if you see that there is a Dreamin event or a community group doing one of these superbadges, join them. Even if you've done the superbadge, that's okay. You can go help the other people that are there. Mike: Oh, I almost think that would be the next best thing after doing a superbadge is going and volunteering to help train. Because never will you ever learn more about something than when you have to train somebody about something or walk around the room and answer questions. You're like, "Hey, I didn't run into that when I was doing mine, but let's figure it out." And it's super fun because then you're like, "This wasn't a problem for me, but now it's a problem that I get to work through." Jean Velonis: Yeah. I mean, bringing you all the way back to SABWA. Mike: Oh, sure. Jean Velonis: Call out, Mike. I mean, geez. Yeah, that is my favorite thing to walk around, especially I live in these superbadges every day. Our team builds them. We maintain them. We have to deal with all the product changes that are very quickly changing and trying to keep up with everything. So being able to walk around the room and see how trailblazers are doing things, that not only helps me figure out, okay, here's some of the common pitfalls or where people are getting stuck and I can write some hints to help, but also maybe we don't do that in the next superbadge or maybe we call it out in a different way or let's go update the help article and call this piece out if somebody's getting stuck somewhere. So it's super helpful. But also you get to meet a ton of different people, which we do virtually every day, but it's easy to hide behind the keyboard again. And to be able to connect with somebody and see their aha moment of where they're like, "Yes, I figured this out," that's super gratifying. Mike: Oh, that's almost the time that you make a friend. Jean Velonis: A best friend. Mike: Yeah. I mean, because you're always going to be like, "Well, let's continue chatting while you work through this." And then the next thing you know, they're building Apex Callouts, and you're like, "Oh, I didn't get that far." And then they're teaching you stuff. I promise you it'll happen. Jean Velonis: It will happen. I can say 100% certainty it will happen. I have two people that I call on all the time or that I met through a conference or doing something, and I'm like, "Okay, I know this person knows code and I know this person knows flow. I'm not good at those things, but I can text or call or Slack and be like, I'm stuck." Mike: Right. So I mean, I have a thousand questions, but let's go to the opposite end of that where if you're a community member, maybe you're a user group leader or a Dreamin event person and you're like, "This sounds like a super fun thing for me to include in my agenda," What would their steps be for possibly including, I know it's in a pilot, but for including this or what's your vision for it moving forward? Jean Velonis: Yeah. We have a facilitator signup forum- Mike: Sweet. Jean Velonis: ... which I'm sure you would be happy to put that in the bio or the show notes. Mike: It is in the show notes as we speak. Jean Velonis: Perfect. But yeah, just signing up to raise your hand to be a facilitator is huge. Because I'm going to have this superbadge in a box ready very quickly for people to take to a pilot. I have two Dreamin events that are already wanting to do this in August and a community group that also wants to bring it to their local people. So signing up to be a facilitator and doing this on your own, love that. And I wish I could go to every one of them, to be honest. I looked at a couple of them and I'm like, "I might be able to make this work and just show up." But there's also a piece in that form too to sign up to be a subject matter expert and help if there's somebody locally that wants to do this. And selfishly, I put that in there that if you want to help us build superbadges, that would be awesome too. Mike: Right. And this sounds rhetorical, but it is honest. They should have probably already completed that superbadge that they want to facilitate or host. Jean Velonis: I mean, I'd advise it. And with the new UI, you can redo a superbadge. You can retake it now. So you can do the superbadge over. Mike: To refresher, because maybe you haven't done it in a while and want to see what's new. Jean Velonis: I mean, the facilitator that did WITness Success told me she still had her notes when she originally did the Apex Callouts in 2017. Mike: Wow. Jean Velonis: Right? Mike: I probably have notes from somewhere of 2017 I have nowhere. That's awesome. Jean Velonis: No, that notebook's gone. Mike: Yeah. I always think of admins listening to this and I don't want it to be a pitch session for your cohort, but this is really a neat way to get involved with the community. From all of your work, and this is just stepping out of your role and what you're doing in this superbadge cohort. Out of all of the work that you've done at Salesforce and what you create for Trailhead, what are some of the biggest themes that you run into that really, when that light bulb turns on for an admin, they suddenly just become, I don't want to say instantly become successful, but they really start to click and feel confidence and have that aha moment? Jean Velonis: I think being a Salesforce admin for such a long time, being able to fail and problem solve is probably the best skill you can have. You can learn any technical skill. I can go into a dev org and break things and figure out how products work. But if you don't know how to problem solve through something, getting to that aha moment is going to take you a long time if you're too afraid to break something. And I have broken things. And I think I've told you, I've deleted records from an org before and went, "Uh-oh, how do I get those back?" So that is one of my favorite things is to go into a playground or dev org and just break it, pull things apart, see how it works and be like, "Okay, I know where I want to go, but how do I get there? And I don't know how to get there, but if I go in and break everything, I'm going to learn a lot more than if I follow step-by-step instructions of how to do something." Mike: Right. If it works out perfect the first time. Jean Velonis: Yeah. What did you learn? Oh, I know how to do that. Okay. Well, what's next then? Mike: Do you find that you have to remind people that it's okay to fail when building and it's okay for things to not work the way you want them to the first time? Jean Velonis: Yeah. And I mean, that's how we build superbadges. I mean,...
/episode/index/show/buttonclickadmin2/id/42185255
info_outline
How Can Admins Reduce MFA Friction in Salesforce?
07/16/2026
How Can Admins Reduce MFA Friction in Salesforce?
Today on the Salesforce Admins Podcast, we talk to Jay Hurst, Senior Vice President of Product Management, and James Ferguson, Senior Director of Product Management, at Salesforce. Join us as we chat about MFA step-up authentication and what it means for Salesforce Admins. You should for the full episode, but here are a few takeaways from our conversation with Jay Hurst and James Ferguson. Step-up authentication protects sensitive actions Starting next week, Salesforce is requiring all users to use Multi-Factor Authentication (MFA). If you’re a privileged user like, for example, an admin, you’ll need to use a phishing-resistant MFA. That’s why I sat down with Jay Hurst, VP of Product Management, and James Ferguson, Senior Director of Product Management, to talk about why these changes are vital to protect your org’s data. The first thing to know is that AI is making it easier than ever to launch targeted phishing attacks at scale. So while the MFA requirements provide a good first layer of protection, we want to make extra sure you are who you say you are before you’re allowed to perform certain actions, like downloading a large number of records or running a big report. Phishing-resistant MFA uses a passkey, like a fingerprint or facial recognition biometric, to verify that it’s actually you and not just someone with access to your email account. Balancing security with user friction As Jay and James acknowledge, these changes will add some friction to your users’ experience. However, with the pace at which these kinds of attacks are evolving, it’s more important than ever to get serious about your security posture. “We're trying to introduce a little more friction right now so that people start to think,” Jay explains, “and start to build those habits of understanding when they're doing something that potentially could be considered a malicious attack, such as downloading that All Opportunities report.” They’re also building out compensating controls that should make things easier in the future, allowing you to trust users from a certain IP range, for example. Security is a journey, not a destination The most important thing to realize is that these requirements are about more than just jumping through some extra hoops. Phishing and man-in-the-middle attacks are growing more and more sophisticated, and you need better protections than “Well, that hasn’t happened yet.” Instead, James and Jay recommend viewing this as an opportunity to partner with other stakeholders in your org to develop a comprehensive security plan. As Jay says, “Security is a journey, not a destination. What is 100% secure today is not as secure tomorrow.” The trick is to develop a security-focused mindset throughout your business that will protect you now and in the future. Make sure to listen to my full conversation with Jay and James for more on step-up authentication and how admins can reduce friction for users. And make sure you’re subscribed to the Salesforce Admins Podcast so you never miss an episode. Podcast swag Learn more Salesforce Admins Podcast Episode: Salesforce Admins Blog Post: Salesforce Help Article: Salesforce Help Article: Salesforce Help Article: Salesforce Help Article: Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins Podcast, we're talking with Jay Hurst and James Ferguson from Salesforce Product Management about MFA step-up authentication and what it means for Salesforce admins. As you know, security isn't just a front-door login decision anymore. It's about protecting sensitive actions, understanding risk, and designing systems users can trust. So Jay and James are going to help us unpack phishing-resistant MFA, compensating controls, IP ranges, SSO, and why these changes matter in a world where data, automation and AI are all working together. For us Salesforce admins, this is a chance to think beyond features and really look at how we steward the entire system. So listen in, click that Subscribe button, and of course I would love if you could share it with fellow Salesforce admins or, hey, you know what? Let's make some friends in that security team. So with that, let's get Jay and James on the podcast. So Jay and James, welcome to the podcast. Jay Hurst: Thanks for having us, Mike. James Ferguson: Great to be here. Mike: Absolutely. Jay, let's start off with you. We kind of want to get to know a little bit about you, and James, we'll call on you second, but before we get into our topic today, can you just tell me a little bit about how you got to Salesforce and what you do? Jay Hurst: Sure, yeah. So I have been with Salesforce for almost 22 years now. I started in our customer support department, one of the first 12 phone support reps here at Salesforce. Did that for a couple years and helped found our Tier 3 organization in support. Eventually moved over to our customer-centric engineering department, stayed in there for a while. And then in 2012, had an opportunity to join the product management group for platform, and I moved over and ran a team called Force.com Canvas. And for the last, I guess, 12-ish years now, I've been kind of weaving my way upwards through platform. Currently, I lead our platform services subcloud, so all of the core foundational pieces of platform that you might think of are schema and metadata, APIs, eventing systems, connectivity systems, and also our identity area, which is what brings us here today to talk about MFA. Mike: Yeah. Boy, flashback. You called it the Force.com platform. Jay Hurst: Well, that's what it was called back then. Mike: I know. I know. Jay Hurst: And I can't remember all of the names we've had for it. Mike: Oh, that's okay. I'm sure there's a website that tracks all of them. Jay Hurst: I'm sure there is. Mike: James, fill us in. How'd you get to Salesforce, and what do you do here? James Ferguson: Well, I am, I guess compared to Jay, one of the newer members of the team. I've only been at Salesforce for about 16 and a half years, almost 17 years. Pretty much entirely on the platform product management side, working on various things people know and love like sharing and big objects and event monitoring and those things. And most recently I've taken over responsibility for the identity product team, responsible for all the login and auth and SSO and all of the wonderful things we'll talk about today. Mike: Oh, wow. Okay. So then just to be clear, I'm actually the newest person on this call. I've only been at Salesforce for a little over 12 years now, so I guess I still have my rookie stripes. Jay Hurst: Combined we're almost at 40, or just over 40. Mike: Yeah, combined. We almost get our AARP discount, right? Jay Hurst: Yeah, exactly. Mike: Jay, let's kick off. I know I did a podcast ... and I'll link back to it ... not that long ago with Laura Pelke talking about some of the new things that were coming out, and of course security is always big on admins' mind. She did a wonderful job of explaining step-up authentication to me, which was basically the airport analogy of you have to show your ID to get in and then you have to show your boarding pass to get onto the plane. I thought that really made sense to me, but let's talk about the new authentication that's coming out, if you call it that, and the new step-up concerns that Salesforce admins have. Jay Hurst: Sure. So I think as we move into the continued proliferation of agents and AI across the industry, security is obviously top of mind for a lot of our customers and for Salesforce as well, specifically because we have to help protect our customers. And so when we're thinking of that and how we ensure our customers' data is protected, with step-up authentication, it's really focused around in that same analogy, making sure you're providing your boarding pass at the right times when you're doing things. So just like you need to show your boarding pass when you go through the TSA gate and when you're on the plane and probably to the gate agent after you're on the plane, when you're doing certain things within Salesforce, we want to make sure you are who you actually are and your session hasn't been compromised. So when you're doing certain higher sensitivity-type actions such as I want to download 10,000 records out of my system, maybe run a report, putting that end user through another verification of, "Hey, is this actually you? Prove it with your step-up," so that we have that confidence that we can release the records. And so this kind of helps prevent some of those man-in-the-middle phishing attacks where somebody gets you to log in and then steals your credentials or steals your session in the background. So it's kind of that second or third or fourth level of protection in the runtime. Mike: Wow. James Ferguson: I think that's an important shift that's worth calling out, because it's no longer about just putting a stronger lock on the front door and making sure somebody has better passwords, or even the later stuff, the more recent stuff with verification. But it's when sensitive things happen, we need to do a little extra even once you're inside the airport, if we want to continue that analogy. And so it's a shift from that front door to moving forward. Mike: Yeah. James, help me understand that a little bit more, because I think one of the things that admins always fight is user friction. How hard is it to do something? And now we're introducing something when it could disrupt their flow of work, but it's for a good reason. James Ferguson: Exactly. I would say that we are constantly balancing that. We're constantly balancing the need for security with the friction it does. And so we aren't expecting to do every click, for example, but just when you're exporting data from a report, which is potentially pulling a large amount of data out, we want to make extra sure. We're looking at some other things in the future around maybe when you're an admin changing some security configurations, we want to make sure you are who you are. And frankly, you see this more and more even in consumer websites where sometimes you're asked. If you're going to change a phone number, change a thing, you need to go back and sort of double-proof who you are. But it is a trade-off. It is a trade-off. Mike: Yeah. It's like once you're logged in, it's, "Oh, if you're going to change." I was trying to order tacos the other day through an app and I needed to update my credit card. And then right after I did that, they're like, "And you need to put your password back in." I'm assuming that was kind of the same situation. James Ferguson: Kind of the same situation. Jay Hurst: Yeah, exactly. Exactly. Yeah. And the other thing I'll add to this too is on the friction point. We always have to balance that. Like James said, we don't want people to become overly frustrated and not want to use Salesforce because it has too much friction. But the reality is over the last 20 years, we've edged so far on the line of not causing any friction that we've led admins down the path of not having that understanding of what their users are doing, and really not getting into that proper security-conscious mode. So we're trying to rubber band a little bit back on the other side, introduce a little more friction right now, so that people start to think and start to build those habits of understanding when they're doing something that potentially could be considered a malicious attack, such as downloading that all-opportunities report. So starting to get customers to think through that while we are continuing to build out what we call compensating control. So the end goal here is not to provide friction and it's not to force you to do these one-time passwords for everything you need to do in the system. It's to give admins that layered capability of saying, "Well, if I have these five or six different controls I can put into place, then they can kind of compensate for one another." So where the most friction might be having to open up your email to get that one-time password to do the step-up, maybe we can compensate that through things like having a trusted IP range or already having a phishing-resistant authentication put in, or other controls that we will layer in. So we ultimately get to a posture where the admin can both reduce friction while choosing the proper set of controls for their needs. Mike: Yeah. No, that makes sense. You mentioned phishing-resistant MFA. Can you help me explain that if somebody's never heard that before? Jay Hurst: Yeah. So maybe I'm going to try and wiggle this airport analogy in. If we think way back in the day when you had your IDs, before REAL IDs and all of this, you didn't actually have good authentication on them. You might have a really bad picture, or in some cases IDs didn't have any pictures on them. They just had your name and your information, but they were accepted. Now, the problem with that is anybody could steal it if it doesn't have your picture, and they can pretend to be you. So phishing-resistant MFA is kind of that same thing. Where a normal MFA might be a one-time password on your phone where you get that push notification that says, "Hey, your code is 123456, enter that code in," that's great because it means you have to have your phone in order to get that one-time password, but it's not as secure because it's sent over SMS. It doesn't really verify that you are who you say you are. It's only that you have access to that phone. Phishing-resistant adds another layer on top of that, so it's not just over SMS or in an app. It would be through what are called passkeys or other more cryptographically secure passes. So think of your face ID, your touch ID, some of those passkey-type implementations that you might see, where it's not just getting a code, but you have to unlock a vault that has your information in it and then you provide that information out. So it's taking it from that ID that anybody can use if they just happen to steal your wallet into more of a REAL ID that also has some biometrics attached to it. So you can actually guarantee it's not just that you have the thing, but you have the thing and you are the person that should have the thing that identifies you. And so that's what we're implementing today that's starting to roll out tomorrow in production. We've already started pushing it into sandbox for admins where we want all of our administrative users across the system to enroll and use these phishing-resistant MFA capabilities, so that they're more secure. Mike: Yeah. I never even thought of that. All the time there's apps I log into and they send me a one-time passcode and I'm like, "Well, of course I have access to it." Never did I think that, "Oh, what if somebody already has access to my email, requests that code, and now they're essentially spoofing me?" And it never dawned on me until you think of, well, they're not really verifying that it's you, Mike. They're just verifying that whoever requested that code also has access to your inbox. And you're like, "Oh." Jay Hurst: Exactly. And that may not be a nice person. Mike: Right. So James, what are some questions that admins are asking online that we can kind of help answer for them, or equip them for when they get this rolled out to them? James Ferguson: They're certainly asking questions about phishing-resistant MFA versus regular MFA and the different sort of authenticators that are out there. I'll shift this around a bit. One of the things they aren't asking about, it's actually something that Jay mentioned in passing, which is the alternate controls. And for things like step-up, if you have login IP ranges on the org or on the user profile, or there's some session settings which force you to always be coming from the same IP address in your session, which is the case for most of us who are at a laptop at work or whatever it is. Those avoid step-up entirely because we have more certainty about who you are and where you're coming from. If your session's bouncing between Eastern Europe and Middle East and North Carolina and keeps hopping around, we start worrying more. So you can do some things around IP ranges, which takes that friction away from the user altogether, and so those are some of the things that I would encourage admins to look into. Now, sometimes it doesn't work because of mobile providers or other network infrastructure, but it's also potentially a low-calorie way of really sort of avoiding at least the step-up part. They'll still have the MFA requirements. Jay Hurst: And one thing I'll add to that. When we add these types of controls to ... admins are human like the rest of us and we always want to make it as frictionless and easy as possible, but we don't want to trade off the security for it. So IP ranges specifically have been a little bit of our bane for the last six months, because we have a lot of customers who have said, "Well, I will just put in the entire internet range of IPs and go 000 to 255, 255, 255, 255. And then no matter where I'm coming from, I'm not going to get challenged and it's going to be great." And that works, or worked, but it's not secure. And so we don't want to trade off security for just checking the boxes. There are reasons for us doing this. Now, with that one specifically, we have put in changes in place where we won't let you use such a broad internet range to get around it in that respect, where you actually have to put though into like, "Well, what is the internet range that I'm actually coming from and using?" And we have some friction still with that, I would say, with admins using very global deployments or salespeople that travel around a lot and using different VPNs. So we're working through that as one of those compensating controls rather than the primary control. But again, it is up to all of our admins to really think through. We don't want you to just do the check the boxes that we're telling you to check because we want you to check a box. We really want you to think about these changes and what it means to your organization, why we're actually trying to implement these, and ultimately determine what makes the most sense for you and your company. And include your security officers and your CISOs to really validate what meets the requirements that your company has, so that everybody is protected both from a security perspective and ultimately a legal perspective as well. Mike: Yeah. No, absolutely. I mean, we did a security day at TDX, our team did, and we had a CISO in there and a Salesforce admin as one of the kind of breakout topics, and they were in lockstep with each other, and I've always said that. I remember the instance I was managing, once it grew beyond 10 users, I was like, "I really need to figure out what our security posture is and who's in charge of this, who sets password complexities," at the time and stuff like that, and it's not adversarial. It's you want to be in alignment with what the rest of the company's doing and also fall in line if there's a SSO requirement. Boy, I was quick to jump on that, because it also made logging in simpler for my users. Jay Hurst: 100%, and that's the other side of this. All of these things do play with SSO. If you have implemented SSO that has phishing-resistant capabilities already built into it, great. We will take advantage of that from the Salesforce side. We'll trust your provider. We'll trust that your security team has already set up what is needed for your company and we'll let you log in. So we don't want to add these additional duplicative type of controls for you, but we also recognize that a lot of our customers, maybe they're smaller customers, maybe they're not the enterprise size of Salesforce and don't have as structured of a security posture. So in those cases,...
/episode/index/show/buttonclickadmin2/id/42105830
info_outline
How MuleSoft Helps Salesforce Admins Build Better Agents
07/09/2026
How MuleSoft Helps Salesforce Admins Build Better Agents
Today on the Salesforce Admins Podcast, we talk to Mofeyi Oluwalana, Director of Product Management at Salesforce. Join us as we chat about MuleSoft, Flow, Agentforce, and what happens when agents need to take action beyond Salesforce. You should for the full episode, but here are a few takeaways from our conversation with Mofeyi Oluwalana. MuleSoft creates agent-friendly business processes Agentforce can be truly transformative for our business processes, but sometimes it’s easier said than done—especially when multiple platforms are involved. That’s why I sat down with Mofeyi Oluwalana, Director of Product Management for MuleSoft. As Mofeyi explains, a problem many businesses run into when they’re trying to implement AI is how to enable an agent to engage with something like a process that starts on a payment platform, goes through an OMS, and then ends up with a request to a warehouse for shipping. You can’t just hand them the APIs and expect them to figure out the rest. That’s where MuleSoft comes in. It gives you the building blocks you need to codify your workflows into something an agent can understand. Data mapping for real-time app integration Building an agent-friendly business process begins with data mapping. What do you need and where is it located? You also need to understand the triggers that kick off each part of the process. Does it start with a Slack message, or when an order is created? Often, these types of business processes don’t start in the Salesforce ecosystem. MuleSoft allows you to translate these business requirements into APIs that an agent can use to take action. How to present to stakeholders As a product manager, Mofeyi frequently gives presentations to stakeholders, so I wanted to know if she had any advice for admins. “The most important thing when I walk into any room, regardless of the stakeholder, is who are they and what do they care about? Your ability to persuade and influence is largely due to your understanding of the three things that the people that you're talking to care about and how you align what you're talking about with those three things,” she says. Make sure to listen to my full conversation with Mofeyi for more about MuleSoft and mapping your business processes. And don’t forget to subscribe to the Salesforce Admins Podcast for a new episode every Thursday. Podcast swag Learn more Salesforce Admins Blog Post: Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins podcast, we're joined by Mofeyi Oluwalana, product management director at Salesforce to talk about MuleSoft, Flow, Agentforce, and what happens when agents need to take action beyond Salesforce. Now, for Salesforce admins, this conversation matters because agents are only as useful as the data, the actions, the permissions, and the business logic they can safely reach. So Mofeyi's going to explain to us why integrations are not just about moving data from one system to another. They're about helping Salesforce connect to the real processes your business depends on. We'll talk about the questions that admins should ask when working with other platform owners, how to think about triggers and data mapping and why business context is so important when you're designing actions for humans and agents. So give this episode a listen, subscribe wherever you get your podcasts, share it with another Salesforce admin who's maybe thinking about how Salesforce could connect to the rest of their business. And with that, let's get Mofeyi on the podcast. So Mofeyi, welcome to the podcast. Mofeyi Oluwalana: Thank you so much. Mike: I'm excited. We don't do a whole lot of episodes outside a core platform. And I know my Salesforce admins ... My ... The Salesforce admins of the world work everywhere and especially now with Agentforce and agents and really just the whole bringing people together and giving a complete view of data, integrating data and working with MuleSoft and tools like that are super important. So I'm glad to have you on. I'm glad we got connected, but let's start off and learn a little bit about you. What was your path to Salesforce and becoming a product management director? Mofeyi Oluwalana: Yes. So I started at Salesforce a little over four years ago. I actually came through the APM program, also known as the Associate Product Manager Program. It's a two-year rotational program for folks coming out of university, getting their start in product. So I was able to come in through that program. I did three rotations all across Salesforce. I spent some time in Commerce Cloud working on how to run promotions on Black Friday. Mike: Oh, holy cow. Mofeyi Oluwalana: And I spent a lot of time in experience services, thinking about how we can make it easier for marketers to build nice looking emails. And I ultimately landed in MuleSoft, which is where I continued working with the MuleSoft team on how to make it easier for our customers to connect the systems that they need to, both for traditional use cases, but also for the agentic ones as well. Mike: Yeah. It's funny, for the longest time in my career, I worked retail and the day after Thanksgiving, Black Friday was always the busiest day. And then I got into tech and I was like, "I don't have to work Black Friday." Mofeyi Oluwalana: Guess what? [inaudible 00:03:17]. Mike: And then realized that like, "Oh man, I was a retail associate. There's still computers that have to be had." So I have a soft spot in my heart for all of the people that on Black Friday have to sweat it out and make sure that servers don't go down so that checks and barcodes and everything can happen on the other end. Mofeyi Oluwalana: Yeah. I never realized how complex it could mean to calculate hundreds of thousands of carts when there were promotions running on Black Friday, but certainly it's more complicated than one may think. Mike: Right. And then there's people like me that add stuff to a cart and I'll come back to it a little bit later like, no, there's somebody ... You're using up the last bit of ... I don't know. He probably doesn't know that. And then I'm also old school retail when you used to have to verify checks and put them through little check readers and now everything's a credit card or a tap or thumbprint. Mofeyi Oluwalana: All of the above. Mike: All of the above. But it's all of the above because we're integrating data and we're doing stuff with MuleSoft. So I threw together some questions, but let's start off with where should admin start when thinking about products like Flow and MuleSoft and Agentforce together? Mofeyi Oluwalana: Yeah. The journey with MuleSoft starts the moment that your agent wants to do anything outside of Salesforce. I think MuleSoft is the connector, so to speak. If you have data that your agents need to reach in your ERP, if you have actions your agents need to be able to take with your payment provider, how exactly will they be able to do that? Now when agents and agentic technology became a thing, a lot of people were of this opinion that, well, agents are smart enough to just understand platform APIs or where agents can read the specifications, figure out the commands that they need to execute and do all the things that they need to do to be successful. We very quickly realized that agents are really smart, but at the end of the day, they're limited by the information that they know and the tools that they have access to. So it's not sufficient to just give your agents a platform API spec. That's not going to cut it. Your agents need integrations and APIs that they can directly invoke that map to your business logic. They need this because not every organization operates the same. For one retail provider, creating an order is very different from other retail providers. And understanding that business vocabulary is really important when building agents that actually bring value. And that's really where MuleSoft and Flow come into the picture. You have actions that your agency to be able to take in order to execute a certain business process. Well, that action is really just an API and we serve those APIs so your agents are able to do those things. Mike: Yeah. I've always thought of Josh who's on my team keeps us in check with helping us understand stuff. And what you just described would be like as if you brought somebody new on and said, "Well, here's a phone and a phone book. And if you have problems, the phone number's in the phone book." And the agent's the same way. If you're just saying, "Here's all the specs and the APIs you can call, go figure it out." It's almost like handing them this giant phone book and just saying, "Well, you're smart. You'll figure it out." Mofeyi Oluwalana: Yeah. Exactly. And the thing is that for a retailer, creating an order may not just be creating that order record. Creating an order may be, oh, I create the order record and then I send a notification out via email that says, "Hey, this is your order." And then after that, I create an invoice. There are a number of steps that happen. And how do you codify those steps? Well, it's not enough to just give an agent, again, the phone book and the numbers. It's much better and much more reliable to give them the actual workflow or the API they can use to execute that entire process. Mike: Yeah. Now, one thing that I've run into, so back when I was doing some integrations as an admin, we had different third party tools that were being used. One thing that I didn't know to ask ... And I'm hoping you can help Salesforce admins like, here's the questions you need to ask. We had an instance and we need to connect it to our financial backend, which ran not on Salesforce. I had to find the owner of that, which I didn't know existed. The other thing I didn't know to ask was I didn't know what to ask. And so as we work through different scenarios, you brought up like, well, they want to take the cart and order the stuff. The orders could be fulfilled in a different system. There could be a warehouse system. What are some of the questions that when the admin's sitting down with a business owner and they're saying, "Here's what I want in Salesforce and I'd really like to be able to pull up the orders." And the admin's like, "Okay, now I need MuleSoft because I need to integrate another system and I got to go talk to that systems' owner." What are some of the questions they should ask and what is some of the information they need to provide so that they can start setting up that relationship? Mofeyi Oluwalana: Yeah. I think it first starts with defining what data are you actually looking for? A large part of building integrations between these two systems is I have some data in the financial system. I have my CRM data in Salesforce. How do those two things map together? So I think the first step is what data are you looking for? And what is the mapping between what you're trying to do from a CRM perspective with whatever may be happening in that financial system? So to me, it starts with the data. I think the next question to ask is what is the trigger? It starts off this process. Is it someone sending a message in a Slack channel? Is it this order being created within your ERP? What is it that triggers this process to happen? You build the trigger, then you identify what the data mapping is between the source being that financial system and the target. And that's really how you get towards that working integration. Mike: Now, when I sit down with another platform owner and I talk about using MuleSoft, we can bring ... And so this is where you're going to quickly hear Mike's knowledge run out of gas because here's where Mike's knowledge hits the wall. But we can bring that data in and it can be like a pane of glass. We can just view that data or we could actually copy that data over so that we can use it in reports. And then we could also extend that conversation with the platform owner and say, "Well, if somebody wants to change something, they could change that in Salesforce and then Salesforce with MuleSoft can push that data change back to that platform." How'd I do? Mofeyi Oluwalana: I think you're almost there. Mike: Okay. Fill me in because what I don't know is what I don't know and I feel like there's other admins that may not know this as well. Mofeyi Oluwalana: I think the best way to think about MuleSoft is that real time app integration layer. So not necessarily the data that you want to live in Salesforce. Getting that unified customer view is really important. And so you'll need the data connectors in place to get data from external systems into Salesforce. That is one use case and one that Data Cloud solves really well. The problem that MuleSoft solves really well in tandem with Agentforce is the agent needs to take real time action. Again, so let's say we're going back to the retail example where I create an order. If order management doesn't happen in Salesforce, creating an order doesn't necessarily mean starting that process within the Salesforce ecosystem. I just want to be able to kick off that process with my OMS, my warehouse, my shipping provider. Then in that case, it's real time app integration. It's using the APIs that MuleSoft has to be able to kick off that workflow and that process using your agents. So it's a little bit different than moving data just from one place to another. Mike: No. I think that's also very important because companies have spent money on those systems. And I remember when I was sitting down with our finance team, they're like, "Well, if this data lives here and in Salesforce, what's the source of truth?" And we set it up so that we were just viewing the data because we really wanted sources of truth within the organization. But sometimes the user lives and dies within one interface and where that data comes from, we don't need that exposed to them. Mofeyi Oluwalana: Exactly. And I think it's the use case for consolidating data into one place is a little bit different from the use case of making sure that your agents can take action. And so I think as part of that rationalization that admins and IT teams have to do is what data do I need to drive what? And what actions do my agents need in order to be successful? And this part of that then can separate it into those two camps and then move forward with the tools that help them do so. Mike: Cool. Now, when you connect MuleSoft with other systems, does the admin need to ask for, can you provide a certain API? That's how it's set up, right? Or walk me through it because I've never set it up and I feel like I'm completely happy being the host of the podcast that asks the questions that admins are like, "Oh, I'm so glad he asked that because I didn't know to ask that question and I didn't want to look stupid in front of my IT people." Mofeyi Oluwalana: Yeah. So I think from the business side, we set the requirements about, okay, this is what I need. This is the process that I need done. These are the steps that should happen. This is what should trigger that. You do that definition. Then you can work with the IT team or the API developer to actually make that happen. Now the API developer has access to a number of connectors within MuleSoft that enable them to build these APIs and integrations without relying on what is the API specification for my OMS system or what is the API specification for my [inaudible 00:15:07] system? There are connectors that have a ton of different actions that you can orchestrate within a MuleSoft integration to get a certain job done. So one example that I like to use is the Salesforce connector. The Salesforce connector has a ton of different triggers. Let's say when a new object is created or on when a record is modified that can trigger the integration. The Salesforce connector also has a bunch of actions or operations. So I can create a record in Salesforce. I can delete a record in Salesforce. I can create a topic in Salesforce. All of the different actions that you can execute through Salesforce APIs extrapolate it into a connector so that it's easier to build and then manage these integrations. So the API developer is in charge of translating those business requirements into the integration composed of those connectors that allow you to achieve exactly that. Mike: Gotcha. Boy, there's a lot. It feels like there's a lot to it and we make it look so simple in demos. Mofeyi Oluwalana: Yeah. I will say it's much easier looking at a screen and hearing an audio podcast of what this really is. But I like to think of them as MuleSoft gives the tools, those building blocks. You can compose those building blocks in a certain order to create a workflow. Those are the integrations that you can use and your agents can also use to take action. Mike: Yeah. I always think of it as admins are managing users and agents and agents are just like users. They have to have instructions and guardrails and guidelines for how to operate and what they can and can't do same way that people have as well. I'd love to know, so as a product manager, you got into the program. How has being a product manager helped you understand the product, but also given you a different perspective of working through explaining different customer stories or use cases? Mofeyi Oluwalana: I would say the best, and I'm obviously biased, but the best part about being a product manager is just the sheer amount of data points that you see. One of the things that I think is really important as part of being a product manager is meeting with as many customers as you possibly can because it's through those customer conversations that they're very clear themes that you can draw, not only of how people use the product, but what the product doesn't quite solve for yet. And so going through those conversations has helped me not only understand those customer pain points better, but then understand the things that we need to do in the product to make it even easier for our customers to use. Mike: Yeah. No. I often feel when I was exposed for a brief six months as a consultant that a lot of the pain points customers have always felt the same. I was like, "Man, they have the same problem that XYZ has." And at the end of the day, you'd look at all the customers you manage and you're like, "They have these five problems." And then brand new somebody would come in and you're like, "And you have completely different use case and requirements and they don't fall into those same five problems that I've been solving all day, which is nice." So I'd be curious, as admins are looking more and more at building ... They build agents and apps on the platform and they extend the platform and they use MuleSoft. What are things that you're thinking about as a product manager for, wow, I have to be a year out or two years out. How should admins be thinking about their building and management of the Salesforce platform as a product? Mofeyi Oluwalana: Yeah. I think the most important thing is not just building for where we are today, but building for what's coming. I think one thing that agents in AI technology has taught us is that the technology market is changing so fast. It's going to be a new model. It's going to be some new capability that you want to be able to leverage. And in order to do so, the foundation and the platform that you're building on has to be interoperable. It has to be able to withstand some of those changes that you want to make. The example I always like to give is if having to change a model is going to disrupt your operations, that is an issue. And we know that is an issue because LLM models, a new one comes up every day, another one is deprecated every other week. So I think the most important thing thinking about the platform is how do I make the platform resilient and flexible so that as these new...
/episode/index/show/buttonclickadmin2/id/42018935
info_outline
How Can Salesforce Admins Find Simple Agentforce Use Cases?
07/02/2026
How Can Salesforce Admins Find Simple Agentforce Use Cases?
Today on the Salesforce Admins Podcast, we talk to Kacie Molina, Salesforce Consultant at Kawaii Cloud. Join us as we chat about how admins can start small with Agentforce and still make a big impact. You should for the full episode, but here are a few takeaways from our conversation with Kacie Molina. Why you should start small with Agentforce With all the capabilities Agentforce brings to Salesforce, it’s easy to dream big. Big projects, however, require major organizational investments in time, planning, and execution. My guest this week, Kacie Molina, has some simple advice for her clients who want to get started with Agentforce: start small. Go back to the basics of listening for pain points and building solutions. Once you start piling up small wins and meaningful changes, it’ll be easier to get organizational buy-in for something big and bold. Admins should listen for problems users already have Agentforce solutions don’t always have to be some sort of major business process overhaul. Those types of changes require layers of approvals, budgeting, and business analysis. You end up spending as much time rethinking the business process as you do worrying about executing everything in Salesforce. Instead, look for simple use cases. For example, implementing an agent summary field to help users easily see what’s going on with an account without having to scroll through a bunch of records. “All of those little use cases that maybe are too specific for a flow,” Kacie says, “we can solve them with Agentforce and natural language.” And over time, the simple solutions add up. Keeping AI work inside Salesforce supports better security Even if you’re not already using Agentforce, people in your organization are already using AI. The problem is that they’re often exporting data over to their LLM of choice, which creates all sorts of security vulnerabilities. That’s why Kacie recommends enabling an agent to assist your users. You can use your model of choice, and it’ll be grounded in your Salesforce data and protected by your security configuration. “It shows users that there's a safe place to get the answers they want without having to worry about breaking company policies,” Kacie says. Make sure to listen to my full conversation with Kacie about how to start small with Agentforce. And don’t forget to subscribe to the Salesforce Admins Podcast so you never miss an episode. Podcast swag Learn more Salesforce 360 Blog Post: Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins podcast, we're talking with Kacie Molina about how admins can start small with Agentforce and still make a big impact. Kacie shares why the best AI ideas often come from listening closely to everyday user friction. The scattered preferences, repeated questions, messy exports, and those tiny gaps that slow teams down. We'll talk about building agents that are grounded in Salesforce powered by Flow and designed with trust and security in mind. Because the next generation of admins isn't just adding features, they're orchestrating safer, smarter systems where humans and agents work together. So give it a listen, click that subscribe button, share this episode with an admin who is ready to make AI even more practical for their users. And let's get Kacie on the podcast. So Kacie, welcome to the podcast. Kacie Molina: Thanks, Mike. I am super excited to be here today. Mike: Well, I'm excited to get you on. I was a rare occasion scrolling through LinkedIn and I came across a post that you had put up and it mentioned the AgentforceNow workshop that I think you were in one of mine or you'd been to one. Kacie Molina: I was in one of yours and it was done extremely well, might I say. Mike: You were. Oh, good. Well, I try hard. And you're talking about coming up with ideas and you'd had some ideas for agents and I thought, "Man, I just think we need some sort of agent brainstorm podcast." And so that's why I wanted to get you on. But we're going to talk about that. But before we get started, tell me a little bit about yourself, like how you got into Salesforce, what you do, all of the fun stuff. Kacie Molina: Absolutely. So I grew up in more rural USA, an Amish type community, so horse and buggy. Think maybe Little House on the Prairie, early 1800s. So did a lot of horse training and cheese making with my sister, tended gardens and animals. So my skills when I became an adult were fairly traditional. So as I was trying to translate, "What do I use my skills for?" I started nannying, childcare, and then I started my own sewing business. And during that phase, I was actually so bad at running a business, so I knew how to sew, but I didn't really know the business part. So keeping track of contacts and invoicing people on time was such a disaster for me. It was all little handwritten notes. So I was listening to podcasts and I heard about Salesforce. I logged into Trailhead and fell in love with the gamified learning. So it was kind of no turning back for me. I got my admin certification in about three months, landed a junior admin role shortly after. And it's been about five years and 10 certifications since then of working on all kinds of projects from in-house to consulting. And I just think like Flows, all think Salesforce. It's so much fun. And in the day and age of Agentforce, even more fun nowadays. So that's kind of how I stumbled onto the Salesforce path and it has been way too much fun. Mike: Oh man, I bet we could do a whole podcast on the skills of sewing and how they carry over to Salesforce. Kacie Molina: We probably could, although I do think Salesforce might be a little more fun. One, because you don't get poked by needles. That's a huge thing for me. I don't even like going to the doctor and getting poked by a needle and I did that for a profession. So I got poked all the time and it's much less frustrating than trying to deal with broken sewing machines. Salesforce kind of works pretty well. And when you're dealing with old-fashioned sewing machines, not so much. Mike: I could imagine. Yeah. Needleforce, that's what we'll call it. Kacie Molina: Needleforce. Mike: I bet that exists. I think that would be so cool if there was quilting or sewing at Dreamforce. Because I see people on the plane all the time with those knitting needles and stuff. I would love to have the patience to do it. Kacie Molina: It definitely takes a lot of patience. So actually, interestingly enough, when I was just getting into Salesforce, Mallory Donahue, she's such an amazing person I look up to. She was getting into Salesforce at the same time as me and she was also a seamstress. So I think there might be more sewing and needle people out there in the Salesforce world than you might think. Mike: Yep. Well, this is the diversion that Mike's squirrel brain gets on too quickly. But let's talk about ... I was so intrigued by your post, because I feel like even in the workshop that we do, the AgentforceNow workshop that I hosted, I think I'm back sometime in October because I have some vacation in July. We build an agent for Pronto, which is a food service company and it handles questions and cases and order issues. I mean, I feel like by the end of it, it's pretty complex because we've already built some Flows. There's some Apex actions that are in there. And so I feel like we're getting nitty-gritty into it, but your post kind of almost felt like a breadth mint of like, "Hey, have you ever just thought about asking your users five questions or whatever and then turning on Agentforce and giving it on action to do?" Kacie Molina: Yeah. I really like the workshop, because it gets into the more complex things and you see how the broader, the depth Agentforce can go to. But for me, when I started looking at ... Okay. So I serve multiple clients, and a lot of people are excited about Agentforce and I talk to a lot of admins about it as well, but where do you get started? For me, it was the really simple, small things where people I feel like nowadays more and more are expecting to be able to use natural language. And you don't really need to build a crazy, big agent that takes multiple sprints to complete. You can turn one on fairly simply to answer a couple simple questions and people can start to see that magic work from even a small start. Mike: Yeah. And I feel like, boy, this is me just thinking of that post, but you had really good ideas around not just what I would call the hard aspects of business, which is like invoicing and questions and emails, but also kind of like the soft aspects of business, which is just asking Agentforce to coach you that day or just kind of simple questions that you could give it that would maybe make you as a salesperson or customer service person feel better about what you're doing. Kacie Molina: Right. I do. I think it's really cool that you kind of came back to the small ideas and I'm actually very impressed you found that post because I feel like not many people see my LinkedIn post. Mike: You mentioned me in it, so I got that. But I mean, to be fair though, the small little detail, little things like that are actually kind of the bigger hooks to look for. Kacie Molina: They are in there. To me, they're everywhere. So bigger agent ideas, like there's a couple things that can be intimidating about them. One, they take a lot of time. Two, you're always looking for that big idea that is going to wow the whole company potentially. And then it also entails potentially budget and project approval, which you need to get approval for most things that you do anyhow. But the small ideas are something that you don't really need to take a whole ton of business analysis, say, to get started on it. It's something that you could know off the start like, "Oh, I see my users asking about this in a support ticket frequently." So one example recently I had was somebody who said, "We have these client preferences and they're kind of scattered in the system and they're a little hard to find. So is there any way you could summarize them?" And I said, "I think this would be a really good use case for an agent summary field." So you can build the prompt and pull things together. It's the little things like that when you're listening to details that you might not have to go build a Flow or build something so specific for. And that would be my old use cases like Flow all day, every day. But all of those little use cases that maybe are too specific for a Flow to say, "Oh, we'll grab this and explain it this way." It comes out in Agentforce as the natural language and I think that is a huge thing for users that they're looking to see something that feels like them or feels human so they can click onto a record. Say they go to a client account and then they can see at a glance like, "Oh, this person prefers this and this and they don't like this." And that's much easier than scrolling through a bunch of records. Mike: Yeah. I've been so busy building agents that I forgot about some of the other prompt builder and the grounded fields that we had. I used to call them sparkle fields, I think like that, because they have little sparkles next to it when you can automatically have Agentforce kind of fill in based on a prompt and that's exactly it. I mean, I remember rolling out chatter and I did it probably the wrong way and I turned it on for the whole company and the whole company was like 50 users, but I didn't give them any use cases. And if I was now to go back, I would've picked a team of five people and said, "I'm going to turn it on for you and here's a use case to use it for." And I feel like your post was just ... It just made me feel less burdened to come up with these extravagant big ideas to use an agent for and it was more like, "No, you can just have the agent totally answer your front door and be like, 'Hi, we're not home right now,' and that's it." And I was like, "Oh." Because I feel like admins are sometimes sitting down and thinking, "How do I make an agent that answers the questions and closes a $6 million deal?" Kacie Molina: Right. And then there's a bunch of, in my mind, you have more selling at that point. So if you're coming up with a new idea, then you kind of have to pitch it to the company. But something I like about the small ideas I've been picking up on lately is that it's kind of puts us back into our usual admin position where we're hearing problems and then we're offering solutions. So instead of coming up with a new business flow, start to finish of a new agent that can do some flashy thing, which is also extremely cool. You can also take something where somebody says like, "Oh, I export this data and ask ChatGPT about it. Anyhow, I'm already using AI." And so you can start to hear use cases where you're not coming up with something new, you're just solving something they're already doing in a more secure way. And that's another big idea for me is security within Salesforce is so much more attainable for admins. When people start exporting data and loading it up into an LLM that you don't have control over, that's a lot more scary for as an admin than if they can just use it from within the system. Mike: Yeah. I mean, when you and I talked before we pressed record, you even brought that up. If you're an admin and you're in meetings and maybe it's not even a Salesforce meeting and you hear people bring up a different LLM, what in your mind goes off and what do you think of to do as next steps if you were to help coach admins who are in that position? Kacie Molina: Something that's really incredible about Salesforce that maybe not everybody knows that they haven't played around with Agentforce yet is that you can use customized models. So it's not like you only have availability to use the Salesforce model. There's also, you can bring in different like ChatGPT if you like their open AI's model, you can use those different AI plugins within Agentforce. So that's something that goes off my head is if you like something, you don't have to totally forsake that for something new. So you can feel at home within Salesforce with the different AI models. And also, if you're using different AI models, which just like constantly goes off in my brain is that you can do that with way fewer clicks and way fewer security risks if you do it from within Salesforce without having to potentially like fudge on permissions or fudge who has access to it. So that's something that goes off in my head is like, "Oh, if you're doing this with AI already, you can just pull that into Salesforce and then you have even more data." So you are kind of limited when you export data to what the LLM can see. But when you have it within Salesforce, you have so much expansive broader options that you can use. So you can pull in different records and different things from here and there and you don't have to be so specific in one point in time. You can re-ask again in 10 minutes if you have information flowing in. So for me, it's like the different LLMs that are available within Salesforce and data availability is huge. Mike: Yeah. I mean, plus once you export that data and take it out of the platform, for many companies, you're already violating security because that data is housed in Salesforce for a reason and it's not meant to be used elsewhere. Kacie Molina: Yeah, that's a big risk I think with AI. Most companies I think are using it, whether it's an approved tool or not. So when you even enable to me a basic agent in a Salesforce or it shows users, "Hey, there's a safe place where I can get the answers that I want and I don't have to worry about breaking company policies to get the data I need." Because we are in a fast-paced world and I know some users, they really do need to get answers that maybe they can't get within Salesforce today. So they're exporting data and getting their answers with an AI elsewhere. But if they can have that easily accessible and it's safe to use, then I think that enables both admins to feel safer about their org and the users to save clicks, save time and get a better answer Mike: Absolutely. Back to that workshop, I'd love to know your perspective. So we talk about agents and subagents and even in that workshop we create a subagent to handle, I think it's returns and refunds, or order issues and refunds. I'm trying to remember it without remembering it. When you're working with customers or talking with companies about using Agentforce, do you even talk about agents and subagents, or do you just kind of like, "Here's the magic and I'm going to build everything behind the curtain"? Kacie Molina: I usually don't bring up the different agents and subagents and I guess it depends who your stakeholder is. If there's somebody who's more admin-minded and very inquisitive, I would potentially bring it up. But most of the stakeholders, I'm working with bring-me problems and expect me to be the expert and bring them solutions and they don't really care about the very cool details about agents and subagents I think are so fun to talk about. They just want to see the magic on the end. So for me, it's kind of like Flows. I kind of relate most things back to Flows when I'm learning how to code or anything. It all comes back to Flows for me because Flows are magic and they're so much fun. A lot of people don't care if you call sub-Flows or you have different components in the Flow. They just want to know when X happens, they see the screen and then magic happens in the background. And I think agents are kind of the same way where they're really cool to see the backend for people who care, but you can also talk to stakeholders at a higher level without them needing to know that detail. Mike: So you talk a lot about Flows. How important was it for you when Agentforce came out that a lot of the power behind what it could do its actions are powered by Flow? Kacie Molina: Oh, that was huge for me because it feels like it brings the control back to the admin. So I definitely wasn't the most happy, quick adopting of AI when it first came out. I was definitely suspicious and I love my Flows and I love doing things manually. So I was definitely suspicious of AI in general and I've learned to really love it. And part of that is being empowered to do tasks on the backend. So you have the agents that do all of this, we'll say agent magic in the background, but then there's also the pieces that you can build out manually in Flow so you have control over what information you're pulling, what you're feeding to the agent, that way you get the predictive and answers that you want. Mike: Yeah. And even the builder, I feel like that the new agent builder feels like Flow Builder, because, well, there's also variables in there, which still worry me. Kacie Molina: I do like the UI better. Mike: I'm still not the best at better building Flows. I don't know why my Flow confidence is low, but maybe that shouldn't have rhymed, but yeah, my Flow confidence is low. Kacie Molina: I feel like you're probably much more of a Flow expert than you're letting on. I will say though, the new UI gave me a pretty big boost. So the old UI wasn't quite as intuitive or friendly and that's something I really wanted to post on LinkedIn about as people who maybe like me, they got their certifications and started doing their Agentblazer statuses on Salesforce when it was earlier. And then when you come back and you see the new UI and ease of use and having things like variables where you feel more comfortable like a Flow, all of a sudden I was like, "Oh, I can really do this this time. This makes so much more sense." Mike: Yeah. And the fact ... I mean, we don't get into it with the workshop, but I'd love to know, have you ... So the one thing I want to do is I'd love to have an agent help...
/episode/index/show/buttonclickadmin2/id/41920675
info_outline
How Do Admins Set Up Agentforce Coworker in Salesforce
06/25/2026
How Do Admins Set Up Agentforce Coworker in Salesforce
Today on the Salesforce Admins Podcast, we talk to Parth Shah, Director of Product Marketing, and Rikke Hovgaard, Director of Product Management for the Agentforce Coworker team at Salesforce. Join us as we chat about Agentforce Coworker and what it means for the way admins help teams get work done. You should for the full episode, but here are a few takeaways from our conversation with Parth Shah and Rikke Hovgaard. Agentforce Coworker brings AI into everyday business work AI has been a game changer for coding, but integrating it into normal business processes has proved more challenging. That’s where Agentforce Coworker comes in. It’s an autonomous AI teammate, grounded in your enterprise data from day one. For this episode, I sat down with with Rikke Hovgaard, Director of Product Management, and Parth Shah, Director of Product Marketing, to find out what Agentforce Coworker is and how it can help admins bring new tools to their team. Salesforce permissions remain central to trust and access Trust is central to any conversation about AI. New tools are exciting, but you need to be sure that they won’t give people access to data they shouldn’t be able to see. Luckily, Agentforce Coworker works around the permissions you’ve already configured in Salesforce. It’s simple for admins, and keeps those guardrails in place. As far as configuration goes, Rikke and Parth are all about keeping it simple and transparent. While Agentforce Coworker automatically inherits the security and governance settings that are already in your org, you also have special configuration options just for the agent. Admins can connect more data through Data Cloud and Slack For Rikke, Agentforce Coworker is especially useful for summarizing her team’s Slack conversations. She can quickly understand which team member is working on which issue, and where she might need to lend a helping hand. At the end of the day, Agentforce Coworker gives you a conversational interface to do more with your Salesforce data. “Coworker does the work in the background so that your team can actually focus on what matters,” Parth says. Listen to the full episode for more from Parth and Rikke about Agentforce Coworker. And don’t forget to subscribe to the Salesforce Admins Podcast to catch us every Thursday. Podcast swag Learn more Salesforce Admins Podcast Episode: Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins podcast, we're talking with Parth Shah and Rikke Hovgaard about Agentforce Coworker and what it means for the way admins help teams get work done. Now, this isn't just about turning on another AI feature. It's about bringing trusted business context, permissions, data, and automation together so users can ask better questions and take action faster. Parth and Rikke are going to walk us through how Coworker connects to Salesforce data, how it respects existing permissions, and how it gives admins a simpler path to roll out and governance. So, be sure to listen in, press that subscribe button if you haven't already. And I would always appreciate it if you could share this episode with a fellow Salesforce admin. And with that, let's get Parth and Rikke on the podcast. So, Parth and Rikke, welcome to the podcast. Rikke Hovgaard: Thank you for having us. Parth Shah: Thank you. Mike: Well, I'm glad we could get you both on. This is the first time I've had a product manager and a product marketing major on a podcast. Usually, one of them has something too important to do that they bail out, but I'm bringing people together. It's going to be great. So, we're going to talk about Agentforce Coworker, but first I want to learn a little bit about each of you. Parth, I'm just going to start with you because you were the first one to bug me in my Slack DMs about Agentforce Coworker. So, I'd love to learn just a little bit about how you came to Salesforce and what you currently are working on. Parth Shah: Yeah, absolutely. Slack makes it really easy to bug my Coworkers, especially my favorite ones. I sent a lot of emojis. So, sorry, Mike. Mike: Oh, I'm your favorite. Parth Shah: Yeah. So, a bit about me. I grew up in Ohio, was a chemical engineer in undergrad, which really I love to build things and I love to, I guess, solve complex problems. And then when I graduated, I didn't want to go work in a plant, in a chemical plant. And so, I ended up going into sales within oil and gas. Did that for about three years, really understood how to actually talk to customers and what their pain points are. And then switched over to a really early stage startup in education technology, really passionate about education. Did that for about three years, which is where I learned a lot about product marketing. Then got my MBA and then joined Salesforce. So, been at Salesforce as a product marketer for about coming up to seven years. And what's been kind of interesting is I started off on the MuleSoft side of Salesforce, so all about integrations. I really learned what it means to connect data between different systems and how developers and admins go about doing that. And that's when I switched over. MuleSoft wanted to launch a new product called MuleSoft Composer at that time, which is now Flow. So, the next level of after connecting data is like, how do you actually use that data to automate processes and make it super simple for admins like our viewers out there? So, help launch that and then moved over to our Data 360, previously data cloud business. And here, I focus on everything that is around unstructured data. So, again, the through line here, if you look at data is, now we can start tapping into the unstructured data that's all out there because of AI. But the more important thing is now that AI is coming in, how do we actually bring that data, which is full of richness in audio, video, meeting notes, et cetera? How do we bring it into AI so that AI is really grounded? And so, that's been kind of my journey. Obviously, looking back at it, everything kind of connected. I didn't know at that time, but the through line I think is my curiosity of what's next within tech has kind of propelled me to go and find out and work on the cool next product that's coming up, which is also how I land on a Coworker. Mike: Wow. I would've had no idea that you started in oil and gas. Also, what's sales like in oil and gas? Hi, do you want any? Yes. Parth Shah: Cool. Yeah. It's very old. It's a very people oriented business. Mike: Yeah. All right. Well, I had to get that joke in. Rikke, I know you're letting me say your name that way, but in all fairness, being German, there's names that we just can't pronounce. So, I'd love to hear how you got started at Salesforce and obviously you're working on Coworker now. Rikke Hovgaard: Yeah. So, originally I'm from Denmark, which is why my name is a little hard to pronounce. Believe it or not, that's actually a pretty common name in Denmark. So, Rikke is fine here, but I started out after university working for a consultation partner. So, I started implementing Salesforce randomly, started out with Sales Cloud, Service Cloud, moved over to Pardot and Marketing Cloud when that was acquired by Salesforce and ended up also doing a little bit of data and analytics there. And then I decided it was time to move on to other things. So, I joined another partner in London and I moved to London and did that for a bit. I was working a lot on analytics at that point and also marketing. And so, it was mostly focused on what we know now as CRM Analytics and I started a blog on it as well. And so, a few years into it, I joined Salesforce in the CIM Analytics product team, helping customers get the most out of CIM analytics, deescalate some of their issues, best practices, all this kind of stuff. And I think that's where I also got a lot more involved with the community. And then I joined later in Data Cloud, moved over there and about two years ago I started the team with the search team in Data Cloud and we had this idea of Coworker and I ended up working on the admin side. And today I own the Coworker setup experience as well as search manager. Mike: Oh, wow. I mean, all roads lead through Data 360, literally and figuratively. So, Parth, let's talk about that. I mean, for anybody that hasn't heard, what is Agentforce Coworker and what is it there to help with? Parth Shah: Yeah. So, Agentforce Coworker, it is your autonomous AI teammate and it's available in Salesforce and it's also going to be available in a lot of different services like Microsoft Teams, desktop, mobile, ChatGPT, Claude, and a lot more. Fundamentally, what it is is it's an AI assistant that knows your business from day one. It's already connected to all of your enterprise data, whether it's structured, unstructured, your opportunities, your cases, your accounts, all of that context that you have within Salesforce and then what's connected to Salesforce. And of course, it respects all the permissions when you do connect those systems. So, it's grounded in your context from the first prompt that you ask. Number two is it can also orchestrate a lot of your agents. It can also execute a lot of complex tasks so that way, it moves your work forward. In other ways, it takes action on your behalf and you can actually update your CRM using Coworker. And then lastly, we built that headless. So, what's really cool about this is yes, it's available in Salesforce, but now you'll be able to take that Salesforce experience and that data and the context that you've spent so many years building into wherever you work. Now a question that we usually get is like, why do we build it? What was kind of the reason behind it? What's the pain point that is really trying to solve? And I think if you look at the industry trends, what's been interesting and what's kind of been going on is you've seen AI obviously augment software engineering, right? It's writing code and it's improving their productivity, but when we think about how business users actually do their work, it's quite different than software engineers, right? Of course, AI can help write emails, it can create the docs. We're going into customer service, but it gets a bit more complex because in our day-to-day work, we're switching a lot between different applications. We're copy pasting a lot of different data from one application to the next, for example, from Slack to Google Docs and so on and so forth. And it's not adding as much value as it does for software engineering. And so, we said, "Okay, how do we bring all of that context that you have wherever you work into a product that brings in AI and actually helps you do the work so you can focus on a lot of the other things that are more important, like building your relationship?" And Salesforce being Salesforce, we said, "Let's bring in that context and we have that AI and let's put it into Agentforce Coworker, which is where also Salesforce, our users work." And the second thing that we also did on top is if you think through where most of your work actually starts, which is again, very different than how we think about agents in general, it starts from work. Anytime you have a question about a task, you go to search. And so, we said, "Why don't we turn that search into something agentic where search gets you answers and then answers can help you take those actions?" And so, fundamentally what we've done is we brought in that context and made it really easy for our users to use Salesforce and fundamentally get a lot more value out of Salesforce and all the things that it can do with the data that you have. Mike: Yeah. I think what's cool is Coworker's not just for admins. I mean, we'll talk about that, but it's for all of your users. So, one question based on everything that you said, just to make sure that I kind of wrap my head around it as an admin, if I'm setting it up, I can permission what it can and cannot have access to in terms of data. So, if I have, let's say payroll data in Salesforce, I don't want to give it access to that so that Bob and sales can go down and be like, "Hey, I wonder what Sally makes," and then ask Coworker and get a response, right? Rikke Hovgaard: Well, we're actually using the same permissions that you've already as an admin set up in Salesforce. Mike: Oh, great. Rikke Hovgaard: So, there's nothing extra to set up. We tried to make the setup experience super simple and one of that is also, of course, knowing what you've already set up in terms of permissioning. So, if you have in your object given access to something, then the user that is locking in will be able to see that. And if they don't have access to it, they won't be able to see that data either. Mike: Gotcha. Wow, that's huge. So, it automatically just respects the user's permissions as opposed to me the admin having to go and set something up for it. Rikke Hovgaard: Correct. Yeah. Mike: Wow, that's really ... I mean, what's funny is every time I see or work through some of these new products, I'm like, "Oh, well that totally makes sense." Except I think that was probably really hard to do. So, it's always really cool when it happens. It's like intermittent wipers, I suppose. Rikke Hovgaard: Yeah. Well, we have some amazing engineers that figure out all the architecture and build this stuff. So, I can't take credit for that, but I guess from my point of view at least, as an admin, there are so many things that you have to learn with all these new features. And so, our vision was really to try and make the whole setup simple. We also wanted to be transparent around the permissioning and the governance around it. So, we've also tried to balance that, but it's also how much information do you give upfront? How much is in the documentation? So, it's a fine balance to try and make it all simple enough. Mike: Yeah. Now can we talk a little bit about the design of it too because I've seen, thankfully I've had an org and I got to play around with it and it couldn't be more intuitive. I'm sure it could be, but can you talk about what went into how you thought about what that user experience is looking like? Rikke Hovgaard: So, I think it's really down to the jobs to be done. What are you trying to achieve? And that's why the ask mode is very much focused on just asking the question and having that conversation. We wanted to make that a very clear, crisp understanding of what is it that you're supposed to do on this screen. I don't know if you had a chance to also play with the other part, which is we also introduced a new search experience and here that's more of a balance where we're trying to figure out, well, all the things that people love from the original search and how do we bring that in as well as also how do we make it a little bit more new and look a little bit more or nicer, so to speak. I think that has been a little bit of a challenge when we're thinking of all of the data that you can bring in Coworker compared to what we have in Global Search. And now I know we're going a little bit more into the admin side of things, but in order to display things correctly, we need to make sure we also have the information of the data in order to show it correctly. So, that has been an interesting challenge to look at, but yeah, really trying to make it super easy for users to know what they actually have to do, prompt them to get the most out of the tool. Mike: Yeah. I mean, it almost feels like at times there's a balance between making it super simple and having people trust it and making it a little bit more difficult just so that people trust it because you've gone through it. And if it's almost too easy, then it's like, "Hmm, but did it really do? Is it really..." I can always feel that anxiety in a user or an executive when you demo something the first time and they're like, "Yeah, but does it really do that?" Rikke Hovgaard: Especially also when we think about AI, we're putting a lot of trust into it and allowing us to get the answers that we're looking for. And so, I think that's why the whole thinking steps that we have implemented is super important for the agentic response. So, we built a level of trust or transparency in what is it that we're actually looking and giving that information to the end user so they can see how we got to the result. Mike: Yeah, absolutely. Now trust and governance is top of mind. It's literally the first thing everybody talks about with AI. Can we talk a little bit about how that works with Agentforce Coworker and maybe some of what you're seeing in the beta version? I feel like I was on that Agentforce Coworker page and there was an admin on that page that's awfully familiar to a lot of the community that had some great quotes. Rikke Hovgaard: Mike, let's maybe start with how do you actually set up Coworker. I think that will lead into how do we control the permissions and- Mike: Yeah, let's start there. Rikke Hovgaard: Okay. So, the vision we had with the setup page, because if we're being honest, we are using features from other parts of Salesforce. So, we're using Agentforce, we are also using Data Cloud, we're also using global search. So, the thought that we had in the beginning was that's a lot of steps and hoops for an admin to go to in order to set up a Coworker. And so, our vision was really, how can we simplify this? How can we get an admin up and running super-fast? That doesn't mean that they don't have more things they can do, but from the first click turn on to they have access to Coworker, we wanted that to be super simple. So, we have defined a bunch of steps that has to be done in order for you to use Coworker. One, for instance, we have to create the search agent. So, when you click turn on, you actually go ahead and we've automated a bunch of steps for you that goes ahead and creates the things that we need to get Coworker up and running. And in that we've created the agent, we created the permission set group that you need to give access to users and we also have enabled your Salesforce data out of the box. So, any Salesforce data, any custom object, any default or standard object that you have is automatically searchable just by hitting turn on. Now, since we are in a beta, we still need you to opt into the beta. So, there is a little step that some people might miss, which is just go ahead and opt in so you have the new search experience in the front end with the global search bar and the ask button. And then the final step in order to get a user to access and use Coworker is to assign them this permission set group. Essentially, if you're an admin, you're probably familiar with different permission sets are giving you access to different things. So, you need to have a permission set for your agent, you need to have a permission set to use some basic features of Coworker and there's some other things, but essentially we're bundling all of this together in the permission set group. And so, all you have to do is directly from the page, the setup page. You can assign your users directly from that, or you can use the permission sets or permission set group from the user setup page as well. So, that's to say that we tried our best to make everything as simple as possible and then you can lay additional features on top of that with external data, et cetera. So, this is how we are controlling whether or not you have access to it, just permission sets and permission set groups. Mike: That's very easy. So, if an admin turns it on, it's not just available to everybody. Rikke Hovgaard: No. Mike: You can choose whether or not maybe you want a small set of users to try it out first. Rikke Hovgaard: Exactly. Mike: Perfect. Rikke Hovgaard: This is all permission based. Mike: I like it. Parth Shah: Now Mike, following on that, I think if we look...
/episode/index/show/buttonclickadmin2/id/41794575
info_outline
What are Security Essentials for Salesforce Admins
06/18/2026
What are Security Essentials for Salesforce Admins
Today on the Salesforce Admins Podcast, we talk to Laura Pelkey, Director of Customer Security Communications and Engagement, and Sabrina Simeroth, Product Manager for Security Center at Salesforce. Join us as we chat about security essentials for the summer and how Salesforce is helping admins protect their data. You should for the full episode, but here are a few takeaways from our conversation with Laura Pelkey and Sabrina Simeroth. Why admins are a target Security doesn’t take a summer vacation. And while AI is helping all of us do more things faster than ever before, it’s also helping hackers deliver new types of targeted attacks at scale. And as privileged users, admins are finding themselves in the crosshairs. Luckily, Salesforce is rolling out key security enhancements over the summer to help you protect your org. I sat down with Laura Pelkey and Sabrina Simeroth to talk about what threats are out there and how you can be prepared. MFA requirements to protect your credentials Because AI makes it easier than ever to imitate someone’s writing style or even their voice, the biggest threats that Laura and her team are seeing are different variations of phishing attacks. In the end, it’s all about getting someone’s credentials and then using that access to do damage. That’s why Salesforce is requiring all customers to use multi-factor authentication (MFA), as opposed to the gentle nudging we’ve done in the past. However, MFA can still be vulnerable to man-in-the-middle attacks, so admins and other privileged users will need to use a stronger phishing resistant MFA. Finally, Salesforce will require step-up authentication for users attempting a sensitive or unusual action, like exporting a large file. I don’t have to tell you that these kinds of changes can often be met with resistance. Laura recommends framing things in terms of what they protect your users from. Does a salesperson really want a hacker to email everyone on their contact list from their account? It’s not about making you jump through hoops—it’s about protecting you from real risks. Security Center Essentials and Health Check give admins a central view We also checked in with Sabrina about how her team is trying to make it easier to get a handle on essential security configurations across the platform and what settings are most critical. Coming in July, the new Security Center Essentials will let you see everything in one place instead of having to wade through a bunch of permissions and toggles. Health Check will help you prioritize which changes will get you the biggest bang for your buck, and help you track your security posture over time. “It’s all about allowing admins to navigate the security space in a way that helps to reduce the complexity and provide some guidance,” Sabrina says. There’s a lot more from Laura and Sabrina about security on Salesforce and what’s coming next, so make sure to listen to the full episode. And don’t forget to subscribe to the Salesforce Admins Podcast to catch us every Thursday. Podcast swag Learn more Salesforce Help: Trailhead: Admin Trailblazers Group Social Full show transcript Mike Gerholdt: This week on the Salesforce Admins Podcast, we're talking security with Laura Pelkey and Sabrina Simeroth. The threat landscape is moving fast and with AI in the mix, attackers are getting better at targeting privileged users like Salesforce Admins. But in this episode, it isn't about fear, it's about readiness, trust, and the systems admins can put in place to protect our orgs. We'll cover MFA enforcement, phishing-resistant MFA, step-up authentication, and how Security Center Essentials gives admins a clearer view of the settings that matter most because today's admin isn't just managing features. They're designing secure, trusted systems that help businesses move forward. So, let's move forward with this podcast and get Laura and Sabrina on. So, Laura and Sabrina, welcome to the podcast. Laura Pelkey: Hello? Sabrina Simeroth: Thank you. Thanks for having us. Mike Gerholdt: Absolutely. Well, it's always good to talk security. I feel like I was watching the news the other day and they talk about kids when they go to school and then they have the summer off and there's that summer slump of information. I feel like maybe over the summer we kind of have a security slump because we're taking time off and we're going to water slides and watching tornadoes in the Midwest, but maybe I'm just crazy thinking about that. Laura, why don't you catch us up and tell us what's going on with security and some of the newest things in summer 26? Laura Pelkey: I would love to. And I was just going to say our catchphrase, which I feel like I repeat every time we do a podcast together and that security never sleeps even in the summer. Mike Gerholdt: Oh, yes. Right. That could also be a fun summer action film. Laura Pelkey: Yes. I would see it. Mike Gerholdt: I would. Laura Pelkey: Yeah. So, I mean, we're halfway through the year, which is crazy already. And I'd say in the last year we have seen the security landscape and the threat landscape shift tremendously. And especially, I mean, I think a lot of people at Salesforce and a lot of people who are listening are very aware of and use on a day-to-day basis, AI nowadays, which is great. It's a very powerful tool. But what we're seeing in the security landscape is that AI-driven cyber threats have emerged and hackers have really up-leveled their ability to create and execute targeted cyber attacks faster than ever before. So, it's kind of crazy the speed at which this is happening. And unfortunately, I think we're going to see their capabilities get better and better as these tools evolve. Mike Gerholdt: Well, that's not fair. We're supposed to use AI for good. Laura Pelkey: Yeah. Well, the good news is, so yes, I agree. The good news is that providers are now using the same AI models or better AI models if you're in the lucky groups to enhance the security of their platforms and products. So, now the playing field has really been evened out. Mike Gerholdt: Well, that's good. Laura Pelkey: Yeah. But we're in a really interesting time right now with cybersecurity and AI. Mike Gerholdt: I mean, I feel like everybody's trying to figure out AI and now that kind of only muddies the water of impersonating other people or the speed at which it can replicate good or bad effective use of, I don't know, text messages or different spoofing. Can you walk us through how does Salesforce leverage AI to proactively block the type of threats that you're seeing today? Laura Pelkey: Yeah. So, there are some really common threats that just across the industry we're seeing that AI is being used for. So, account takeovers and this is a really common one. This is where attacker might use AI to create a phishing campaign, which targets users and tries to get access to their account. And then once they're inside a user account, they can then utilize all of the privileges that that user has to continue carrying out their attack. So, it's really about getting credentials, finding creative ways to get around our existing solutions to get those and then get that user profile and exploit it. Mike Gerholdt: Yeah. I think one thing that you've pointed out in the past is identity-based social engineering. So, I'd love for you to kind of expand on what makes admins and some privileged users such high-value targets for that. Laura Pelkey: Yeah, that's a great question. So, identity-based social engineering is when attackers create very highly personalized phishing campaigns and this can be phishing. Traditionally, we saw that with email five years ago it was primarily email. Now we're seeing phishing campaigns and especially with the help of AI, attackers are conducting these campaigns over voice calls. So that's called vishing or voice phishing. And admins are such a appealing target for these attackers because they're privileged users, they have such a high level of privilege and they can do almost anything within their Salesforce org. And so, that persona in general is highly targeted by attackers because of their level of access. Mike Gerholdt: What would you suggest an admin listening to this do today to start just being ready for if that phone were to ring and it was a malicious actor on the other end? Laura Pelkey: Well, I mean, we always say use common sense. So, there are a lot of built-in protections that I can talk about within the Salesforce platform that will help protect admins, which is great and I'll talk about those in a minute. But if that ever happens, if you are an admin and you get a call from a number that you don't know, from a person that you don't know claiming to be your help desk or claiming to be even Salesforce in some cases and they're asking you to log into your Salesforce account for them so that they can help you do something, that's typically how these things are positioned, that kind of scenario is never going to legitimately happen. No one's going to call you or email you and send you a link and ask you to log into your Salesforce account ever. That's just not something that we do. So, look for red flags like that. And in general, whenever you're suspicious about something from a cybersecurity perspective, the best thing to do is disengage with whoever is trying to speak with you or engage with you and get you to do something and then hang up the phone, don't email back whatever it is and then call your help desk line or call your Salesforce account person in a number that you already have and that you are already confident in and that way you can verify if that interaction was real or not. Mike Gerholdt: Yeah. I think the thing that always struck me when you would bring it up or somebody from your team, Laura, would bring it up is it's that human nature side that they try to take advantage of like, "Oh, you want to be helpful and you don't want to cause a problem." And so, you just kind of go along with it and it's like, yeah, you're not causing a problem if you just say, "Let me call back the number that I trust and talk to somebody there." Laura Pelkey: Yeah. Yeah. And you can do that in any scenario. If it's like your bank, someone calls and says they're from your bank and they're reaching out to you, that probably isn't going to happen. So, what you said, Mike, is exactly right. The reason that people are exploited is because we have these human behaviors, which human behaviors are great. They make us who we are, but false urgency is one of these tactics that attackers will use and they'll try to get you to do things quickly without really thinking about it. So, if we feel like goosebumps or we kind of have a weird feeling about why is someone calling me and asking me to log into my account, we can just stop and think and that's the best thing you can do to break this cycle. Mike Gerholdt: Yeah, absolutely. Well, let's talk about some of the security enhancements that has come out over the last few years. I mean, we have MFA and we have a whole bunch of other things. Laura Pelkey: Yeah. Yeah. So, we're very aware that this threat landscape has shifted and that it's our duty to protect our customer's data as it always has been at Salesforce. We take that super seriously, trust. Trust is our number one value. And so, to better help our customers protect themselves against these quickly evolving threats, we have some new enhancements and some new requirements in our platform that will help harden our customer security posture against these kinds of attacks. So, one thing, I'll only talk about a few, but one thing, and everyone really should be using this because it's been around for a while, is MFA, like you said, Mike. And I think we had started requiring customers to use MFA back in early 2022, I think. So, it's been quite a while, but we're actually going to be enforcing that. So, rather than being contractually required, it's going to be enforced in the product, meaning you may not be able to log in if you are not using MFA. So, this is going to happen starting in June. There's a phase rollout based on sandboxes and production environments. So definitely check out the documentation for the exact dates, but it is starting now. So, soon all Salesforce customers will need to use MFA to log in. Mike Gerholdt: And I know we've done security workshops. I've seen you present a lot. One of the questions, and inevitably the person that is listening to this is like, "Yes, Mike's going to ask this question." That comes up in all of the security workshops is, "Well, we use SSO to sign in. Do I still need to use MFA?" And we just threw out a whole lot of acronyms there, so I'll have you explain them too. Laura Pelkey: Yes. So, SSO- Mike Gerholdt: Alphabet soup. Laura Pelkey: SSO is single sign-on. That's a great question, Mike. So, if you do use SSO to access your Salesforce instance, then that does satisfy the requirement, but we ask that you also use MFA on top of your SSO. SSO is great. It's a great tool to make it possible so that you don't have to remember a million passwords for all of your work apps. It's awesome. Just have to remember one, but as long as you are using MFA to access your SSO, you are satisfying this requirement as well. Mike Gerholdt: Awesome. You explained it and you used all the alphabets too. Laura Pelkey: All the letters in the alphabet. Yeah. Mike Gerholdt: It's like MFA is like bacon and SSO is like a cheeseburger. It makes it better. Laura Pelkey: Yeah, exactly. Yes, I love that. Mike Gerholdt: Because MFA is also just good on its own. I mean, I'll just eat some bacon. Laura Pelkey: Yeah. So you can either use MFA for direct logins directly into the UI or with your SSO login. Mike Gerholdt: So, this makes me think of, you talked about phishing. Oh, boy, this is where audio doesn't serve me well. Phishing and vishing, which there's the PH and the V, but because I'm from the Midwest, you can't hear the difference. Could you explain the difference between standard MFA and phishing-resistant MFA? Laura Pelkey: Yes. So, yeah, this is actually kind of a newer... Think of it as a supercharged form of MFA. So, what traditional MFA, you have two layers of verification before you can log into an account. With phishing-resistant MFA, you are actually bound to a specific site when you're logging in, which makes it harder for attackers who are trying to get you to log into those fake websites that might look real. It actually helps prevent that. So, that's why we call it phishing-resistant MFAs because that is a really common thing for phishing attacks to leverage is these man in the middle fake websites where you think you're logging into your actual tool or product, but you're logging into a fake version of it. And another thing that's great about phishing-resistant MFA is most users of this use biometrics as their second form, so like a fingerprint or a retina scan depending on the device that you're using to log in. So, that just makes it, again, harder to fake and harder to intercept. So, this is most companies are moving towards phishing-resistant MFA as it's so effective, and which is why we're actually also starting in June, so this month, we are requiring system administrators and privileged users to log in with phishing-resistant MFA. Mike Gerholdt: And why is that? Laura Pelkey: Because those are privileged users like we talked about, they're highly targeted. They're more targeted than their regular user and they have such a high level of access that if their account, especially were to get compromised like an admin, it could cause a lot more damage. And so, we want those folks to be extra, extra protected. So, phishing-resistant MFA we feel is the best thing to ensure that those accounts and those users stay safe. Mike Gerholdt: I like that. Now I know I've had to roll out different features to users and sometimes you can't do it fast enough because they love it and other times it's getting them to eat their vegetables. For admins that are worried about user friction with MFA, what would your advice be? Laura Pelkey: Well, hopefully your users are already using MFA. If they're not, we often find that if an admin holds a training, some informational sessions with their users, some kind of enablement before this change happens and also talk to them about the value that this provides to them. The last thing a salesperson, for example, would want is if their account got hacked and then their clients are getting emails that are sent from them, which are actually malicious. They don't want that to happen. No one wants that to happen. So, just there's some enablement materials that exist on the help portal that could be helpful, but really it's admins explaining and enabling their users why this is so important and helpful. Mike Gerholdt: One last thing, admins love reports and I feel like isn't Salesforce doing something to help admins set up different kind of reports or report actions to understand maybe when a user would log in that's outside of the normal behavior? Laura Pelkey: Yes. Yeah, I love that. Yeah. So, this is another enhancement that's coming this summer and it's called Step-Up Authentication and we're doing it for report actions and for anomalous report behavior. So, let's say one of your users all of a sudden wants to export a very large file or something. There's something kind of unusual about this. Anomalous is the word we use in the security community. Our platform is now able to flag that and will cause a step-up authentication toggle to happen. And if you're not familiar what step-up authentication is, it's basically like having to re-log in after you've logged in, which I know might sound annoying, but there is a really good reason for this. So, I always think of it as like the airport analogy. So, when you go to an airport, you have to show your boarding pass and your ID to get through the security line, right? Mike Gerholdt: Mm-hmm. Laura Pelkey: And then once you're through security in the airport, you have the freedom to kind of walk around, go get a coffee, go get some food, maybe go to the bathroom and you have freedom of movement because these are not sensitive actions, what we would call in security. But when you get in line at your gate and you're trying to board the plane, you have to again, show your boarding pass in order to get on the plane. And that's actually a step-up authentication. You can think of it like that. This is because getting on the plane is considered a highly sensitive action and requires additional identity verification. And so, that's what we're trying to do within the product. So, say an adversary or an attacker did get access to your Salesforce instance through a user and now they're inside and they're trying to do sensitive things or they're trying to do things that are very bad, we are now able to force them to verify their identity again, which would likely stop that action. Mike Gerholdt: Nice. Well, here's your Starbucks, but you can't board the plane. Laura Pelkey: Yeah, exactly. Mike Gerholdt: I like it. Laura Pelkey: I mean, if you lose your boarding pass in the airport, you can't get on the plane, right? Mike Gerholdt: I mean, you should- Laura Pelkey: Oh, wow. Mike Gerholdt: It also probably means I've lost my phone and the whole day is just going downhill from there. Laura Pelkey: That's a big problem. Yeah. Mike Gerholdt: I know. Laura Pelkey: But that's the thought behind that. Mike Gerholdt: Sabrina, we didn't forget about you. It's usually Laura has a long laundry list of things to talk about, but I'd love to bring you into the conversation. First of all, I think this is your first time on the podcast, so tell us a little bit about what you do at Salesforce. Sabrina Simeroth: Yeah, thanks so much for having me...
/episode/index/show/buttonclickadmin2/id/41682270
info_outline
How Agentforce Helped Build a Food Waste Solution in Days
06/11/2026
How Agentforce Helped Build a Food Waste Solution in Days
Today on the Salesforce Admins Podcast, we talk to Parth Sevak, Director of Technology and Principal Architect at Incepta. Join us as we chat about how Parth built a multi-agent system designed to connect surplus food with the people and organizations that need it the most and won the Agentforce for Good Grand Prize at the TDX Hackathon. You should for the full episode, but here are a few takeaways from our conversation with Parth Sevak. The Hackathon project focused on reducing food waste If you listened to last week’s episode with Alexandra Iyer, you know that Agentforce for Good was a popular problem at this year’s Agentforce Hackathon at TDX. Contestants took on big issues like nonprofit volunteer coordination and disaster relief. That’s why I was so excited to sit down with Parth Sevak, whose project Harvest Bridge won the Agentforce for Good Grand Prize. Harvest Bridge is a multi-agent application that connects food donors with organizations near them. As Parth explains, food waste is a serious problem. According to the UN’s World Food Programme, about 318 million people are facing acute hunger today. “In North America, 30-40% of the food that is produced never gets eaten,” he says. So he decided that this would be the perfect problem to tackle for the Agentforce Hackathon at TDX. Simple integrations and out-of-the-box tools Under the hood, Harvest Bridge features multi-agent coordination between four agents to handle donor intake, food matching, volunteer logistics, and reporting analytics. While it sounds incredibly complicated, Parth is quick to point out that 80% of the work was done in configuration with out-of-the-box admin tools. Parth needed to write some Apex to do specific things like geo-matching, which he vibe-coded with the Claude plugin for Agentforce. Crucially, he didn’t have to write glue code to make everything work between Agentforce, Data 360, automations he built in Salesforce, Slack, and Tableau. “All of it just worked like a charm,” he says, “five years ago, that integration story would have been months, if not years.” How to get started building Agentforce solutions In just a few days, Parth was able to build an autonomous, multi-agent system that uses Agentforce, Data 360, Slack, and Tableau to match surplus food with local organizations and coordinate delivery in under 90 minutes. If you’re looking to get started with Agentforce, Parth recommends jumping on Trailhead as your first step. The Agentforce Specialist certification gives you the tools you need to start building, and then it’s all about getting your hands dirty. Make sure to listen to the full conversation with Parth Sevak about how he built Harvest Bridge and won the Agentforce for Good Grand Prize. And don’t forget to subscribe to the Salesforce Admins Podcast so you never miss an episode. Podcast swag Learn more Trailhead: Salesforce Admins Podcast Episode: Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins Podcast, we're talking with Parth Sevak about how a real world food waste solution went from idea to working system in just days using Agentforce. Drawing from a challenge that impacts millions globally, Parth built HarvestBridge, which is a multi-agent system designed to connect surplus food with the people and organizations that need it most. Now, this was part of the TDX26 Hackathon Challenge and what makes this conversation the most compelling isn't just the technology, it's how admins and architects can really orchestrate data automation, AI agents and human coordination together without months of integration work. We also get into what it means to design a trustworthy system where humans stay in control while AI handles scale and speed. So, if you've ever been wondering about how Agentforce changes the role of the Salesforce admin from builder to system orchestrator, this episode's for you. Be sure to subscribe, share the episode with your team, your friends, your local Salesforce admin user group and let us know what kind of real world problems you'd solve with Agentforce. But for now, we're going to get Parth on the podcast. So, Parth, welcome to the podcast. Parth Sevak: Thanks, Mike. Really glad to be here. Mike: Well, I'm glad to have you. So, if everything shakes out, the episode before this will be the episode with the Agentforce for Good People, but sometimes scheduling is what it is. But I was at TDX this year and we had Hackathon winners and you were part of the Agentforce Hackathon. And so, that's how I got connected with you. But I think before we get into that, I'd love to know a little bit about how you got started in the Salesforce ecosystem, what you do and let's go from there. Parth Sevak: Absolutely, Mike. Again, thanks for having me. So, the story of how I ended up in Salesforce is really interesting. That was not my plan. In fact, back in 2011, I was a fresh computer science engineering grade hunting for my first real tech off somewhere. And that time, the startup economy was just taking off and Java was the thing, the only thing in my perspective as far as I was concerned. And then my boss pulled me aside and said, "Parth, you are going to work on Salesforce." And I said, "Oh, what is Salesforce? I'm looking for Java opportunities." So, he made his pitch. "Apex is basically Java, you will feel right at home. And there is this thing called Dreamforce, massive event, you might get to experience it someday." And that's where you see a lot of enterprise innovation is going to come in. Basically, he sold it and 16 years later, here I am loving the challenge, loving the stretch, always finding ages I haven't touched yet and it keeps me motivated. Mike: He was a heck of a salesman. Java, here's Salesforce. It's just like Java. And if you're good enough, you might get to go to Dreamforce. That's awesome. So, go ahead. Parth Sevak: Yeah. And just to tell you what currently I'm doing. So, these days- Mike: Yeah, please. Parth Sevak: ... I'm working as a director of technology at Incepta Solutions where I lead data, CRM integration and agentic AI transformation for enterprise clients across financial services, retail manufacturing and pharma healthcare. But I make sure to keep one foot in hands-on building always. And that's how HarvestBridge happened at TDX, as you see. Mike: Yeah. So, let's talk about that. I mean, it's really cool. This isn't our first hackathon since we've come out with Agentforce. We've been doing hackathons and the early hackathons, I was a judge in quite a few and some of the really neat ideas that people were coming up with for the use of AI agents and some agentic use cases I think were really kind of interesting. I know we had that at TDX. So, I guess let's start off with the TDX Agentforce for Good Hackathon. What made you want to enter that to begin with? Parth Sevak: Yeah, to be really honest, it was again, my boss encouraged me because even I was not sure whether I would be attending the TDX in first place, but my boss was really motivated to join the party and he invited me. And then I realized, okay, if I register for TDX, there is an option to participate in the hackathon. And that's how my journey began. Mike: Oh, well, we made that awfully easy for you, didn't we? Parth Sevak: Yeah. Mike: I mean, I would like to think I'm a competitive person, but when it comes down to it, I think I really like watching competitions as opposed to competing. What made you think, "Oh, I'm going to get into this because the idea that I have is so great." So, tell me a little bit about what your idea was and what it solved for. Parth Sevak: Yeah. So, honestly, the topic I picked is not a fleshy topic, right? I picked the food waste, which is definitely not a hackathon topic. It's not a biotech, it's not a blockchain. But my heart said, pick it anyway because food is the most basic thing and somehow we managed to throw away nearly half of it while families a few blocks away are skipping dinner. And then again, I am a data guy, so please allow me to share some numbers here. Mike: Oh yeah, please. Parth Sevak: And that application for me, that 2.5 billion tons of food wasted every year, 783 million people are facing hunger. And when I read that and thought, "This cannot be right." And I check UN website, food banks' websites, and again, the numbers held up. And the on that hit really hardest is this number, which is in North America, 40% of food produced never gets eaten right here in our cities, whether it's San Francisco, Toronto, basically with our neighborhood. Mike: I mean, that's crazy. I know I've seen ... I forget the show. It was on Discovery Channel here in the US and they talked about ... I didn't know there were hog farmers out in Las Vegas, but there are and they work with the casinos. The casinos have all those buffets to get all their food scraps. I thought that was really, really fascinating. I guess you think about it and until you look at it on a larger scale, do you even understand how much food is produced and unfortunately how much is wasted? Parth Sevak: Yeah, totally, Mike. Mike: So, let's talk about your solution because it involves Agentforce. So, were you going to feed Agentforce some apples? That's a joke because you can't feed it apples. I mean, you could feed it apples maybe like an emoji. Parth Sevak: So, yeah, I think let me first of all piggyback on this one, this idea that this HarvestBridge as a idea, right? When you look at this project from the outside, it may sound like as a big AI project. We have four agents, multi-agent coordination, the whole team, but the reality on the inside is three of those four agents are about 80% configuration. And this is the Agentforce play in my opinion because I used agent builder topics, instructions, guardrails, then flow for orchestration, custom objects, validation rules, formula fields, like typical standard admin toolkit. And obviously, there was a 20% which is code, which is attacks actions for things like geo-matching. So, that also like I wipe coded with cloud plugin for Agentforce available. And what came back was the quality of a season developer with proper design patents, clean error handling, governance limit aware as I made sure to provide the right context. That is very important. So, anytime if anybody ever built a flow with a decision branch and a few validation rules, you can think the way you need to build an agent. The tools just caught up with you. Mike: Yeah. Well, actually we had a few presentations at TDX and the admin track from admins who are vibe coding and I've had a few people on the podcast talking about how they've vibe coded and just the product itself is just insane to think you can sit down and there's a plan and there's an action button. And even in the plan button, I was really impressed with how much Agentforce Vibes could give you back as an admin to really help you plan your application. Parth Sevak: Yeah, that is really empowering thing has happening just in front of eyes and not just that, but we are at the forefront of that innovation and definitely the Agentforce for Good is really the category that should motivate everybody to get their hand dirty for something to produce something really good. Mike: Yeah. So, let's talk about while you were building your application to deal with food waste, what was a point in time when you sat back and maybe learned something that you didn't know as you were building it? Parth Sevak: Yeah. So, before I answer that question, I need to tell you how I approach the build process if it is okay. Mike: Oh, please. Parth Sevak: Yeah. Okay. So, basically like Mike, to be very frank, I didn't follow a plan. I would love to say that I sat down on day one and map out a clean sprint like user stories and backlog, but that was not what happened. What actually happened is I just started building right away. So, I picked the first thing, which is a donor bot. This is the agent that talks to donors and captures surplus food. First I got that working and the moment it ran, the next question was obvious that, okay, now surplus is in the system in the Salesforce. Now where does it go? So, I built the matchmaker agent and once matchmaker was written in matches, the next question came up on its own that who actually picks the food up and delivers it? Who is the volunteer? That became logistics coordinator on Slack and by then, I had data flowing through the whole system and it was almost asking to be visualized and that become impact analyst on Tableau. So, overall, I ended up building four agents, each one revealed the next. And what made that look possible beyond Agentforce itself is that I had AI assistance alongside me the whole way, like not just for the apex spaces we talked about, but for the thinking too, like should this be one agent or two? What edge cases am I missing? Is this topic structure clean, less a solo build and a more long conversation with a partner who is read every Salesforce document kind of like ever published. So, when I started building on the Agentforce platform, I had some high expectations and let me tell you, like what really surprised me in a pleasant way is the breadth. I use Agent Builder for the agents themselves, the topics, instructions, custom actions. Then underneath, I relied on agent script for the deterministic safety rules. So, things like allergens and expiry windows are not left to the LLM to decide. From there, I brought an Agentforce voice for the call-in donation capture, which I think just became GA recently, which I think, yeah, an intelligent context handled passing food details out of photos that donor send in. All of it was sitting on Data 360, which held the unified profiles of donors, recipients, and volunteers. Here is the part that genuinely caught me off guard. I didn't write any glue code between those layers, like an agent would hand off to a flow which will call an apex action that will update the records in the Data 360 and that would trigger a Slack message. That would feed back into another agent's context and all of it just worked like a charm. And if I reflect like five years ago, that integration story would have been months, if not years and this made me possible to deliver something so amazing in just few days and that was my wow moment from the whole build. And Mike, if I just like tell you another perspective that the other thing I was nervous about going in was hallucination because I am building four different agents and then you have obviously hear the horror stories, right? But between agent builders topic structure, agent script for hard rules and clear instructions, that's how I make sure that my agent behave very well. So, food safety rules around allergens and expiry are not something that I would let an LLM to decide. I would make sure to enforce them deterministically at the architecture level and for that I leverage agent script and thank God, that agent script work really well and where I would love to see things improve is just the debugging because when an agent's reasoning across topics and data sources, tracing what it actually did is still a bit difficult. So, the tooling is getting better, but its place still I'm watching. Mike: Yeah. I do an Agentforce Now workshop every month and I always try to point out when we're building it and preview how you can go through and see what the agent is doing and how it's deploying its sub-agents. And I think with everything we're still learning what AI is and how to debug it and it's this interesting intersection because we want the intelligence and the context and the engagement of AI, but I think people got really hooked on how perfect a bot would respond and a bot would respond because it's always A, B or C and we gave it those answers. And the nice thing about AI is it doesn't necessarily have those answers, but it can think independently, but we still want that control. So, it's like building the perfect employee. Parth Sevak: Yeah, absolutely. And that's why, like as I said, Mike, the deterministic approach is very significant and particularly, I would kind of rely on agent script that really gives that control back to the human or admins or architects so that they don't need to basically do the guesswork that, okay, what will be the response of agent if I do this prompt versus that prompt? It can simply be predictable. So, that is the cool thing I would say about the agent script and what it makes possible now in the reality of governance. Mike: So, I think one thing that's really cool about hackathons is it's kind of blue sky and green field. You can come in with a solution and like in your case, it really solves a real world problem. If somebody is listening to this and thinking, "Wow, I'd really like to get started with Agentforce," what was the first thing that you did to get hands-on with Agentforce and start understanding the product to the level that you do now? Parth Sevak: Oh, I think I don't recall exactly the date and time, but I think it was I think a couple of years ago when there was already like Agentforce discussion has already began because I was active in the community and thanks to Trailhead. And I basically started my journey to equip myself about like what is this best Agentforce, right? And then I did few modules and ultimately I think last December, I got certified in the Agentforce as Agentforce specialist. So, that really gives me clarity that okay, just not about like, okay, what I can build for the demonstration purpose, but also for me, it's very important that I can actually pass on that knowledge to my team so that they can ship the products or ship the agents that is really the kind of like configurable and scalable across the systems, not just one particular cloud or system or CRM. Mike: Yeah. I mean, anytime I need to learn something for a demo or for a presentation I'm putting together, I usually turn to Trailhead first and kind of walk through it and get an idea of what the product can and do and how I can configure it. So, I'm right there with you. Even Salesforce people still learn on Trailhead. Parth Sevak: Yeah, that's amazing actually. I call it as a live report, it's always live. You never get any stale recipe or stale dishes. So, that means everybody, whether it's a employee of Salesforce, partners or customers, everybody can rely on Trailhead for the real time information for sure. Mike: So, moving forward, we have a little event in the fall that we do called Dreamforce that you mentioned. Obviously, none of us have a crystal ball. Well, I'm sure a few people in Salesforce do to know what we're going to show, but what are some of the things you would love to see this year at Dreamforce? Parth Sevak: Okay. So, as I said, I have been part of the Salesforce ecosystem for almost 16 years and what really amazing to see is that the platform never sits still. So, when I started, here is the context, Mike, what I'm talking about is when I started we were building the S controls and it came to Visualforce. Mike: Yeah, that's back when I started too, called them Superman controls. Parth Sevak: Yeah. Then Visualforce, like proper MVC, controllers, pages, then Aura framework. And my first test of real component-based DUI was that Aura and then Lightning Web components. And I remember thinking, okay, this changes everything. And now 2026, we have got React running on Lightning Web Runtime along with the Headless 360 and agents that reason and act on their own and every leap has bigger than the last, right? So, it is the one ecosystem I have worked in that's never stopped becoming more interesting. I will make sure like a kid, I always go without any expectation that, okay, oh, what I'm going to get out of this conference because I know whatever will be there, it will be super amazing, super productive and...
/episode/index/show/buttonclickadmin2/id/41598370
info_outline
Agentforce for Good Shows the Power of Inclusive Innovation
06/04/2026
Agentforce for Good Shows the Power of Inclusive Innovation
Today on the Salesforce Admins Podcast, we talk to Alexandra Iyer, Director of Marketing Strategy and AI Transformation, and Global EVP of Abilityforce at Salesforce. Join us as we chat about the Agentforce for Good Hackathon at TDX and what happens when technology, accessibility, and community come together to solve real-world problems. You should for the full episode, but here are a few takeaways from our conversation with Alexandra Laxmi Iyer. Agentforce for Good expands AI beyond business problems This year, we added a new twist to the types of problems you could solve for at the TDX Hackathon. We called it Agentforce for Good, and it offered participants a way to work on some big problems: food insecurity, nonprofit volunteer coordination, disaster relief, and more. That’s why I’m so excited to bring Alexandra “X” Iyer on the pod. She’s the Global EVP of Abilityforce, Salesforce’s internal business unit for people with disabilities and their allies. They’ve been running an internal accessibility hackathon for years, and Agentforce for Good grew out of a desire to open it up to the community and broaden its scope. “Builders who probably never thought of themselves as social impact developers shipped working Agentforce solutions for all sorts of big problems,” X says, and 62% of this year’s Hackathon entries were solving for Agentforce for Good. Inclusive design creates better technology for everyone “When we are challenged with designing for the edge, you make the center better,” X says. Finding challenges that force you to push tools like Tableau, Slack, and Agentforce in new ways helps you uncover capabilities that you might not have otherwise thought about. As X likes to put it, “Good design is just good design, full stop.” Going forward, X and her team are looking for ways to expand Agentforce for Good beyond TDX. Consider this a call for participation, and she encourages you to get in touch to volunteer or bring Agentforce for Good to a community event near you. Lived experience is a valuable design credential “One of the main things I would love for people to take away from our conversation is that your lived experience is a credential,” X says. “It's not a distraction.” After all, designing around new challenges is how we come up with innovative solutions that nobody else would have thought of. Your unique perspective is valuable. Make sure to listen to the full episode for more insights from X. Next week, we’ll hear from the winner of the TDX Hackathon, so make sure you’re subscribed to the Salesforce Admins Podcast. Podcast swag Learn more Trailblazer Community Group: Admin Trailblazers Group Social Love our podcasts? Subscribe today or ! Full show transcript Mike: This week on the Salesforce Admins podcast, we're talking about what happens when technology, accessibility, and community come together to solve real world problems. I'm joined by X or X, who is the director of marketing, strategy and AI transformation at Salesforce and Vice President of Abilityforce to discuss the Agentforce for Good Hackathon that happened at TDX. Now we're going to find out that it started as an employee-led accessibility initiative. And has grown into a community movement bringing together admins, developers, partners, and customers to build solutions that address challenges like food insecurity, disaster relief, and volunteer coordination. We're going to talk about why designing for inclusion leads to better outcomes, how AI can help scale impact, and why your lived experience might be one of the most valuable design credentials you have. So if you're thinking about how data automation, AI agents work together to create meaningful change not just inside your organization, but in the world around it, I promise you this episode is for you. So let's get Alexandra on the podcast. So Alexandra, welcome to the podcast. Alexandra: Thank you for having me, Mike. Mike: I think it's going to be a fun conversation because we're talking about Agentforce for Good today. So let's get started to learn a little bit about you and your path to Salesforce and your path to the Agentforce for Good Hackathon. Alexandra: Absolutely. Thank you for asking. And by the way, I go by X for short, so feel free to call me X. Mike: Perfect. X: I'm the director of marketing strategy and AI transformation for our customer success and partner marketing team here at Salesforce. And I'm also the vice president for Abilityforce, our employee resource group for people with disabilities and their allies. And when we're talking about the Agentforce for Good Hackathon, this is really a moment where these two worlds actually collided. Normally, they wouldn't collide, but the hackathon is genuinely where they did. I come from 20 years of go to-market experience. I'm not a builder by background. I actually got curious in a marketing role about the products that I was marketing and how they worked. So that curiosity pulled me into the platform, into development, into force certifications that I did not see coming. And then, I went from talking about technology to building on it and that changed everything. I believe that the AI era is only worth building if it's built for everyone. That's not a tagline for me. It's a design requirement. And I truly feel that admins have always known that. Admins are the ones closest to the humans using the platform, the problems, the friction, the gaps. And I also believe they're the closest to the solution. So I think it's not a support function, it's a superpower and I'm really happy to be here. Mike: Yeah. Well, I agree with everything you had to say, X. I do agree that admins are very superpower. I also think just in general, when we think about technology, it's not how do we roll it out for some people? It's how do we roll it out for everyone? And I remember this is a long time ago, but when I first joined a company that did workplace assessments, I remember they said, "Well, when creating the test, we have to assume the person doesn't know how to use a mouse." And I remember thinking to myself, this is ... closed-minded is the wrong word, but I just was unaware. And I was like, "Well, who doesn't know how to use a mouse?" And they're like, "Well, you don't understand." And I was like, "Oh, that is a huge challenge." And sometimes until you get someone else's perspective, do you really understand like, it's not that you've been living under a rock, it's just too often sometimes people assume their world is just like everyone else's world and it's not. So there's a Mike side of I had to remember that not everybody knows how to use a mouse sometimes. X: Well, Mike, frankly, I consider that the main dish. I don't think it's a Mike side. I think that if you're designing for the default user, it's not really good technology and that when you optimize for the average, you're excluding by design. So I think it's the main dish and it's part of the reason why the Agentforce for Good Hackathon even exists. So to give you a little context, three years ago, the Agentforce for Good Hackathon was an internal-only, employee-only hackathon led by Abilityforce. I mentioned earlier Salesforce's business resource group for people with disabilities and their allies. And then, last year we said, "Why does it have to be about accessibility only and why does it only have to be for employees?" So then we opened it up to the community. We had partners and customers and employees all building on the platform, really stretching the platform, bringing us to TDX this year, where builders who really probably never even thought of themselves as social impact developers shipped working Agentforce Solutions for food insecurity, for nonprofit volunteer coordination, you name it. So when we all come together to threshold platform for everybody, not the default user, we're really shipping great technology and boy, did the admin community really show up for this. Mike: Yeah, no kidding. And just as kind of a teaser, next week on the podcast we have the winner of the hackathon to talk through their application. So that was a fun conversation, but let's dive into what some of the things that you did around the hackathon, some of the stuff that you saw and what some of the participants tried to tackle. X: Absolutely, so we had ... so a little fun fact for you is that of all of the submissions for the TDX Hackathon, over 62% of them self-selected to say, "I want to solve for the Agentforce for Good." It wasn't required. And then, 50% of the Agentforce for Good projects were participants could submit in multiple categories, but 50% of those 62% of the projects were only for Agentforce for Good. They solved things from disaster relief to supporting teams post-addiction to food rescue, truly really pushing the boundaries of the Salesforce platform. Mike: Yeah, absolutely. And I always think sometimes that we're trying to solve problems with technology where it's just how do you layer in the technology? But I do feel ... and I was there when they gave the awards, I do really feel that the integral solution for a lot of these works the technology along with the process that is also needed. There's just things you can't do without the technology that when you layer that in, wow, it unlocks a different world. X: Yeah, absolutely. I think that when we are challenged with designing for the edge, you make the center better. And so I'm sure that some of these solutions that put together Tableau and Slack and Agentforce have uncovered some capabilities that maybe we might not have thought about, whether it's for a good cause or not. So I do think it also allows very special kinds of developers and admins to come to the surface as well. Mike: Absolutely. So in your work with the community and around the community, what are some of the events that you go to? What are some of the presentations and content that you put out there that people find valuable and useful? X: Well, I mean, I'm only starting to get into the conference circuit or the community circuit, to be honest with you. I've been kind of- Mike: I like that we call it a circuit. X: Yeah. Mike: Get around the circuit. X: I mean, for me, it's something that I've always been ... and this might be a little too raw, but I am an open book, Mike, so hear me out here. I have never, ever had the ... what's the word I'm looking for? It's kind of like, I guess confidence is the right word. I've never been raising my hand to say, "Oh, I should submit and speak," or, "I should fight to attend this event because this really matters to me." And it's only recently where I've started to get my legs a little bit more to do that. I've published a couple of articles on LinkedIn, building with Cloud Code, using Slack, Slackbot, all these things. And so, I'm just starting to get out there and really getting exposed to the possibilities of our platform. I actually don't know how to answer that question, except for I'd love invites, I'd love to know what the community finds interesting and I'd love to facilitate doing good in the world, doing as much good as we are solving business problems. Mike: Yeah. I think ... I mean, you're also just taking the first step. Some people ... I'll just go, but I'll never present. And I always encourage people, even ... you don't have to go to a big conference or you don't have to present at Dreamforce, but even getting up and sharing things at your local user group, the thing I'm reminded of, somebody needs to see somebody like you presenting. X: Well, thanks for saying that. I'm actually presenting at Connections this week. Yeah. It's my first real speaking session and we're talking about how we've used Slack and Slackbot to scale top level support to our incredible partners. We have over 13,000 partners in the Slack community and we have a lot of different skills that we're using to help our partners go to market faster in a more customized personalized way. And so, we'll be talking about that. But back to the hackathon, the one thing I did want to underscore is that Salesforce has a total of 16 equality groups from Abilityforce, to Neuroforce, to Asiapacforce, to Outforce, BOLDforce. And we all came together for this hackathon and we're going to continue to do that. So likely, you'll see us at Dreamforce and at TDX again. So I would love to have the community just continue to support this and participate and start the platform. I'll say that our community is proving that intersectional volunteer-led initiatives drives higher engagement and faster product adoption than traditional top-down motions. And so, I just want to have a call to participation. If your community or your listeners want to participate, we're definitely open to having more volunteers support and would love to see these at our community events as well. Mike: Yeah. I've already been to a community event MidAtlantic Dreamin', this year in Philadelphia. And I love going to those events because it is all community presenting and really showing their perspective on giving different solutions and tackling different challenges. And it ranges from technical through just giving presentations to your executives and having the confidence to walk into a boardroom and really working through that, not all the presentations are exactly technical. And so, you can learn different skills that way, but I appreciate you bringing that up. That's always very good and good for you getting up on stage. It's okay. I do think sometimes ... I've spoke on a lot of different stages. Sometimes it's the smallest ones that are the hardest because once you get up on a big stage, there's just so many people that your brain can't absorb it. It's crazy. X: Yeah. Well, I guess my little theater session at Connections will have to do, but- Mike: You never know, there could be 200 people there and do a little theater session. X: I know, I know. My goodness. Yeah. What I'm curious about, Mike, from your perspective is why do you think ... Here I am, I'm asking you a question. Mike: Please. X: Why do you think we had such incredible participation? Because it really was humbling the amount of community support we got from folks joining the Agentforce for Good Hackathon. Mike: I thought about that too and I think it's maybe a couple of things. One, I've been a part of either on the team where people around me are planning the hackathon. I've been in the judging room sometimes for a few of the events and going through, watching the submissions and watching the integration of how did they use Agentforce and what was the solution they were trying to solve. I feel like the opportunity for solving things that really provide, I'll call it exponential value to the community, is so great. And it also kind of, in some respects, opens up the creativity because depending on how long you've been a Salesforce admin, how long you've been a Salesforce developer, you might not have all of that kind of exposure into different businesses and different processes. I know for a long time, a lot of hackathon people were tackling things in the medical world and I won't give away ... Well, I can give away the winner because we all know it. But the unique solution that they come up with, you have to think of it's not what is the technology solved for, it's what was the issue and the challenge that provided the biggest gap that technology proved out to do the most good. And I just think after talking with the winner and seeing that solution, I think a lot of people just genuinely found a lot of really satisfying things to build when it comes to solutioning ... I'll call it solutioning for good, as opposed to solutioning for profit. X: Right. Mike: Because then you're like, wow, if we can do this, this and this, because the gaps are always there and they're always huge because nobody ... For lack of a better terms, nobody is maximizing good for profit. X: Yeah. Mike: And so, the thinking of just different things around animal adoption or adoption shelters or food and food insecurity, there's always communication gaps there. And the biggest thing that AI we found and Slack, and some of these other tools, but the biggest thing that AI solves is communication. I was on Amazon the other day just not as a tangent, but kind of ... and they have this new button now you can click and it generates kind of an AI overview of the product and some of the common answers to the questions that they have. And I thought to myself, that gap probably didn't exist, but AI solved it and AI is able to communicate with us. And I think that to me for things that do good and help others, communication is always the key and it's always the biggest gap because communication at scale never happens. X: It's interesting that you say gap and it's making me think of something I'd love to share about our employee hackathon. So we are still doing our employee version of the Agentforce for Good Hackathon and this year, we're adding an AI fluency track. So we have our traditional builder track, and then we have our AI fluency track and you don't have to be building an agent to build something powerful. Mike: Right. X: And so, we want to provide an opportunity for admins and marketers and all sorts of folks to be able to confidently collaborate with AI to give our users agency to drive impact at speed and scale. And so, I think admins do a really great job at understanding human like you were saying the Amazon button and clicking that button as an admin, you kind of know why the user might click it or why they might click the wrong one because of maybe where it's placed or is it accessible or things don't get filled out correctly and you know how to create some workarounds. And so, I think the AI fluency track for us is about really bringing more of that human element back into the AI. So I'd be curious if the community would be down with participating in an AI fluency track where it's like writing ... like it's not about building something. Maybe it's like the most artful skill, Slackbot skill, or maybe it's a killer Gemini prompt or something along those lines. But I think you mentioning the gap really made me think about how I want AI for all technology that empowers everybody, but I also don't want to leave anyone behind. Mike: Right. Yeah. I mean along those lines, I was talking today with my manager and we were discussing something and she's like, "So what do you use?" Because at Salesforce we have a wealth of tools. I think comparative to ... I've talked with other friends and like, "Wow, you get to use that and that and that?" And I'm like, "Yeah, and there's probably more that I don't know about." And they're like, "Geez, we don't even have ..." So that part alone was ... I was like, "Yay. Well, I'm glad I have a wealth of resources." But she asked what I was going to use it for. And I said, "The biggest thing that I try to use AI for in looking at a lot of data on sheets or 10, 15 page documents, what are the blind spots for the stuff that I don't normally pick up?" And that to me was the greatest prompts that I could use. And back to some of your Agentforce Hackathon stuff, I think actually that's some of the biggest opportunities that admins have across their org is we always look at, well, how can the agent improve this or that? Boy, I would just love it if ... how could the agent just look at the record somebody created and be like, "Yeah, Jim, that's not going to cut it." X: Absolutely. Mike: "You left a bunch of fields blank and you know what, those fields are there for a reason. Go back and fill them in." That's what I would want. I would want a little snarcastic clippy coming up and being like, "I think you can do better." X: Yeah. Mike: But it's also not, how do I make myself perform in a greater capacity or increased speed? Yes, that's part of...
/episode/index/show/buttonclickadmin2/id/41523350
info_outline
Salesforce Admins Can Reduce Risk With Proactive Security
05/28/2026
Salesforce Admins Can Reduce Risk With Proactive Security
Salesforce Admins Can Reduce Risk With Proactive Security Today on the Salesforce Admins Podcast, we talk to Kate Lessard, Lead Admin Evangelist at Salesforce. Join us as we chat about why security is the foundation for how data, automation, and AI work together. You should for the full episode, but here are a few takeaways from our conversation with Kate Lessard. Why strong security is proactive, not reactive Security can often feel like the elephant in the room. Everyone knows it’s important, but the amount of work needed to do it right can feel daunting. Thorny problems like accumulated tech debt and organizational inertia can make you feel like you’re better off not talking about it. That’s why I sat down with Kate Lessard. This month, she ran a workshop called Security in Action to highlight the simple steps you can take to strengthen the security posture of your org. She got hands-on with an example org to demonstrate how to use Health Check to identify and fix security problems. It’s all about taking a proactive approach to security, rather than waiting for something to happen to you. Your Health Check score is a security action plan “Health Check is no longer just a list of settings for you to review,” Kate says, “it’s your dynamic risk mitigation dashboard.” Issues are sorted into four categories: high-risk, medium-risk, low-risk, and informational. There is also a status to rate the level of urgency for each issue: critical, warning, or compliant. Health Check is also customizable. If your organization’s security policies are different than the Salesforce Baseline Standard, you can download an XML file and tweak the criteria. You can compare your policies to what’s recommended by Salesforce, and maybe identify some low-hanging fruit. In short, your Health Check score gives you a prioritized list of which security issues need to be addressed first so you can walk into a meeting with stakeholders with a solid plan of action. Helpful reports for user management Security and user management go hand in hand, and Kate recommends some reports that admins can run to help with governance. First of all, the Active System Administrator Report can help you find users who might have more access than they need. This can often be an issue in older orgs where it was easier to give someone admin access than to sit down and solve the permission problem. Kate also likes to run a report on Reports, to keep track of what her users are interacting with the most. As Kate says, it’s all about making a shift towards a security model built around permission set best practices. As admins, we need to find a way to fit security seamlessly into our organization’s business processes, and vice versa. There may be an upfront cost, but it’s all about making security easy in the long run. Listen to the full conversation for more from Kate about security and Health Check. And don’t forget to subscribe to the Salesforce Admins Podcast so you never miss an episode. Podcast swag Learn more Salesforce Admins Blog: Kate Clicks Through It: Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins podcast, I sit down with Salesforce Evangelist Kate Lessard to unpack why security is really no longer a side conversation for admin, but the foundation to how data, humans, automation and AI all work together. We're going to cover her new security workshop that she led last week, and talk about health check upgrades, permission set security models, and of course how Salesforce admins can move from reacting to security problems to proactively designing trusted systems. We do touch on a little bit of governance, user access, and why secure data is the backbone of every successful AI implementation. So if you've ever wondered how modern Salesforce admins evolve from feature builders into stewards of trust, this episode is for you. And with that, let's get Kate on the podcast. Kate, welcome back to the podcast. Kate Lessard: Hey, thanks for having me back. Excited to be here. Mike: Well, it feels like a lot of relevant things for admins are coming out of your camp lately from True to the Core Deep Dive to last week's security and action. I feel like there should be like a thunderclap after that. Security and action. Dun, dun, dun. Kate Lessard: Yeah, absolutely. Data and access. Mike: Right. Mm-hmm. Yep. Like a comic book hero. And then you got to do the comic book land. Anyway, totally off topic. Look at that. 30 seconds into the podcast, we're already in comic books. People- Kate Lessard: I mean, I am here for it. Admins are superheroes, especially when they are securing their orgs. Mike: We are. So let's talk about what that first workshop was, and what you covered, and how it went. So tell me a little bit more, tell everybody a little bit more about what that workshop was. Kate Lessard: So in the Security and Action workshop, we were really focused on data and access and using HealthCheck as our guide. So essentially we started off with some security basics knowing that much of our audience was at different levels. So we had people joining us that are brand new admins that are working on their first certification. And then we had people joining us that have been in the ecosystem and in a Salesforce role for more than 10 years. So wanted to make sure that we had a strong foundation and that we had reviewed some security foundational knowledge base points for everybody to get on the same level. And then we got hands-on in an org that just didn't have a great health check score and had some security concerns that we went through, and hands-on adjusted together until we improved our score, we better secured our org, and just increased our security posture. Mike: Cool. I didn't hear Agentforce in there and we're in the age of AI. Kate Lessard: Yeah. So I do think we didn't specifically touch on Agentforce in this first workshop. We really wanted to focus on that strong security base where it applies to all of your org. And that might mean that it applies to your users, both human and agent, but really focusing in on that prime security. And then we do have plans in the future to enhance this and take this to the next level and really expand on some of those agentic guardrails. But I think that it's just really important to have that foundation first. Mike: Yeah. I mean, all of it bases around good, clean data and secure data. Kate Lessard: Absolutely. And you're not going to have a successful Agentforce implementation without that. That is the foundation point that's going to set your organization up for success using AI. Mike: I did the Agentforce Now workshop that week, and I always emphasize the importance of filling in description and metadata fields as well. Kate Lessard: Yes, hugely important. Mike: So one of the things, it's really cool the workshop pivots all around HealthCheck. And I know having worked some of the Q&A, people were like, "Wait a minute, I thought HealthCheck went away." Kate Lessard: Yeah, HealthCheck has not gone away. It is free for admins to use and it actually recently got some pretty impressive and exciting upgrades that we spend some time on in the workbook. So it's no longer just a list of settings for you to review. It is really dynamic and serves as your risk mitigation dashboard. So you can do things like not only configure the specific settings for your org security, but you can also set up email notifications for system admins or anyone who that you would like to receive notifications when your security score changes. So maybe members of your IT team, your security team, if you work with a governance team, making sure that they get notifications because as you know, security is a team sport. I think the coolest thing that we do in the workshop and that I really want everybody to be able to take advantage of is you can actually export the standard Salesforce baseline and customize it to your own organization's security criteria. So if you have different security criteria like maybe your password policy has a minimum of 11 characters at your organization, the Salesforce baseline has eight characters. That is a change. And you want to compare your Salesforce security settings against your own organization standards, and you now have the ability to do that, which is just incredible. Mike: Yeah. And it's not like the way that you walk through it, it's not that daunting. I mean, is it an XML file that you download? Kate Lessard: Yeah, absolutely. So you don't have to start from scratch, which is the really nice thing. You can actually export the standard Salesforce baseline. It is an XML file. In the workshop, we walk through what the download looks like and how to actually make the edits. It's pretty easy to read. And even in the file, there's a link to help notes so that you know exactly what types of formatting to use when you're editing the XML. And then you can just save it as your custom, re-import it, and set it as your default. Mike: Yeah, I thought that was really cool. One other thing that you dive into is, and of course it's set up because it's a workshop, but number of admins that... Kate Lessard: Oh yeah. Mike: Or number of people that have the Salesforce admin profile. Kate Lessard: Absolutely. So everybody's favorite admin horror story that you log into an org for the first time and take a look and realize that you have just a completely disproportionate number of system admins and folks that are over-privileged just because it was easier to give them that permission than to really sort through a proper permission set model. And in our org, we have the very scary informational security setting letting us know that we have 100% of our users as system admins opposed to the typical 5% that you see in the standard baseline. So we address that and we talk about who really needs admin permissions. Mike: So I mean, let's expand upon that because we've had that idea of delegated admins as well. So they wouldn't have a system profile or a system administrator profile. Kate Lessard: That is correct. Yeah. You might have your delegated administrators that are taking certain tasks for certain teams, but that doesn't mean that they have the full system admin profile. It means they're a delegated admin and they have certain admin responsibilities that they take on, but it does not give them the keys to the castle. Mike: Very important. Very important. With HealthCheck, I think it's always one of those big discussion areas because there's different levels that we call out. We have critical. What are some of those stages? Non-critical, informative. Would you as an admin getting started approach HealthCheck as maybe it's like a topic we should bring up in governance? Kate Lessard: I absolutely think it's a topic we should bring up in governance. And it really is set up well to help you prioritize. So if you're going into a governance conversation or maybe a meeting with your security stakeholders, and you want to present different actions that you would like to take or approaches and settings that you'd like to address in your org, it's broken down by high risk, medium risk, low risk, and then informational. And then in each of those different categories, we have it called out what is a critical status, what is a warning status, and then where you're compliant. And so you might want to prioritize your high risk critical items, and then you could share that information of what your value is versus that baseline so that you can provide a really strong recommendation about where to take action to better secure your org. Mike: That makes sense. You've been doing a lot of security stuff lately. I mean, you've had some workshops. Outside of this, we had the True to the Core Deep Dive. What are one of the areas that almost consistently comes up as a theme that really maybe this year admins could address the most? Kate Lessard: That is a really great question. I think we've seen it in the True to the Core Deep Dives that we've had. We had one recently on security and user access. And I think those are two things that go hand in hand and something that comes up consistently. It was also a major discussion point at our admin day of security before TDX. We had a day zero event with several admins and that was just a common conversation as well. Really making that shift towards the best practice of having a permission set led security model, what that looks like for your organization, how to get there, what tools are available to help. I think that things like user access summaries, which we dove into in the workshop as well last week. There are just so many tools that can help admins better move to that permission set led security model. And I mean, I don't have to tell you that security and user management really go hand in hand, and oftentimes are interchangeable topics about how we can better secure our orgs and create a better user experience as well. Mike: Absolutely. And being proactive on topics that come up, one of the things that you cover that I really enjoyed, this is also, this speaks to how long I've been in the ecosystem. It wasn't until I joined Salesforce that I think you could do really in depth user reports, basic reporting was available, but one of the things that you create is the active system administrator report. I'd love to know, I mean, you were an admin out in the world more recently than myself. Were there reports that Kate always created to help her understand her users outside of just if they had a license or if they didn't? Kate Lessard: Yeah, absolutely. I think that the active system administrator report is a great one to call out, but it is looking specifically at users that have that system admin profile. And you might have other concerns about your users or things that you're checking up on them and what they're doing and what they're using. I loved to create the report on reports to get little snippets and information into what reports my users were using. I found that to be really helpful. And also there is a great Salesforce Labs report package about different administrator reports to help you get a little bit more insight into your user activity. So I think that something like that is really helpful if you don't have advanced security options to pinpoint that user activity for you. Mike: Yeah, that definitely makes sense. In addition to knowing when people log in and when they don't, it's also what are they doing? Because I remember I did an implementation and they were adamant about having a login component on a dashboard. And I had one user that I, to this day, I think all they did was wake up, check their email, and then log in and out of Salesforce because they were always head and shoulders above everybody else. They'd have 300 logins for the week. Kate Lessard: Oh, interesting. Mike: I'd be like, "Are you just logging in, updating a field, and logging out?" And they were very dodgy about their answers, but I think that's what they were. I think that's what they were doing because they liked being at the top of the board. Kate Lessard: That is hilarious. Mike: And I always had to reframe the conversation with executives of, we have to look at the entire dashboard, not just logging in because it could be meaningless. Kate Lessard: Right. They're just like logging in, logging a single activity, logging out, coming back in. Mike: Refreshing a dashboard, refreshing a report, and then that's it. Kate Lessard: Oh my goodness. Well, and then the other concern is where are they logging in from, if we're talking about dodgy behavior. When I was an admin out in the wild, one of the stories I like to tell about why security is so important. I worked for a mental health hospital system, and as you can imagine, we dealt with a lot of PHI. And I noticed some funky login IP ranges, and it turns out that someone had given a local college student access to their Salesforce credentials and was having them log their activities for them. Mike: Uh. Kate Lessard: Yeah, I know. And thankfully they didn't actually have access to any PHI because we had a good security model set up. However, obviously huge concern and something that Salesforce was able to help us identify because we were able to see those different login IP ranges, spot what was going on, and address it, and prevent it from becoming a big security concern, which I feel like that's really one of the big takeaways that I... If you asked me what I wanted people to take away from this workshop, it is to shift from being reactive about your security and just waiting to become a statistic to really being proactive and getting ahead of things and making sure that your org is secure and that you are addressing those risks versus waiting for them to happen to you. Mike: Yeah. I mean, to that point, I often look at things that are security that don't sound like security. And one of them is process management. So to me, that sounds like there's a complete separation between what executives expect in Salesforce and what the actual process is. Because the process, the technology should support the process that's needed, and here it sounds like it's burdensome to the process. And that to me is a security risk. I mean, if you don't have the process ironed out so that it feels natural, every action has a deliberate and equal technology component, then the security's going to fall apart. Much like a Salesforce admin shouldn't learn about a person being separated from a company four days after they've left the company. They need to be part of the off-boarding or onboarding process. They don't need to know why, but they need to make sure because that person should or should not have access to that system. Kate Lessard: Absolutely. I think that it is certainly a role of power and responsibility because you are getting that notification, best case scenario, to freeze that user. And again, you don't need the why or the explanation, but to have an actual process in place to be able to continue to secure your org so that after someone's left an organization that you're able to say, "Yes, this is still secure, this is not a risk." And you know you're not maybe going through a full deactivation process right away, but that ability to freeze that user and be able to take action is just so important. Mike: Absolutely. Well, Kate, I appreciate you coming on the pod and helping admins keep all of their data secure and their org secure. Kate Lessard: It is my pleasure. I mean, I love to talk about security any chance I get, and I think that we have so many brilliant people on our security team at Salesforce who I'm always learning from and happy to partner with. And this workshop was just a real labor of love, and I'm so happy that so many people were able to attend last week and glean the information and be able to take that and go use HealthCheck and better secure their actual orgs, not just our fake, very poorly-secured org that we fix and adjust in the workshop. Mike: Yeah. I mean, it works because you can spot things very easily because I think in the real world, sometimes things aren't as obvious as they should be. I know the biggest question that we can answer, and we're doing it at the end on purpose, will there be more of this content? Kate Lessard: Yes. So I can't give you a date, but we are planning to continue this on a monthly basis. I do think that there are plans to expand the content as well. And you'll also maybe catch us doing these workshops hands-on at some community conferences over the next year. Mike: Ooh. See, even more of a reason to go to community conferences besides the fact that they're super fun and held at really interesting locations. Kate...
/episode/index/show/buttonclickadmin2/id/41444150
info_outline
Can AI Help Salesforce Admins Build Apps More Efficiently?
05/21/2026
Can AI Help Salesforce Admins Build Apps More Efficiently?
Today on the Salesforce Admins Podcast, we talk to Nick McOwen, Senior Salesforce Administrator at Alpine Intel. Join us as we chat about his path to Salesforce and the TDX workshop he gave about the development lifecycle, sandboxes, and data masking. You should for the full episode, but here are a few takeaways from our conversation with Nick McOwen. Nick’s unconventional path into Salesforce Nick is the second touring musician I’ve had on the show this month—I promise I’m not raiding a recording studio somewhere just to find podcast guests. He was waiting tables in between gigs when a guest called him over to ask if he might want to try something different. A chance encounter turned into an entry-level job and, eventually, an admin certification. I caught up with Nick fresh off his workshop at TDX, where he shared how he uses sandboxes and data masking to build new agents and apps for his organization. Learning better development habits and sandbox management They say every warning sign has a story behind it, and the same goes for best practices in Salesforce. Luckily, Nick had Salesforce MVP Kelly Bentubo around to show him the ropes. He learned about the importance of consistent naming practices, managing user expectations, and having a structured deployment process instead of building in production. Recently, Nick was tasked with building a new recruiting app for his organization. He was able to spin up a sandbox with an app they had already built and, using that foundation, quickly reconfigure it to meet the new requirements. Once the app was in good shape, Nick moved it up to a staging sandbox environment for testing. There, he could copy data over from production and use data masking to keep everything secure. Once everything was thoroughly vetted, it was finally ready to be deployed into production. How Agentforce Vibes can help admins collaborate with developers Recently, Nick’s been taking advantage of Agentforce Vibes to work more closely with his dev team. He was able to write an Apex class and, while the code isn’t perfect, he was able to go through it with a developer to learn what was working, what wasn’t, and why. “It was a great launching point,” he says, “something that would have taken days was written in an hour.” For Nick, the most important thing admins need to do to get the most out of Agentforce Vibes is to learn the basic underlying principles of Apex and coding. It’s just like using a calculator—you still need to have some way of knowing if the answer you’re getting is in the right ballpark. Make sure to listen to my full conversation with Nick for more on sandboxes, data masking, testing, and why AI is a new opportunity to grow. And don’t forget to subscribe to the Salesforce Admins Podcast so you never miss an episode. Podcast swag Learn more Salesforce Admins Podcast Episode: Salesforce Admins Podcast Episode: Salesforce 360 Blog: Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins podcast, I'm joined by Nick McOwen, which means now I've started a trend of having former musicians who become Salesforce admins as guests. Anyway, Nick is going to show us how he went from touring in a band and waiting tables to leading Salesforce projects that involve sandboxes, data masking, deployment processes, and AI assisted development. We talk about the early build it in production and hope for the best admin days, how Agentforce Vibes is changing the way admins approach coding and why today's Salesforce admins are becoming orchestrators of systems instead of just builders of features. There's also a little Apex talk and surprisingly deep analogy involving semi-trucks and AI because you know my analogies and a confirmation that developers will always think their code is prettier. So hit subscribe, share this episode with your favorite Salesforce admin and let's get Nick on the podcast. So Nick, welcome to the podcast. Nick McOwen: Hey, Mike, it's great to be here. Mike: Well, I was introduced to you through a couple product managers at Salesforce that are always on the hunt for finding good Salesforce admins and you were also presenting with them in the admin track. So before we get to that, let's learn a little bit about Nick. How did Nick get started doing Salesforce and be in the ecosystem? Nick McOwen: Well, it was a complete fluke. I had been touring in a band and we just kind of stopped playing music and I was waiting tables at a country club and one of the members was, "Do you want to keep waiting tables?" I said, "Not particularly." So got me a job doing the entry level position at the company and I realized I didn't want to be doing that either. So I went to the developer at the time who was also the CIO and the CTO and said, "I'm going to learn Salesforce." And he kind of looked at me in the way that an adult might look at a middle schooler who said, "Watch me hit this three point shot." And I eventually learned it after a few misses, but they decided to take a risk on me and many, many years later here I am working with Agentforce agents writing a little bit of Apex here and there. And yeah, it just didn't intend to get here, but here I am. Mike: I mean, people are going to think I went down and raided the local music festival because not but a couple weeks ago I just had Adam Stark on who was also a musician that became a Salesforce admin. So apparently it's a trend. Nick McOwen: Yeah, that's the track. That's the track line for most musicians, I guess. Mike: Yeah. I mean, let's see. Should I be like an '80s metal hair band or an admin? Nick McOwen: Oh, that's a tough call. Mike: I know, right? Let's talk about some of the stuff that you presented at TDX because you covered a lot of things in terms of development life cycle and sandboxes and I felt like you were in that area for stuff that admins are interested in and kind of that next level of their career building apps. Nick McOwen: Yes. It was a talk that focused around seeding sandboxes masking data and my experience with that and it's funny because prior to the presentation at TDX, shout out to Allie and Sam, I was talking to them and they were running a booth and they were saying how many people that they'd talked to who didn't use sandboxes or didn't quite see the value in sandboxes. And so I realized that this talk probably had a lot more impact than I thought it was going to be. My particular use case was how we had rebuilt an app that our recruiting team was using for our field agents and how we spun up a sandbox specifically for it, rebuilt everything using the foundation of the app that was already there and got to test in a secure environment, move it up to our staging environment and then production. So it was an interesting experience and an eye-opening one too, getting to talk to everybody. Mike: I mean, to be fair, I don't think when I started as an admin, I really had to pay attention to what my organization's life cycle for app development was because you're kind of, and in this case, and I don't know about your company, but you're kind of a small scrappy unit and maybe they got Salesforce for like 20 or 30 people. I mean, nine times out of 10, I was just building stuff in a dev org to make sure it worked and then literally just not even deploying it, rebuilding it in production and Monday afternoon being like, "Okay everybody, so there's a new field on the account." I think back to those days of like, "Wow, what was I doing?" Nick McOwen: 100% identify with that because that is exactly how I more or less learned when we were first starting out because like I said, it was just the developer and then me and we had to get things done because it was a startup environment, things move fast and so it was tested in the sandbox and then move it. And I didn't want to bother him so I wasn't using change sets and so I would make a field or whatever he asked me to make and then rebuild it in production when nobody was working and just, yeah, it was loose and fast. Mike: I mean, nine times out of 10 when I was building things in my dev org, I wasn't paying attention to naming. I was just trying to like proof of concept and so I never wanted to package anything up because I didn't want to move it over because I was like, "Well, when I get to production, that's when I'm going to make the names nice and shiny." Nick McOwen: Yeah, I remember we brought on Kelly Bentubo, MVP. She sat me down and was like, "All right, we're going to start fixing some of these habits," which totally warranted. And I mean, she was great at helping me understand the value in the consistent naming, the process aspect of everything. So she really elevated my abilities and my use cases and everything. Mike: So as somebody that just started, obviously went from waiting tables, which by the way, 20% tip is not excessive. It just means that you got everything good and on time, you should tip more. Thank you for attending my waiter tipping TED Talk. Just getting into this and thinking, okay, I guess these are bad habits. I bet you had the same bad habits I did. What was the first things that she kind of tackled? You mentioned some of it was naming. Did she help you set up sandboxes and kind of a deployment life cycle? Nick McOwen: So we had the sandboxes and she came on at the time when the dev team was starting to grow and the company itself was starting to grow. So we needed more organization and she kind of sat me down and helped me with these processes, like how to move it up through the environments, the value of making sure that everything is tested within the sandbox environment and then user management, which I think is something that I relied on when I first started. It wasn't necessarily that I knew what I was doing a lot, but I knew how to put on like a waiter attitude so to speak. And if somebody asked for something and I didn't know what I was doing, it was just that kind of like, "Oh, I didn't burn your steak, but let me make this better for you." And so through talking with Kelly, I kind of like refined how to shape expectations for users. If I couldn't figure something out, then she would kind of help coach me through the deployment issues or level setting and expectations with users, which that was a big one. Mike: I mean, I think that also we've talked about order taker admins before and it's very easy to sit across the desk from somebody and listen to them be like, "Oh yeah, this is totally easy to do," or, "I have no idea what I'm going to do." And then say, "Yep, let me just work on it and kind of forget that maybe there's bigger things in the organization they need to pay attention to as opposed to everything that comes in front of me right away." Let's get into that recruiting app that you built. Was that your first kind of get your hands dirty in the org per se, building something new for the organization? Nick McOwen: That was my first project that I led from start to finish. I got the specs from the higher ups. They said, "This is roughly what they're asking for, figure it out." And immediately went to the recruiting manager and said, "Okay, let's figure out how we want this to look." And we had an app that was already built and I knew that the foundation of that app was great. And so it was really a matter of building off of those blocks and reconfiguring it, re-imagining how it could be used and then future-proofing it so that it could scale as the business grew. And it was definitely a lesson in organization and communication, which is good. Always want to keep learning and growing. Mike: Yeah. So let's dig deeper into that organization communication. What organizationally, do you mean the way that you organized stuff, understanding your company's organization, a little bit of both? Nick McOwen: A little bit of both. For me, it was keeping track of everything that was getting worked on, making sure that we were trying to document the change in processes and communicating those changes to the business side so that they would know, you might not interact with this functionality, but this is what's going to happen to get you this result. And that it sounds pretty straightforward, but I think that can get lost sometimes on people, especially in larger projects where it seems peripheral and intuitive, but it might be what's intuitive to someone who built it might not be for the person that's going to end up using it. Mike: Yeah, which leads into communication. I always feel you can't communicate enough. I feel with every project I've ever worked on, you always learn more about communication. What did this first jump in kind of give you in terms of maybe some best practices that you follow now or stuff that you learned really quick? Nick McOwen: I think the accountability aspect maybe was if you presented an idea and it's kind of your child and you say, "What do you think about this, huh?" And then the end user going, "No, that's not going to work for us." There's like a little bit of an ego bruise where you think, "That was a really good idea though." Maybe it wasn't, but then kind of absorbing that critique and then using it to build something that you know is going to work and not being stuck ruminating on the fact that your idea didn't get accepted, that was kind of a lesson because prior to that it was somebody else's idea or I was building something that was given to me. It wasn't as personal, but that was the first time I got told, "Hey, I don't like that." Mike: Yeah, that can always... It's funny because you almost want your cake and eat it too, right? I don't want to take the rejections personal, but you 100% take the wins personal and it's like you can't have both. You really do though because it does feel like, "Well, no, I know how this thing works and I promise this will really work for you, but you're just not seeing it." And that can be the frustration that I always ran into. Nick McOwen: Exactly. And then even after I built it, my bosses came up and they said, "What is this object?" Oh, well, I made that because that was giving the solution to the end user and they said, "Hmm, well, why didn't you do this?" I was like, "Ah, I don't know why I trusted my gut and stuck to it." Mike: Right. Well, this is the way it is now. Let's talk about, I feel like that's always the first part. Your path into Salesforce, they always talk about individuals that grew up and like I was in high school in the 90s just to date myself, but I remember in middle school there was no internet and when I got to high school, you could go to the library and check out the internet for 15 minutes on a computer. I bring that up to say, obviously now everything's online and I don't know how I even got anything done in 15 minutes with dial-up modems back then, but apparently I did. You kind of came in to the Salesforce ecosystem at about the same kind of inflection point with AI in that there's really best practices and development aspects to learn, but then, oh, hey, by the way, now we've got a lot of new stuff coming like Agentforce Vibes. How did you kind of balance those two that learning path? Because I think it would be very easy to, "I don't need to learn this. Vibes can do it for me." Nick McOwen: I think that's something that is incredibly important in this time with the ubiquity of AI and how many people are using it. I think people need to become literate in AI. I don't mean learning how to program large language models or even write agents, but just understand how it functions. And in the context of Salesforce, I remember I first started getting into the predictive analytics for Einstein and thinking, "Oh, this is super cool." We didn't end up going that route, kind of kept my eye on everything going and then Agentforce came out and started learning that. And it feels like every couple weeks something's getting rolled out, which is exciting because there's always something to learn and I don't know, I would hate to be stagnant and have to do the same thing over and over for 20 or 30 years. So it's a blessing and a curse to have a product that constantly evolves for you to learn. So it's exciting. Mike: I think you covered Agentforce Vibes in your TDX workshop. What have you done in Agentforce Vibes? Nick McOwen: Shockingly, I made an Apex class and a test class that- Mike: Hey. Nick McOwen: If you had asked me... Mike: It's kind of what it's there for, right? Nick McOwen: Yeah. The musician that could barely string sentences together is all of a sudden writing Apex classes and test classes. I mean, if you asked me even a year ago, "Hey, Nick, would you think you could write an Apex class?" I was like, "Yeah, give me a couple years so I can write it line by line over days." Mike: Sure. Let me put an ad out on Craigslist and see if I can get a developer to do it. Nick McOwen: Yeah. I would've laughed if somebody said that and then all of a sudden this product comes out, which actually Allie and Sam, when we were doing our ... We did a webinar for the sandbox seating and data masking and they were talking to me about the Agentforce Vibes and I said I hadn't really looked into it. And so after that talk, I started to and that kind of encouraged me to look into the foundations of Apex and coding languages. So it wasn't just learning Agentforce Vibes and how to use it. It was also getting a base understanding of the underlying principles. And so through that journey, I was able to use Vibes to write an Apex class and then I could take that class to the developers and then the developers would look at it and go, "Well, my Apex is better, but we'll use yours." And corrected a couple things because... Mike: Wow, you really nailed the developer intent like mine's better, but we'll use your... Nick McOwen: It could be flawless code and still, mine's prettier. No, I do. I enjoy working with all those guys and they were great helping walk me through everything and showing me, "Okay, this is where Vibes made this. This is the intent but it doesn't quite hit. Here's how we're going to fix that. Walk me through." And it was a great launching point. Something that would have taken days was written in an hour. Mike: Oh, wow. Nick McOwen: We're not talking thousands of lines here. It was- Mike: No, but still. Nick McOwen: 150. Yeah. And then the test class on top of that, it saved us a ton of time. Mike: If you threw me in jail and said, "You're out when you write 150 lines of Apex class," I'll be like, "What's for dinner?" Nick McOwen: I've been be here for a while. Let me get some furniture. Mike: We're going to be here for a few years. Do I get a shave every now and then every few weeks to keep me from looking scruffy? I mean, I was so impressed getting the admin track ready for TDX this year with the submissions that admins had. I watched them demo vibes and just use the planning tab and really kind of have vibes spell out like, "Here's everything you need to do and here's kind of an action plan." And I felt like natively some people had that, but for a lot of people, wow, this was really helpful because I had this monster of an application but I didn't know where to start and it wasn't just, "Oh, I have to vibe code this super hard application." It's like, "No, this is actually just helping me get my steps down." Nick McOwen: I'm excited for the future of the vibes and Salesforce integration, specifically with your organization's metadata and being able to find, where are these fields referenced? What would happen if I did this? I think when that becomes a reality, it could be something that's really cool. And I imagine that's something that's possible if it's not already. I'm not a vibes connoisseur just yet, but I think something like that would be incredibly beneficial. How many times have you tried to figure out where an error is coming from...
/episode/index/show/buttonclickadmin2/id/41364320
info_outline
How Headless 360 Helps Admins Bring Salesforce Anywhere
05/14/2026
How Headless 360 Helps Admins Bring Salesforce Anywhere
Today on the Salesforce Admins Podcast, we talk to Khushwant Singh, SVP of Product Management for the AI Application Development Platform at Salesforce. Join us as we chat about what Headless 360 means for admins and how Salesforce is building towards a future where setting up complex systems becomes a conversation, not a checklist. You should for the full episode, but here are a few takeaways from our conversation with Khushwant Singh. What is Salesforce Headless 360? If you’re not a developer, the idea of a “headless” platform may sound a little spooky. My guest this week, Khushwant “Khush” Singh, is here to tell us what it all means and why Salesforce Headless 360 represents a step forward into the future of the Agentic Enterprise. As Khush explains, in a headless platform the frontend is separated from the backend. If you have a pixel-perfect website that you love and you want to use Salesforce applications, or visualizations, you can do that without having to change anything. If your organization relies on Slack, your users can interact with Salesforce data and agents in the chat instead of having to open another browser tab. “Headless 360 is about bringing Salesforce to wherever you need it,” Khush says. Headless 360 builds the foundation for the Agentic Enterprise One of the main reasons for Headless 360 is to rethink the Salesforce stack for AI. “For the last 27 years, those layers have been put in place for a human,” Khush points out, “so how do we open this up for both a human and an agent?” To do that, Khush and his team are translating the entire platform into a set of model context protocols (MCPs), skills, and metadata that can interface directly with AI agents. This makes conversational tools within the platform, like Setup with Agentforce, even more powerful, while also allowing you to use any other outside AI model you like. And while these changes have the biggest impact on vibe coding for now, Headless 360 lays the groundwork for a future where we build agents, create applications, and configure Salesforce through a conversational interface. No coding required. Why trust is even more important with the rapid pace of AI AI is quickly transforming the way we work, and the conversation can become centered on how to move fast. But that makes trust, quality, and governance even more important, Khush explains. Headless 360 is built with trust as a core feature, so you can move quickly without making compromises. There’s much more from Khush about Salesforce Headless 360 and what it means for admins, so be sure to listen to the full episode. And don’t forget to subscribe to the Salesforce Admins Podcast to catch us every Thursday. Podcast swag Learn more Salesforce 360 Blog Post: Salesforce Admins Podcast Episode: Salesforce Help Article: Salesforce Admins Blog Post: Trailhead: Admin Trailblazers Group Social Full show transcript Mike Gerholdt: This week on the Salesforce Admins podcast, I'm joined by Khushwant Singh to talk about what happens when Salesforce stops just being a destination and starts becoming part of every system your business already relies on. That's right, from Headless 360 to Setup with Agentforce, Khush breaks down how admins are moving beyond configuring features and into orchestrating how data, AI agents, automation and people work together across the business. Now, we're going to dig into what Headless actually means for admins, why governance and trust matter more than ever in an AI first world, and how Salesforce is building toward a future where setting up complex systems really becomes more of a conversation than a checklist. This episode is really about systems thinking, how admins can connect experiences without forcing teams to rebuild everything from scratch. So if you've been trying to figure out where AI fits into your role or how your role is evolving alongside it, I promise you this episode gives you a practical look at what's already happening and what's coming next. So be sure to hit that subscribe button. Share this episode with your favorite architect or admin friend, and let's get Khush on the podcast. So Khush, welcome back to the podcast. Khushwant Singh: Thank you for having me back, Mike. Mike Gerholdt: I say that because I had to look and it was 2022 back in the day you were talking Experience Cloud when we last had you on. You've since moved on, moved up, had your hands in a lot of things, did an admin keynote with me. So let's start there and let's kind of catch everybody up on some of the products you've been working on, and then we're going to talk about the newest one that we launched at TDX this year. Khushwant Singh: Yeah, happy to. And again, great to be back. I think back in the day, started obviously with Experience Cloud. Experience Cloud really was building a product that is external-facing and again, it's built on the same platform. And again, as we looked at the product portfolio, it just made sense to start to bring things together. So we've actually sort of rolled and morphed into the application development platform, obviously within the platform organization, everything pro-code, low-code, desktop, mobile. And so there've been quite a few products leading up to here, anything from our delivery on mobile, mobile offline, the Salesforce mobile app, all the way to Agentforce Vibes, the Agentforce Experience layer, obviously a fair amount of work on the Headless side of things. So yeah, it's been quite a journey to this particular point, Mike. Mike Gerholdt: Yeah. I mean, it's actually hard to point out things that aren't admin-friendly that you've had your hands on because you've always kind of championed everybody being able to build on our platform. So let's talk about TDX this year because we launched Headless 360. Khushwant Singh: Oh yeah, we did. Mike Gerholdt: By the way, in case you forgot. Khushwant Singh: Yeah, it was a massive announcement. I think, look, as you think about what's happening in the market right now, you've got customers engaging through many different surface areas. We've got customers on ChatGPT, on Claude, on Gemini, Teams. At the same time, you've got developers also using a variety of different tools, different IDEs, different coding agents. And so I think Headless 360 really is a testament to acknowledging this change in the market in the industry and trying to meet the customer where they are. The customer being an end user or the customer being a developer and admin, just meeting them where they are in whichever tool, whichever interface they might be. Mike Gerholdt: Yeah. I mean, do you recall ever a time in technology when it was, I hate to use the euphemism, but like the Wild West where I feel like there's so many choices for what you can do just in regards to AI? Khushwant Singh: There is. And there is obviously a good side to it. There's also a downside to it. The good side is really your [inaudible 00:04:31] for choice. There is innovation that is helping you drive productivity day in, day out. The downside of this is you just have to be really careful about quality, about trust, about governance. And you have to ensure that while you're going fast, you're not sort of compromising on that trust aspect of things. And that's what we're trying to do here at Salesforce and just trying to be a little bit more thoughtful in our approach over here. Mike Gerholdt: Yeah. So my developer friend, Josh Burke, who comes on the podcast, usually has to explain things to me every now and then. I think developers are very familiar with the term headless. Khushwant Singh: Yes. Mike Gerholdt: I'm not sure outside of Headless flows, which I know what those mean, I'm not sure admins could understand or could confidently buzz in on a game show and answer what is Headless 360. So can you help them kind of understand what is Headless 360 if they had to tell their manager? Khushwant Singh: Yeah, sure. So one way to think about it is, let's say you're a customer and you've got your own website, it's built out of React, it's not built on the Salesforce platform, but there is so much of your goodness and investment that you have within the Salesforce platform that you want to be able to easily reuse in the context of this other website that you have, portal that you have, mobile application that you have. All of that may not be built on the Salesforce platform. You want to be able to reuse your investment seamlessly. And so Headless 360 really is about how do we empower you, the customer, to be able to easily use those assets, those investments within the Salesforce platform in that surface area that you've got that may not be on the Salesforce platform. So it's really about giving them that flexibility so that they can easily reuse their investments in all of these various surface areas and just meet their customers wherever they are versus bring their customers into Salesforce. Mike Gerholdt: Yeah, I think it makes sense. I mean, I was a customer way back in '06 when I remember it was like transfer and move to Salesforce, and everything was "have it on the platform, have it on the platform." And then shortly thereafter it was kind of like almost the realization that we had was, "Well, it's a lot of friction to constantly move platforms. What if companies just integrate and we become that connector to everything?" And I feel the same way with this. Khushwant Singh: 100%. And you know what? Look, I think the one example is if you go into the Williams Sonoma website, right? Williams Sonoma website, it's not built in Salesforce, but if you use their sous chef AI, I think... I'm not sure what they call it, but- Mike Gerholdt: I'm sure it's something really, really snappy and small. Khushwant Singh: Olive. Olive. There you go. Mike Gerholdt: Olive. Yeah. See? Khushwant Singh: A snappy name right there. That agent is an Agentforce agent, right? So that's on example where Salesforce is being used in whichever head that you'd like us to be in. And so in this particular case, the Salesforce agent is in the Williams Sonoma website. So that's just one example where we are trying to make it easier for this integration to happen through the Headless 360 platform. Now that's one view. And that's the view, I would say, an easy way to try to understand what it means for Headless 360. Mike Gerholdt: Yeah, because then as an admin, as a developer, you're not having to sit down and say, "Okay, well, if we move to the Salesforce platform, we have to deprecate everything that we just spent the last two years building on our site." Marketing's like, "No, no, we just got the site pixel perfect the way we want it. Now we can integrate best of everything that we want." For admins who aren't thinking of maybe websites, how does Headless 360 play into other integrations that they may talk to IT or internal stakeholders about? Khushwant Singh: Yeah. So for example, when admins are chatting with their other internal team, they may have a custom application that they already have in place and they want to be able to have Salesforce data, Salesforce visualizations surface in whichever application they may have already, right? That's one example. So again, it is about bringing Salesforce to wherever they may already have. So for example, an admin may have a business application that already runs within ChatGPT. So ChatGPT, for example, it allows companies to create bespoke applications. And if you want to be able to integrate Salesforce into that application, that's doable as well. It doesn't have to be in ChatGPT. It could be in any other existing non-agentic application as well. But it's about that, look, you don't have to rebuild everything. Wherever you are, you've got an existing application, we'll find a way through Headless 360 to be able to bring Salesforce to it. Mike Gerholdt: Yeah. No, it totally makes sense. I mean, in that way we can really think about how are we making sure that the departments have the software and the tech that they want, but also access to all of the information that they need to do their jobs the best. Khushwant Singh: Mm-hmm. Mike Gerholdt: So Headless 360 is a big thing we talked about. I also know I saw you in some True to the Core and True to the Core Deep Dive stuff. Was there some features you were talking about in that that possibly play into what admins are going to be working on for the rest of this year? Khushwant Singh: Well, yeah. I mean, a few aspects as we think about Headless 360 that would be of interest to admins. So first and foremost, you've all seen the stack diagram of the Salesforce platform. You've got those four layers. You've got your layers of engagement, you have layers of context, you've got the sort of our data foundation, et cetera. So you've got those layers that make up the Salesforce platform. For the last 27 years, those layers have been put in place for a human, right? And now what the product teams and the engineering teams are doing are going back and saying, "How do we now open this up both for a human and an agent so the agent can do that work on behalf of the admin when the admin sort of wants a task to be done for that particular reason?" And so what that means is that we're translating our entire platform into a set of MCPs, a set of skills, a set of metadata that is grounded so that these agents can do the work on behalf of the admins. So one good example is the setup with Agentforce, which is so far so good. We've gotten great feedback on it. Now behind the scenes is a set of skills, a set of MCPs that are firing off to be able to get their tasks done. And so that's one thing that I think our admins can look to benefit from. The other piece is I know we have some admins who are familiar with some of these IDEs that we have out there. They use Cloud Code quite a bit. They use Vibes quite a bit. It may not be the entire admin audience, but for those audiences, again, the ability to be able to use all of these MCP skills in these development environments is another thing that our admins can really look forward towards. Now the other thing that we've also worked on is, over the last few months, the foundation for these skills, these MCPs, this Headless 360 foundation has been very sort of focused on how do we unblock these pro-code use cases, whether that's in Cloud Code, whether that's in Vibes, et cetera. But this is the same foundation upon which as we speak in safe harbor, I share that we are building what we call our no code offering as well. So how do you go about in an unintimidating sort of type of interface, have this conversation with an agent, which behind the scenes is interacting with that same Headless 360 layer to help you build out your agents, your applications, to help you augment your existing agents and applications, help you set up provision, configure Salesforce from a zero to one point of view, because we all know how setting it all up is quite a taxing task for our admins? So that's the potential I see for Headless 360 for our admin personas. Mike Gerholdt: Yeah. I mean, to go back on some of the stuff that you were mentioning, I remember the first time I thought, "Hey, I could have ChatGPT rewrite ChatGPT's instructions." And I remember thinking like, "I'm so far ahead of the curve, man. I'm making AI rebuild AI." And then it was only a few weeks later that Cheryl was demoing Setup with Agentforce and I thought, "Oh, that makes so much more sense because all of the things that you were having that setup agent do are things that not necessarily admins don't like doing. It's like paper cuts." It's the little things that take 20, 30 minutes out of your day when you really wanted that solid hour to build that application kind of start to finish. Khushwant Singh: Indeed. Indeed. So we really viewed Headless 360 as the foundation upon which agents can work on behalf of the admins. And again, look, this is agents and admins working together because again, we've got to have the human presence to be able to validate, to be able to interrupt, to be able to initiate any actions that are performed by the agents. And if these agents can help drive greater productivity, then it's a win-win while at the same time having governance by humans over it. Mike Gerholdt: Right. Absolutely. Do you envision us being at a point where all of setting up Salesforce could just be a conversation with an agent based on the business and what they're trying to accomplish? Khushwant Singh: We are trying to do that. We are trying to do that. Now, I'll give you a view into our approach over here. We're taking a steel thread approach here where just trying to, for example, set up a customer service agent. That cuts across Service Cloud, cuts across platform, cuts across Agentforce, cuts across Data Cloud. So we've got to take a system view, an end-to-end view versus a feature view because that's what our admins go through. That's what a practitioner goes through. They look at it from a steel thread point of view, and that's what we as product teams have to do. And so as we think about using agents to go ahead and help provision, set up, get Salesforce up and running really quickly, that's the new strategy that we are taking over here, a steel thread view so that we can look across the board and say, "Look, which MCPs are missing? Which skills are missing? Which APIs are missing? Which metadata needs to be grounded? How do we ensure that across entire steel thread, quality is being ensured, governance is being woven into?" So we are starting that way and we want to scale that way as well. So my hope is that come Dreamforce this year, we'll be able to at least have a sizable number of steel threads that we feel really, really confident about on Agentforce really helping and agents helping in this particular side of things. So yeah, that's the approach we're taking, Mike. Mike Gerholdt: Wow, that's going to be amazing. Every time you think, "Oh, we've probably invented everything," technology just comes along and pulls the rug out from underneath of you and says, "Haha! There's new stuff. You got to figure this out now." I'd be curious, you're so ingrained in a lot of things that admins do on the platform, a lot of things developers do on the platform and then also having to keep up with AI. What is a piece of advice you could give people for how you personally keep up with the newest news and innovation on what's going on with AI? Khushwant Singh: Wow, that's a good question. I think first and foremost, I spend a lot of time just looking at reading publications like what's on TechCrunch, what's on Techmeme, trying to just understand how are technology providers adapting, how are companies using AI. That's one. The second one is actually you learn a lot via speaking with others in the community, right? Mike Gerholdt: Mm-hmm. Khushwant Singh: You talk to customers, you talk to other admins, you talk to other developers and you get to understand there are use cases that they're working through and some of the very many innovative workarounds or users of AI that they're applying. And then you're thinking about this that, "Wow. There's a trend here, there's something that we should be backing up and maybe providing out of the box within the product." And so I think that community piece speaking with other customers, with your peers, your colleagues from different companies, that sort of brings a very practitioners and practical view to things. So I think if you combine it with some of these ... So if you take a combination of both, what's being published out in the internet, what sort of bleeding edge and...
/episode/index/show/buttonclickadmin2/id/41287420
info_outline
Why Pattern Recognition Matters for Salesforce Admins
05/07/2026
Why Pattern Recognition Matters for Salesforce Admins
Today on the Salesforce Admins Podcast, we talk to Adam Stark, CRM Systems Administrator at Belmont University. Join us as we chat about how his experience as a musician with learning and pattern recognition has set him up for success as a Salesforce Admin. You should for the full episode, but here are a few takeaways from our conversation with Adam Stark. From the stage to the Salesforce Admin chair I met Adam Stark at TDX, and he had such an interesting path to becoming a Salesforce Admin that I had to bring him on the show. Based out of Nashville, he’s been a professional touring musician for twenty years. But when everything shut down during COVID, he spent his days on Zoom making an album, and his nights on Trailhead working towards his admin certification. Adam’s experience in the studio made it surprisingly easy to jump into automations on Salesforce—they made sense to him. “As a music producer, one of the things I got really good at doing was accomplishing signal flow, like trying to get a sound source to a final, presentable stage,” he says, “and that sort of signal flow process is the same with flows.” Whether it’s building tracks in a DAW or building solutions in Salesforce, Adam discovered that it’s still the same underlying logic. How pattern recognition makes learning Salesforce easier Starting out in Salesforce can feel overwhelming because the platform is robust. But, as Adam explains, the same could be said for learning guitar, and he realized that he could draw on his experience as a music teacher and performer. A part of learning any instrument is pattern recognition. You practice scales or licks in isolation so that it’s easy to find them and play them when you’re performing. “The more you do it, the more familiar you get, the more you begin to recognize patterns,” Adam says, “and once you see the patterns, things start to feel smaller.” Over time, something that seems very big, like learning a piece of music or trying to use campaigns in Salesforce, becomes more manageable. Acing your job interview with honesty I also wanted to hear how Adam got through the interview process and landed his first job as a Salesforce Admin. His experience as a musician helped here, too, because he was already used to doing interviews with radio stations while on tour. But nerves aside, Adam feels the key to his success was honesty. “I don’t know everything,” he says, “but if I don’t know it, I’ll figure it out, and we’ll find a solution.” For the folks out there who are still breaking into the ecosystem, Adam encourages you to get out there and meet working Salesforce professionals as soon as you can. Go to a community group, or even TDX, and pick someone’s brain. It can help you piece together what you’re learning in Trailhead by understanding what Salesforce looks like in action. There’s so much more great stuff from Adam about how he learned Salesforce and landed his first admin role, so make sure to listen to the full episode. And as always, make sure you’re subscribed to the Salesforce Admins Podcast, and we’ll see you next time. Podcast swag Learn more Salesforce Admins Podcast Episode: Salesforce Admins Podcast Episode: Admin Trailblazers Group Social Full show transcript Mike: This week on the Salesforce Admins podcast, Adam Stark didn't start in Salesforce. He started on a stage, building songs and touring as a professional musician. In this episode, he's going to share how that same mindset of thinking and systems, sequencing steps, and designing outcomes translated into building solutions with data, automation, and now AI. In this episode, we're going to dig into how admins aren't just learning tools anymore. They're designing how work actually gets done across people and technology. Adam's going to walk us through his journey from Trailhead to his very first admin role and what it really takes to connect those dots when you're building something bigger than just features. So if you've ever wondered how your past experience shapes the way you architect solutions today, this episode's for you. So with that, let's get Adam on the podcast. So Adam, welcome to the podcast. Adam Stark: Happy to be here, man. This is awesome. Mike: I'm glad we got connected through our architect friends. You are at TDX this year. So let's just give people an overview of who Adam Stark is and how you got started at Salesforce. Adam Stark: Yeah, absolutely. So I work down in Nashville, Tennessee. I work at Belmont University. And my journey into Salesforce is quite a unique journey. I actually was a professional musician for a long time. I was a touring artist, a professional songwriter, producer, and did that for many, many years. And then a thing called COVID hit in 2020 and really put a damper on the touring side of things, as you can imagine. So during COVID, I went through my own personal little existential crisis moment of, are we ever going to play shows ever again? This was a huge part of my income stream to provide for my family. And so I'm going through this crisis moment of what's next, what should I be doing? And a really good friend of mine who is a Salesforce developer, he told me, he's like, "Man, you should look into Salesforce. Just go on Trailhead and just poke around." And this is me not knowing anything about it. I didn't even know what a CRM was, but went on Trailhead and shout out to the Trailhead team because what an incredible resource, like unbelievable resource for people to learn the platform. Just really, really impressive. But yeah, I would spend my days working on music with my... I was a duo, if you will. I was in a band with another guy and he and I produced our records and we wrote all of our songs. And we're doing that virtually during the day during COVID where we're songwriting over Zoom, which is a complete interesting exercise to try to be creative over Zoom. And then we're recording audio files and sending them back and forth and compiling them into a record, which was wild. Doing that during the day. And then at night, I would just get on Trailhead and just start learning. And the more that I learned, the more interesting it got to me. And yeah, I got hooked and was really fascinated with what Salesforce as a platform was capable of doing and honestly how beneficial it is to businesses and organizations. Mike: Wow. Adam Stark: So yeah, I started learning. I was really determined to get an admin certification just to have in my back pocket. And then the world opened back up. And we did what artists called revenge touring because so many people were starved for entertainment at that point in time. It'd been a year, year and a half of no real public entertainment. So we got busy, went back out on the road, and I put Salesforce on the back burner for a little bit and then had more kids and talked to my wife and we just decided we're at a spot in life where being home is really, really nice. And I was pretty invested into the Salesforce journey at that point. So I went ahead and finished up, got my admin certification and I saw that Belmont was looking to implement Salesforce and went ahead and filled out an application and landed the job. Mike: So I've shown Salesforce to people. I've taken good friends of mine to user groups and I've had friends of mine even get up to Ranger status, which is a hundred badges and still be like, "Meh, it doesn't make sense to me or nothing's clicking." Something clicked for you that was like you got it and it's hard to describe, but I know what you're feeling, but what was it for you? Adam Stark: As a music producer, one of the things that I got really good at doing was accomplishing signal flow, like trying to get a sound source from one stage to a final stage, final presentable stage, if you will. And what I found was when I really started to get into some of the automation tools in Salesforce, especially flows, I realized this actually feels like a very familiar muscle to me. How do I get from A to B and what are the steps I need to take and in what order? What's the logic to get there? If I was producing music, it would be, I've got this... Say it's a vocal, do I want to EQ the vocal first or do I want to compress the vocal first? And then do I want to bus it to a different channel and affect it there with other things or do I want it to be isolated? And really that signal flow process is the same with flows. And then I just watched what it could do with data and I was like, "This is actually really fun because you're building solutions." As a songwriter, you're building songs. As a producer, you're building tracks and you're building records and I'm still building. It's just a different medium now. Mike: Yeah, that's fascinating because the next question I was going to ask you was... So I will confess, when COVID hit, I was one of those people that's like, "I'm going to learn a skill." Except I didn't do like you, I wasn't as devoted. I bought a guitar, a really nice acoustic guitar. And let me tell you why. Two reasons. One, I was like, if I'm going to learn, I'm not going to learn on some Walmart guitar level, I'm going to learn on something good. Adam Stark: Good for you. Mike: And two, if I buy something nice, then I feel like the investment will... I'll feel bad if I don't use the investment, right? Adam Stark: Mike, I'm the same way. When I told my wife, I'm going to get into cycling. It's like I need to buy a nice bike to make myself get on the bike. Mike: Right. I'm not going to buy the Lance Armstrong. I didn't go out and buy a Les Paul and spend a used car's money, but I got a nice acoustic guitar and people come over to my house, they see it on the stand. They're like, "Wow, do you play?" So here's the moral of the story. I took guitar lessons online for like a month solid and I realized, I don't know what it is, but music and math are two things that my brain's like, "Hey, that looks like I should go on the couch and sit and eat some Cheetos and somebody else will figure this out." That is exactly what my brain does. And so I would get to the point where I could learn the chords and figure out the finger and then they started to get to the point where they're like, "We're going to teach you music." And those notes on those bars, it might as well have been a foreign language. It was to me. It just didn't make sense. And I'm sitting here, during the day, I do Salesforce and we're dealing with complex flows and data validation and all this other stuff. And I'm like, "Why can't music make sense to me?" And it's funny because the reverse almost sometimes doesn't hold true. What works for you in understanding music did not work for me in taking understanding Salesforce to music. It's crazy. So anyway, so the moral of the story is I have a really nice acoustic guitar- Adam Stark: We're going to do some guitar lessons out there. Mike: ... that has sat on its stand. But I did play it for a month. Adam Stark: Well, you bring up an interesting point, and this might cross over to just some meta principles in general is the longer you're doing something, when you first get into anything, whether it's music or Salesforce for that matter, Salesforce is so daunting to get started because it's just so robust. There's so many things. It's overwhelming. It feels like this massive mountain you have to scale, but the more you do it, the longer you go about doing it, the more familiar you get, you begin to recognize patterns, right? And then once you see the patterns, things just start to feel smaller, if that makes sense. And I think the best way I could describe it is, that has been my journey with Salesforce. To get started, it felt like this massive undertaking. And the concept of campaigns, it's like, what are those for? I still don't really know why someone... There seems like there's several different angles to use campaigns, and it's just trying to get your head around it without ever being a user in Salesforce. But then you start seeing one example of campaigns, and then you see another, and then you're like, "Oh, well, now I've got some creative ideas because I recognize some patterns and I know what the functionality of this thing is." So yeah, I just think the longer you work at something, you recognize those patterns and then it's like, "All right, this actually is starting to make a little bit more sense to me." Mike: So you got your certification, you did Trailhead on and off when you weren't revenge touring, which is a fun term. I also remember that when the world opened back up and we were like, "Oh, let's do a thing." And maybe ironically, the first thing I did was I went to a Hyatt Regency and I got French fries. Adam Stark: Yes, sir. Mike: Totally boring, but man, the quality of French fries in those restaurant style fryers, nothing at home makes the same. Adam Stark: You are right. Mike: Everybody right now that's listening to this podcast wants me to ask this question, so I'm going to ask this question. Adam Stark: Okay. Mike: What was your first interview like? Because you obviously did a remarkable job of interviewing because you got a job. And I asked that question because I probably every day get a dozen or so DMs across various social networks of, I'm starting in Salesforce and I want to be an admin and how do I get my first job? Adam Stark: It is the million-dollar question, right? Mike: Right. Adam Stark: Again, going back to familiar muscles, one of the things that I was familiar with was the concept of interviewing because I did interviews with radio stations all over the country for years. So the idea of someone sitting in front of me and asking me questions, I wasn't expecting it. I was pretty nervous about it at first when I was venturing into this new career path because I was like, "I haven't had a job interview in how many years? It's been a long time." I was pretty nervous about it. And then once I sat down and started having the conversation, again, it was like a familiar muscle of like, "Oh, this is an interview just like a radio interview is an interview." So I felt pretty comfortable in the interview environment. And then it was me being honest. I really wasn't trying to put on that I knew more than I actually did. I wasn't trying to talk technical where I didn't understand it. I was honest with the idea of who I was as a person, what I'd learned. I'd achieved my certification. I have a pretty good base of knowledge for what Salesforce is and what it can do, but I don't know everything, but I'm determined to find out. If I don't know something, I'm the person that will figure it out. That's what I've always done. In my music career, where there were technical needs, we didn't always have resources to have somebody else meet those needs for. So I would be the one that would go and dive into it. I would figure out how to code lighting rigs and write DMX and program a light show for us because we needed a light show. So that's just my makeup is I'm a hard worker, I'm a learner, and I was honest about that in my interview. If I don't know it, I'll figure it out. We'll find a solution. And it worked to a point. Obviously, the organization took a chance on me because of an experience gap, but they saw something in me, I guess in my integrity and honesty, but also my drive to find solutions and not be afraid to go learn was attractive to them. Mike: Yeah. Well, from your perspective, what were you the most concerned about going into that interview? Adam Stark: I would say I was most anxious about the technical interview side of things, mainly because I have never been a front end user and I'd never been an admin before. So I was a little anxious about, am I going to look like a fool if they're asking me technical questions that I should know answers to? And there was a little bit of that. We found some limitations in that interview process, but again, I always said, "I'm happy to go learn. I'm happy to run that down and figure it out." Mike: Yeah. That's always, I feel like, the first question is, how do I get through the interview? How do I get through... I've never had a Salesforce admin job before. Aren't they going to look for experience? And to me, my first job, I didn't have a Salesforce admin certification or anything, and I just got handed that as a responsibility. I think it depends on the vision and commitment that people see. They saw something in you and said, "Hey, he can grow with us in the same way that we're probably looking to grow this platform." And also, you were a good fit culture. I think people are always like, "Well, what if I'm not smart enough?" Well, the other part of it too is, do they see themselves working with you? Adam Stark: Absolutely. That's a really good point. And I should mention, I don't think I mentioned this, I graduated from Belmont, so I went here for undergrad. Mike: A little bit of alumni. Adam Stark: I had the alumni angle coming in. So that really helped because I did understand the culture. I was here for four years. I'd know what the school represents. I knew how, at least on a basic level, how the school functioned and what some of the departments and teams were. So that was a starting point, right? But you're absolutely right. What you know is, I don't want to say half the battle, maybe more than half the battle, but there's a large percent of the battle is like, are you going to be someone we enjoy working with day in and out? And are you someone that thousands of other faculty, staff and students are going to be interacting with? Are you the person for that job? So you're right, the culture fit is a huge part of it and not to be underestimated. Mike: Yeah. What part, now that you're in it, of the job has probably been the most rewarding that you didn't anticipate? Adam Stark: Oh, it's for sure this idea of going through a journey with people. As admins, you find your users and you go through the discovery process with them and you learn about what are your pain points and you just learn about the language they speak and their staff, their workflows, all that stuff. And when you can deliver something that helps relieve those pain points for them, and at the end of it, they see that beautiful chart that they've been longing to see for two years, or they see the one-click automation that just executes perfectly and performs the need they need. When you can look at each other and high five at the end, and just it's so rewarding. I just love those wins with people. Mike: Yeah. The best part for me was always go live day. When somebody finally gets that solution and they're like, "Oh, I don't have to look at that green DOS screen anymore." God knows whatever else they were dealing with. Adam Stark: Absolutely. And then you see the spreadsheets and things that they've been managing. Mike: Oh, [inaudible 00:18:03]. Adam Stark: "Oh, Lord, this is your world." Mike: It is. But what's funny is some people, I'd say, almost get to the level of coding with the amount of cross tables and pivot tables and references that they build in these spreadsheets. You almost have a robot there. Adam Stark: You are right. You are correct. Mike: So you spent some time at TDX this year. Was that your first Salesforce event as an admin? Adam Stark: It was my second. I was able to go to Education Summit last year first, but I got to say TDX was awesome. I loved it. Mike: A lot of people that listen to the podcast don't get to go. Some people do the over under. I wish all my listeners could go to TDX, but for you, what were you going there thinking, "Here's what I need to leave with?" Adam Stark: It's a really good question. For me personally, I am not content staying where I'm at. I always have this need to grow. So as an admin, I feel like I'm getting comfortable with some of my admin tasks and I'm always...
/episode/index/show/buttonclickadmin2/id/41183915
info_outline
Agentforce Grid Enables Next-Gen Admins to Scale AI Workflows
04/30/2026
Agentforce Grid Enables Next-Gen Admins to Scale AI Workflows
Today on the Salesforce Admins Podcast, we talk to Avi Shah, Senior Director of Product Management for Salesforce AI. Join us as we chat about Agentforce Grid, a new way to coordinate data, automation, and AI agents. You should for the full episode, but here are a few takeaways from our conversation with Avi Shah. Spreadsheet-style AI workflows to simplify complex automation Salesforce Admins deal with data, automations, and AI every day. But how do you make everything work together in a way that makes sense? That’s why I sat down with Avi Shah to talk about Agentforce Grid, a spreadsheet-like tool for creating AI workflows. “Agentforce Grid is, in our opinion, the fastest and easiest way to build AI workflows,” Avi says. “You have columns for your data and the actions you want to take with it.” Some columns are AI-based, enabling you to run prompts or agents you’ve built, and others are action-based, allowing you to update records or call an invokable action to send an email. Put it all together, and you can build complex AI automations that can transform your organization’s workflows. Combining data and actions As Avi explains, Agentforce Grid gives you a simple, spreadsheet UI to perform powerful transformations on your data. You can pull things from Data Cloud, uploads, or even the web into a data column. Action columns give you a way to act. You can run prompt templates, agents you’ve already built, or inline prompts. Not everything needs to be an AI step, however—you can also perform more deterministic actions like formulas, updating records, or invoking flows. AI and non-AI actions work together in workflows All of this makes more sense when we talk about actual use cases. For example, you can use Agentforce Grid to assist with case categorization, working with a list of cases, a prompt column to analyze them, and another prompt column to look at those analyses and categorize them based on theme, priority, or issue. Avi has also seen customers take advantage of Agentforce Grid for transcript and session analysis for customer-facing agents. You can use the prompt column to analyze, classify, and extract information from transcripts to make sure that everything is working the way you want it to work. Be sure to listen to the full conversation for more from Avi on Agentforce Grid. And don’t forget to subscribe to the Salesforce Admins Podcast so you never miss an episode. Podcast swag Learn more Salesforce Admins Blog Post: Admin Trailblazers Group Social Full show transcript
/episode/index/show/buttonclickadmin2/id/41061570
info_outline
How Agent Script Is Redefining the Admin Role
04/23/2026
How Agent Script Is Redefining the Admin Role
Today on the Salesforce Admins Podcast, we talk to Joshua Birk, Senior Director of Admin Evangelism at Salesforce. Join us as we chat about how Agent Script helps admins build more predictable and reliable AI solutions. You should for the full episode, but here are a few takeaways from our conversation with Joshua Birk. How Agent Script expands the admin toolkit The new Agentforce Builder gives admins new tools to create effective AI agents to help their orgs. Chief among them is Agent Script, which gives you more control than ever before over how your agents operate and behave. I sat down with Josh Birk to find out how it all works and why Agent Script redefines the admin role. Agent Script is a simple, high-level scripting language that lets you create complex instructions and actions for your agent to follow. You can step in as the human in the loop and create a framework for agent behavior and context, helping you build more predictable and reliable AI solutions. Redefining the admin role In simple terms, Agent Script lets you look under the hood at how your agents function. If you’re comfortable with coding, Script view allows you to make fast, precise changes and analyze error messages. Canvas view, meanwhile, uses visual blocks to make it easy to understand what’s going on with your agent. And of course, the Agentforce assistant is always available with suggestions if you get stuck. With so much more control over agentic behavior, Agent Script puts admins in the driver’s seat for how their organization will evolve with AI. You’re not just building a solution—you’re designing interactions between humans and agents. In the big picture, the role of the admin starts to look less like traditional system configuration and more like experience design, governance, and operational strategy. Getting started with Agent Script All of this requires a great deal of thought in terms of how you’re building new agentic solutions and rolling them out to your organization. Josh’s biggest piece of advice is to take it slow: “Don’t panic, learn Agent Script,” he says. Your existing agents will continue to work, so take your time to experiment with Agent Script to get a better understanding of what’s possible. Build some new agents and take it one step at a time. Listen to the full episode for more from Josh about what admins can do with Agent Script. And subscribe to the Salesforce Admins Podcast to catch us in your feed every Thursday. Podcast swag Learn more Salesforce Admins Blog: Admin Trailblazers Group Social Full show transcript Mike Gerholdt: This week on the Salesforce Admins Podcast, if you've ever been wondering why you can't just copy and paste your old agents into the new version, this episode is for you. I'm joined by Josh Burke, who recently walked our admin relations team through what's really changing with Agent Builder and Agentforce. And more importantly, why it matters. We're going to unpack a little bit of hybrid reasoning, what determinism really means for admins, and how Agent Script gives you even more control without losing all of that magic. So with that, let's get Josh on the podcast. So Josh, welcome back to the podcast. Josh Birk: Thanks for having me, Mike. Mike Gerholdt: Well, we know that a few people are vibing now because of the dulcent tones of Josh Burke. So in all honesty, you were in a team meeting last week and you were kind of updating the team on stuff that's coming out for new products and beta products. And the biggest thing that you always explain is like, so why is this important? Josh Birk: Yeah. Mike Gerholdt: And of course, every now and then you end your little skit with, "Thanks for attending my TED Talk." Josh Birk: Yeah. Mike Gerholdt: And I remember last week's meeting, I was like, "Oh man, that's a podcast. I need to do that." Josh Birk: Yeah. Mike Gerholdt: Because the way that you would explained what was new with Agent Builder and Agentforce, I was just like, "Oh, that totally makes sense to me." So this is where we're at and this is what I was hoping we would talk about. Josh Birk: Yeah. And I'll have to try because I kind of remember getting into a very weird, almost like conspiracy theory level stream of consciousness. Mike Gerholdt: Oh, okay. Well, it didn't feel that way. Josh Birk: Good. I think that's years of experience of thinking in streams of consciousnesses, whatever the plural of that is. So yeah, so I think to kind of recap a little bit, so there were two things that I think are kind of important to consider about the new Agent Builder. One is what we mean by hybrid reasoning and what we mean by determinism. And then the second thing is, where does Agent Script fit into that? So the question we were kind of tackling was, why didn't we just go back and revise the old builder? Why can't we just reiterate on it? Why are we starting completely new? Mike Gerholdt: And I think you even said, not to interrupt you, but to interrupt you, why can't I just move my stuff over? Why do I have to rebuild it? Josh Birk: And why can't I just move my stuff over? Why isn't it just copy and paste? And Agent Script is part of that. So the original engine wasn't hybrid, is I think the easiest way to put it. So this came with a conversation with product management where I was trying to describe the differences between the old builder and the new builder. And they're like, well, let's ... The old builder wasn't doing anything wrong, so much is that the new builder's doing something more. And what the new builder's doing that is more is that when we say hybrid, when we think of AI, we think of AI being autonomous, making its own decisions. So we had the Atlas reasoning engine that's like, "Oh, Mike is looking to find a description on a certain account. I'm going to take these actions. I'm going to put them together into a plan and then I'm going to try to make that work." What we didn't have was the human in the loop portion of that. And where Agent Script really comes into play is it allows users to basically be like, "In this scenario, I want you to behave like this." So when we say hybrid, we mean, yeah, we're letting the engine kind of do its own magic. But then we're also applying almost ... I don't want to say flow because that's such a loaded term for a Salesforce community. Mike Gerholdt: Yeah. Josh Birk: But well, let's go to the name, right? A script, right? A script that a human can actually control personality, control tone, control behavior. When you see this, do this, when you need to call it human. So kind of giving this very human-friendly dialogue that you can then apply to the agent. And so that's how we provide more determinism. So the reason you can't just copy and paste your old agent into the new agent is the old agent doesn't have that connection to Agent Script. And so it's literally missing a piece of the puzzle to run the engine kind of thing. Mike Gerholdt: Right. No, I think ... I mean, hearing you explain it, sometimes, at least as an admin, I was always like, "Oh, so they just came out with another version because they had to stick another layer of something on." Josh Birk: Yeah. Mike Gerholdt: Or like a car analogy, they changed the fuzzy dice. But this is, no, no, no, no. We're really moving from this version, which ran a certain way to an even better version. And that's the part that I feel like ... Because you brought up Flow, I feel like we've been through this with Flow. Josh Birk: Yeah, totally. Mike Gerholdt: We got like a business process ... Business management process is what it used to be called. And then that thing went through iterations and then we found a different engine to run it on. And then we had ProcessBuilder for a while and then now we have the new Flow. And it's like sometimes it's not just the interface that changed, but it's actually the guts behind it. Because I mean, I can't recall ... It's sometime between after the pandemic and today that AI came around. And I feel like that's the window that works in my brain because I can't put down a time. Josh Birk: Totally. Mike Gerholdt: Was it 2022 or is it 2023? I don't know. Post pandemic, before today, AI happened. But just when you thought, okay, I've kind of got this thing figured out, nope, all of this stuff changes. Josh Birk: Yeah. And it happens in technology, right? It happened with the Lightning Web Components. We really kind of had to go back and take the new ECMAScript format and take the new ECMAScript standard and really rebuild the way our web components work so that they work in a standard based way. So that they're more similar to React and more similar to these other frameworks. And there wasn't really a way to go back to Aura, now it's called, and just be like, "Hey, Aura, be more standards based." Mike Gerholdt: Right. Josh Birk: Because Aura was effectively just ... It was pre-standards is the easiest way to put it. So this happens, right? Now, if people are listening to this and like, "Oh gosh, I have all this work in my old Agent Builder, what am I going to do?" First of all, Salesforce does not like taking away people's toys. Mike Gerholdt: Right. We've learned that. Josh Birk: We've learned that. I've said this anecdote in workshops so many times because when we did release Lightning, one of the most common questions I got was, "Are you going to end of life Visualforce?" So I went to the product manager, might have been Skip at the time. And I'm like, "Hey, when would you end of life Visualforce?" And his response was, "When I pull up a dashboard and I see there are zero active users using Visualforce, and then I'd probably wait three months after that." Mike Gerholdt: Just in case. Josh Birk: Just in case, right? Mike Gerholdt: Yeah. Josh Birk: So the classic one is not going anywhere anytime soon. But I think the other important thing is a lot of our messaging when it comes to building out agents is that you're already an Agent Builder. You're already somebody who can build AIs because you know Flow, because you know Salesforce. Now you've learned topics, now you've learned actions and all of that kind of stuff. All of that is still true. It's all still true. And so you're still getting to use your existing skills in order to control it. It's really just adding the skill of knowing how to write out the Agent Script. Now, one of the cool, really cool things about ... Well, there's two cool things about the new builder that I think will really help people with that. One is the Canvas mode. And so Canvas mode takes what you write in Agent Script and puts it into a visual UI interpretation. And so this is very handy for two things. Number one, it gives you a little bit of kind of a predictive window as to what your script is going to be doing. It also gives you a very visual way of thinking about it. It's also a really neat way to go look at somebody else's Agent Script and translate it. So you don't have to read through all the thing. You can flip over to Canvas mode and be like, "Oh, that's trying to get these parameters in order to do these actions." The other thing going back to vibes and this new AI coding AI is that you'll have an AI assistant in Builder to help you build the AI. So you're not alone. Agent Builder itself will also help you create these things out. So my biggest statement back in the Lightning web component today was don't panic and learn lighting. And now it's, don't panic and learn Agent Script and you're going to build out some really powerful solutions. Mike Gerholdt: Well, and I think back to ... I mean, I was chatting with Jennifer today too, and just the way that we started using AI. And I remember, I mean, not that long ago doing workshops and saying, "Okay, you need to tell the AI your role, its role. And then what you want it to do and what it can do and what it can't do." And for everything, whatever model you were using, I remember writing prompts a certain way. And I feel like for this and with Agentforce, especially for admins, this is the least set it and forget it kind of thing. Josh Birk: Yeah. Mike Gerholdt: Because you can always go back and make it better. Josh Birk: And tweak it. Yeah. Mike Gerholdt: And this is- Josh Birk: And tweak it in theory. Yeah, exactly. In very small corners too. Mike Gerholdt: Small corners that make a huge difference because like with Flow, I mean, half the time I'm just excited that I got it to do what I needed it to do. And then I look at what Jennifer built and I feel like I'm over here rubbing two sticks together. Josh Birk: Together. Mike Gerholdt: But with Flow, that's your goal, right? You just want that, okay, boom, it's done. But with agents, people are interacting with them, they're asking them questions, I can make this so much better and I can make this better. Here's the clue when people stop using them. To your point of when you would replace Visualforce. Well, if you're looking at your Agentforce dashboard and seeing, "Hey, your users aren't using it." well, now might be a time to like, "Well, let's switch over, let's round some edges, let's change some things." And I would say this is like an every two weeks kind of thing. Which sounds crazy, but the amount at which you're going to find feedback from your users. And the amount of rounding of edges, I worked myself into an English problem here. It's going to be like, you're going to find like a star and then it's going to look like a ribbon of rounded edges that you have to work on. Because as you use that new builder, now your users are happier and being more proficient. And I think like even today, when Jennifer and I were talking, we were talking about building Gems in Gemini. And I said, "One thing that I do is I'll actually have another window open and ask it to refine my instructions in Gemini." Josh Birk: Oh, yeah. Mike Gerholdt: Because the way that I write the instructions works for me, but maybe not for it and it can refine it. And I've seen it take thousand word prompts and reduce it down to 200 and it's actually faster. And so having all of that is sometimes there's a lot to keep up with. But it's all for the better because now you're like click click, oh wow. And then you get that ... I think it's always, at the end of the day, the admin is going after that first look on a user's face and they're like, "Ooh, this- Josh Birk: Nailed it. Mike Gerholdt: ... just made my life so much easier." Josh Birk: Exactly. Yeah. And I think to kind of append to that, again, not to overuse this analogy of Visualforce. But it's like don't be in a rush to go and recreate your existing agents in the new Agent Builder. If you have a new agent you're building, I would start with the new Agent Builder and go from there. Two reasons, don't fix what's not broken. And also you'll learn more about Agent Script and things like that. So when you do decide to move your old agent to the new builder, you'll be more educated on how to do it. Now, huge forward-looking statement, asterisk, safe harbor, there is a conversation internally about creating a porting tool of some kind. It's on a roadmap somewhere, no guarantees. Mike Gerholdt: Oh. Josh Birk: But I do think people should know where we are looking at that kind of thing. So stay tuned because we do want to make this as easy as possible. Mike Gerholdt: Yeah. Yeah. But also there's some joy in rebuilding things and maybe that's just me. But I've always- Josh Birk: Seems like part of the tech world. Yeah, exactly. Mike Gerholdt: Yeah. I mean, there's that and there's also, it reintroduces you to things that at one time you were good at and brings it back. And then I think too, anytime that these new features come out, one part is, okay, well, here's the tech to change it. But also, has the process changed? Has the stuff that people do internally changed? And that might also be true. And the other point you brought up, which was really salient, just because you can change it, doesn't mean you should right now. Josh Birk: Yeah. Mike Gerholdt: One thing that ... And I was a part of this, doing a big org rollout. What are the other changes that your users are experiencing within your organization? And so you adding to that, is that one layer too many? Or when would be a better time? Like we always joke, like you're not going to roll out a sales opportunity change the last week of the quarter. Josh Birk: Right, right. Mike Gerholdt: So picking your timing, this means that gives you time to test. Josh Birk: Yes. Yeah. And I think this goes into a lot of the conversation we're having about admins in the AgentiCare. Like what kind of a steward are you being? And how are you using those existing instincts and skills as an admin to not topple over the apple cart, but now you're doing with AI? Mike Gerholdt: Right. Because in my opinion, admins are getting paid for their judgments. Josh Birk: Yeah. Yeah. Agreed. Mike Gerholdt: Josh, thanks for coming on and helping us understand the new Agent Builder. Josh Birk: Thanks for listening to my TED Talk. Yeah. Mike Gerholdt: I knew you had to fit that in. And we've got just enough time that Daryl can hopefully get his boat from home to the internal ... It's not internal. Inside the podcast joke. Josh Birk: Inside the podcast joke. Mike Gerholdt: You have to go back to the Daryl Moon episode- Josh Birk: Yeah, exactly. Mike Gerholdt: ... and then it all makes sense. It's the key to unlocking the mystery of the Dan Brown episodes. I don't think so. Josh Birk: I love it. Mike Gerholdt: Anyway. Josh Birk: I love it. Mike Gerholdt: Have a good day, Josh. Thanks for coming on. Josh Birk: Cheers, my man. You too. Mike Gerholdt: Huge thanks to Josh for coming on very impromptu and turning what could have been, I think, a little confusing of an update into something that actually makes sense. New engine, new script layer, AI helping you build AI. Awesome. I like it. So remember, don't panic, learn Agent Script, and it's all about having fun. And like any powerful tool in Salesforce, it's less about flipping a switch and more about steady improvement over time. So if this episode helped you clarify your next steps, share it with another Salesforce admin who's navigating some AI right now. And until next time, we'll see you in the cloud.
/episode/index/show/buttonclickadmin2/id/40979540
info_outline
How Salesforce Built a Scalable AI Puzzle App in Six Weeks
04/16/2026
How Salesforce Built a Scalable AI Puzzle App in Six Weeks
Today on the Salesforce Admins Podcast, we talk to Jagan Nathan, Senior AI Architect at Salesforce. Join us as we chat about how he built a Slack app for Salesforce’s “Million Dollar Puzzle” ad, where millions of concurrent users raced to solve riddles by chatting with Slackbots. You should for the full episode, but here are a few takeaways from our conversation with Jagan Nathan. The tech behind the “Million Dollar Puzzle” contest If you were watching the big game, you might have seen Salesforce’s “Million Dollar Puzzle”. As soon as the ad aired, the race was on for contestants to solve puzzles by chatting with Slackbots to discover the location of a secret vault. My guest this week, Jagan Nathan, built the Agentforce-powered Slack app that made everything possible. They needed Slackbots that could act as a conversational gateway for millions of concurrent users. And with a million dollars on the line, they needed to be sure it couldn’t be tricked into giving away the answer. Even more incredibly, Jagan pulled all of this off in only six weeks. I sat down with him to find out how he did it and what he learned along the way. Using AI to build quickly at scale Just like with any project, the first step was to gather requirements—though it’s more fun when your stakeholder is the “Puzzle Master.” Jagan and his team needed a thorough understanding of what they were dealing with and how they could translate those gaming mechanics into the application. The clock was ticking, and AI was pivotal for accelerating the development timeline. Jagan and his team used Salesforce Vibes for quick prototypes and wireframes to help them decide what to build. But the development team still needed to take these ideas the rest of the way. “AI cannot help us solve all of the architecture problems,” Jagan explains, “we have to have a human in the loop.” With millions of concurrent users, they needed to do thorough testing—and quickly. Luckily, they could use Salesforce Scale Center to stress-test for performance issues and identify bottlenecks so they could be sure that when the ad ran, the app would work flawlessly. Designing for security with a million dollars on the line I know this might be shocking, but when you’re holding a contest with a million-dollar prize, some people will try to cheat. So Jagan and his team needed to make sure there were plenty of guardrails in place to make sure someone could win it fair and square. They needed to start with a security mindset and think through any security vulnerabilities as they designed the application. Einstein Trust Layer was crucial for toxicity detection and monitoring for anything malicious, like prompt injections. Most importantly, they were very careful with what information the Slackbot knew and what it didn’t. It didn’t have the solutions to the puzzles, so even if someone managed to crack it, they wouldn’t be able to get very far. Instead, puzzle answers were always validated by humans. There’s a lot more from Jagan about building for scale quickly, so make sure to take a listen. And don’t forget to subscribe to the Salesforce Admins Podcast so you never miss an episode. Podcast swag Learn more Salesforce Admins Blog Post: True to the Core Deep Dive: Salesforce Admins Blog Post: Admin Trailblazers Group Social Full show transcript Mike Gerholdt: When you think about building on Salesforce, it's easy to focus on features. But today's admins aren't just implementing features. They're designing systems that have to perform, scale, and hold up under real world pressure. In today's episode, I'm going to sit down with Jagan, an architect who helped deliver a high stakes, high scale experience serving millions of users through a custom Slack-based AI system. We're going to unpack what it actually takes to compress months of work into weeks and how to design for trust and guardrails from day one, and where human judgment still matters in an AI-driven architecture. So if you've ever wondered how your role evolves from building flows to orchestrating full systems, this is the conversation because this just isn't about speed. It's about responsibility at scale. Now if you enjoy this episode, hit Subscribe, share it with a fellow admin and let's get Jagan on the podcast. So Jagan, welcome to the podcast. Jagan Nathan: Hi, Mike. Thank you for having me. Mike Gerholdt: Yeah. Well, I was excited when you sent me the Slack DM about some of the projects that you've worked on here at Salesforce. But for people that don't know you or maybe didn't listen to the episode of the Developer Podcast you were on, could you tell us a little bit about what you do at Salesforce and the fun project you got to work on recently? Jagan Nathan: Sure. Hey everyone. I'm Jaganir. I'm architect part of our AA practice team here at Salesforce, building agents for our customers. This is my third podcast on our channel. My previous episodes were focused on event monitoring and threat detection. Mike Gerholdt: Wow. Let's talk about some of the stuff that you got to work on around the big football game that happens in February that Salesforce had an ad on. Jagan Nathan: Yeah, sure. Very excited. This is our first ever online puzzle app, which was built entirely on our Salesforce platform. Mike Gerholdt: So you got to be a part of that. I'd love to know from a Salesforce admin listening to this, we used the platform for the puzzle. Can you give me a little insight into that? Jagan Nathan: Yeah, so let's unpack this. So what we did is we didn't just build a chatbot. We deployed our custom Slackbot, of course, powered by our Agentforce, which acted as a conversation gate for millions of participants grounded in real-time data. So we just collapsed a nine-month roadmap into just six weeks, which is 42 days. Within that, we designed iterator and we went live on day of February 8th. Mike Gerholdt: Wow. Nine-month roadmap. Holy cow. That's insane. I mean, can you talk a little bit about the architecture problem solving and how you moved so fast so quickly? Jagan Nathan: Yeah, sure. Of course, we are a customer zero company. So we leverage our internal tools and the external tools, what we have developed. So for this entire application, we use our Agentforce Vibes to accelerate the development. We quickly do a lot of wireframes and the prototypes, and then we figure out what sort of user experience and what sort of applications we need to build using the power of Agentforce Vibes that accelerated our development timeframe to start with. Mike Gerholdt: Oh, that's nice. I mean, I've definitely seen Vibes do a lot of things. I'm assuming we really took it out for a test spin on this one. Jagan Nathan: Yeah. So we use Agentforce Vibes to do this. And then we also leverage our scale testing product because this particular application, we anticipated there's going to be at least millions of users who is going to access this application concurrently. So performance is super important for this application. So we leverage scale testing product to identify quickly and resolve all the problem bottlenecks as well. Mike Gerholdt: Yeah. Wow. I've had some talks with PM for, was it Scale Center? Is that what you used? Jagan Nathan: Yep. Yes. Mike Gerholdt: Yeah. And we've put out a couple of blog posts about those. So for admins that aren't familiar with what Scale Center is and what some scale testing helps them do, what did you use it for? Jagan Nathan: Yeah, Scale Test is the performance evaluation tool. So that gives a lot of metrics. Before customers used to run some automated performance testing to figure out what sort of performance bottlenecks they have in the ACRM instance. But with the power of Scale Test, we can write a test plan creation. We can do a test environment set up. And we can also simulate all those real-time performance challenges, and then we can schedule those test trend to see where exactly fails and at what threshold it fails so that we can understand the spike and then we can fine tune our application. Mike Gerholdt: Okay. That's super helpful. I mean, was there any surprises that happened in your testing? Jagan Nathan: Oh, yeah. Since we anticipated there's going to be at least millions of concurrent users, there's going to be a lot of DB rights back and forth. And then we ran into a lot of issues. We were able to figure out with the help of scale testing, we figured out all those in the sandbox, and then we fine-tuned our code and the logic and everything to make sure it is scalable for concurrent users as well. Mike Gerholdt: That sounds like a lot. Holy cow. I don't think I've ever built an application where I had to plan on a million people using it concurrently. So you talked about Agentforce Vibes. I'm sure we leaned into a lot of AI to build this. How did you decide really what AI should do versus what humans should still control during the project? Jagan Nathan: Yeah, that's a great question. So of course we can use AI, but AI cannot help us solve all the architecture problems. One of the architecture problems, we have to use human in the loop. For an example, when we started designing this application, considering the scale of users, we thought just by writing a prompt, it's not going to solve the problems. Prompt is going to give, based on the request prompt is giving the response back, but that alone is not sufficient enough. So that's where we use humans power to understand and architect well for this [inaudible 00:06:50] game. Mike Gerholdt: Yeah. Wow. On top of that, you got to think of guardrails because I'm sure somebody was thinking, "Well, since Slackbot was in use, what if somebody just asked it, what's the answer?" That seems like the most obvious guardrail to put in place, but how did you sit down and think about some of the guardrails to put in place for an experience like that? Jagan Nathan: Yeah. So there's an aha moment here. So when we built this custom Slackbot, we intentionally built in a such a way that this custom Slackbot doesn't know the puzzle answers. So even if someone tries to crack the puzzle Slackbot, they would not be able to get the answers out of it. So that is the first so that no one walks away with the puzzle answer, right? Mike Gerholdt: Right. Jagan Nathan: So that is the first thing what we did. And then the next thing what we did is automated toxicity detection at the hedge. So what we tried to do is we leveraged, of course, the power of Einstein Trust Layer and then it's not like a traditional AI chatbot. So we just built intentionally a custom Slackbot with all those automated toxicity detection so that if the Slackbot finds some harmful response or some sort of response which is not supposed to do it, if the user on the other side, if the user is a bad actor trying to do some prompt injections or whatnot, our platform is able to monitor and mitigate the risk immediately. It's being very proactive stage of monitoring. Mike Gerholdt: Yeah. No, I guess I just thought the Slackbot would have access to the answer and you'd just have to guard it really well. But if you set it up and never give it access the answer, then it can't accidentally hallucinate and give the answer. So wow, that was probably a little bit of planning on your end. So looking at what you built and deployed, if a Salesforce admin wanted to recreate some of the best learnings that you had from this, what were some of the key takeaways that you had? Jagan Nathan: Yeah. So I had that security mindset to start with. Let's say you are a bad actor or else you are trying to act the system, what sort of loopholes you might find in the system and then find all those security vulnerabilities, why you designed the application itself. It's like having a security mindset is super important. And that too for the scale of the cash prize is one million. So definitely there's going to be a lot of participants going to crack the Slackbot or else they try to trick the Slackbot and try to get the puzzle's data out of it. So I would say security mindset is super important. And then start with the understanding of, basic understanding of how prompts work and then try to build a Hello World app in Slack to start with. Mike Gerholdt: Yeah. Did you have a whole team of people that were just, I guess it's called negatively testing because there's always positive testing, which is test it to make sure it does what it's supposed to, but then there's negative testing, which is to make sure it doesn't do what it's not supposed to, right? Jagan Nathan: Yes. So we did advisory testing as well. So of course, we used the power of AI. We built our own agents to try to craft this agent to see where it bakes. And then we try to enhance our prompts and all the safety guardrails to make sure. We did a ton of testing during our design and implementation phase just to make sure Slackbot is not supposed to provide any information which is not needed or which is kind of out of privacy zone. Mike Gerholdt: Yeah. Wow. So given the scale of everything that you did, what is something that you maybe hit a limit with AI that you didn't know would exist? Jagan Nathan: What we felt down the road is like, AI cannot solve all the problems for sure. That too for the scale of millions of concurrent users trying to access the system. We thought there might be places in which there might be some timeouts happening, but knock on the wood, nothing happened. We were able to build a scalable application. Now, we don't rely 100% on AI. We also added a human in the loop, for example, some sort of puzzle answer validation, mainly the final puzzle answer validation. We don't just rely only on the AI. We use a human in the loop. So that we brought in experts on the puzzles who validated the answers and lot of stuff at the backend. Mike Gerholdt: Yeah, that's interesting. What was it like to have to translate a puzzle into a technical requirement? Because I feel like a lot of Salesforce admins often get business processes that can sound like a puzzle and they have to translate that into a technical requirement. Jagan Nathan: Yeah. Great question. That was very interesting and challenging because not all of our teammates worked on the puzzles or solved the puzzles before. If you take me as an example, right? I haven't solved any puzzle in the past. I went through the basics of understanding what sort of puzzles exist in the real world. Some are logical puzzles, a lot more Sudoku puzzles, some are mathematical puzzles, some are geolocation puzzles. So for us, it took some time for us to understand the basics of what sort of puzzles we have. And then we had conversations with the puzzle masters and then who built this puzzle. We tried to understand from the puzzle master what sort of application they wanted to build because they know very much on the gaming side and we know very much from the technical side. It goes hand in hand. That was very interesting and challenging conversations we had to understand. It took some time for us to understand and translate the gaming mechanics into our application. Mike Gerholdt: Wow. Okay. So be honest, how cool wouldn't it be to have a title named Puzzle Master? Right? Jagan Nathan: Yes. Mike Gerholdt: So one of the last questions, because I bet you use Slack a lot as the project team to get things done. I've noticed as I work at Salesforce and we use Slack in different channels, I've noticed changes in behavior, ways that we work faster with Slack. Was there something you left this project with where you're like, "Oh, I'm going to start posting this way in Slack or I'm going to start sharing information this way in Slack," because it was something that actually was a way that you worked in that team. For example, I've noticed that when we have really long threads rather than posting one big post that could take up a lot of screen, somebody will post a comment thread about a topic and then put all of that into the comments because then it keeps their feed kind of cleaner. Was there anything like that that you kind of learned as like, "Ooh, I'm going to start doing this more often now in Slack?" Jagan Nathan: Well, yeah. So what we did is when we started working on this project, we had a 14 member team, few members were focusing on the technical side, few members were having conversations with the puzzle master. So we used Slack as a project management tool. So what we did is we created a Slack Canvas with a list of team members and then what sort of priority task we need to work on. And then we automated to the next level by adding a Slack list as well. We created a list, like what is the roles and responsibilities for each team member? And we started tracking the list. And then every week we were running the Slack workflows. We extensively used the Slack workflows. We created a ton of workflows, one workflows for summarizing the Slack channel so that what happened in this one week's ... Because see, we had at least six weeks to develop and build and deploy, right? Mike Gerholdt: Yeah. Jagan Nathan: So each week we were running the Slack summary workflows to understand what is the latest going on around them. And then we were extensively using Slack, mainly the Slack Canvas and then the Slack list to start with. Mike Gerholdt: Yeah. Wow. I love building workflows. I tell you, they're really cool. I can almost build too many sometimes. Well, I appreciate you coming on and sharing what you could about this. I think the amount of work that was completed for this project and in the amount of time is super incredible and I'm sure it was quite the learning for you. So it also teaches us that even the biggest projects we can still accomplish very quickly. So thanks for coming on the podcast. Jagan Nathan: Thank you for having me, Mike. Mike Gerholdt: So it was great of Jagan to come on and share his experience on that project. I think it's a good reminder that building on Salesforce today means thinking beyond automation. It's about really designing systems that are resilient, trustworthy, and ready for real world scale. From AI guardrails to perform testing to human in the loop decision-making, this is the work that the modern admin is balancing speed with responsibility. Now, if you found this episode helpful, share it with another Salesforce admin who's thinking bigger about the systems they run and making sure that you're subscribed so you don't miss what's next. Until next time, we'll see you in the cloud.
/episode/index/show/buttonclickadmin2/id/40871185
info_outline
How Admins Can Get the Most Out of TDX 2026
04/09/2026
How Admins Can Get the Most Out of TDX 2026
Today on the Salesforce Admins Podcast, we talk to Jennifer Lee, Lead Admin Evangelist, and Eliza Riley, Content Manager for Admin Marketing at Salesforce. Join us as we chat about what’s coming at TDX and how to get the most out of your visit. You should for the full episode, but here are a few takeaways from our conversation with Jennifer Lee and Eliza Riley. Connect with product leaders at TDX TDX is around the corner, and I sat down with Eliza and Jen to talk about must-see content for admins and how to get the most out of your visit. One thing you won’t want to miss out on this year is Sneak Peeks, a special experience in the theater where you’ll be able to see new features in action. We’ll be showcasing things like the new App Studio and Setup with Agentforce so you can get an idea of what’s coming. There will also be a Q&A with the product teams so you can give feedback and better understand the roadmap. There will also be True to the Core Deep Dives covering flow and automation, reporting and analytics, Agentforce, and low-code and pro-code development. These extended Q&As offer you a chance to connect with product leaders and ask all of your burning questions. Finally, if you have a thorny problem that needs solving, you can sign up for a 1-on-1 Ask the Expert session with a Salesforce engineer or product leader. See the sights We’ve been talking a lot on the pod about Agentforce Vibes, so maybe it’s time to see it for yourself. In the Agentforce Vibes Zone, you’ll be able to get hands-on with how you can build using natural language. There will be demos, a guided project, and sessions to help you get started. You’ll also want to check out the Hackathon Showcase in the keynote room, where the three finalists will pitch their builds live to the judges. As Jen says, it’s always interesting to see how different people solve problems and get some inspiration for what you’re building in your org. If you’re coming alone, make sure to stop by the Community Cove. It’s the spot for networking with other admins and other folks in the ecosystem, and a great jumping-off point for exploring TDX. How to plan for TDX As you’re getting ready for TDX, it’s important to remember to balance planning with flexibility. “You're going to be connecting with people,” Eliza says, "you might see a cool activation that catches your eye, or a robot you might want to stop and grab a picture with.” Wear comfortable shoes, bring water and snacks, remember that some sessions require headphones, and make sure you have a swag bag. Most importantly, come find us and say hi. Make sure to listen to the full episode for more on what’s coming at TDX. And don’t forget to subscribe to the Salesforce Admins Podcast to catch us every Thursday. Podcast swag Learn more Salesforce Admins Blog Post: Salesforce Admins Podcast Episode: Admin Trailblazers Group Social Love our podcasts? Subscribe today or ! Full show transcript Mike: If you're heading into TDX thinking it's just another event, this episode might change how you show up entirely. Today, I'm joined by Jennifer and Eliza to break down how to actually get the most out of TDX26, not just attend it. We're going to talk about everything from Sneak Peeks and Ask the Expert zones to hands-on Agentforce experiences and so much more. Most importantly, how these moments are going to help you design better systems, not just learn new features, because this isn't about collecting swag or just session notes. It's about connecting with the people building the platform and shaping how your organization runs. So, if you're serious about evolving from admin to orchestrator, we got your game plan. So, let's get Jen and Eliza on the podcast. So, Jen, Eliza, welcome to the podcast. Jennifer: Thanks for having us. Eliza: Super happy to be here. Mike: It's going to be fun. So, Jen, you're a veteran of the podcast and in the community. Tell us a little bit about what you do at Salesforce, and then, we're going to get into what we do for TDX. Jennifer: Sure. I'm one of a few admin evangelists on the team. So, some of the things that I do on a daily basis is write blogs, create video content, and present to all of you admins out there. Mike: Just a few. Eliza, you're like our secret Alfred in the bat cave. I feel like all of us evangelists come back with torn suits, and our Batmobiles have a flat tire and you fix everything up. But you also did a whole bunch of stuff at TDX last year, but what do you do on the admin team? Eliza: Yeah, I know you guys are really on the front lines. So, I'm a content manager on admin relations, and I focus on creating resources and storytelling to help admins grow into more strategic roles. And I also lead our admin blog. So, really helping to translate just everything that's happening across Salesforce into what actually matters day-to-day. And that includes a lot of coverage on TDX, which I'm really excited about. Mike: Yeah, we have a lot planned. To be fair, you also did a showdown last year at TDX, if I recall. Isn't that right, Eliza? Eliza: Yes, we did. That was super fun. We had a few members of the community come and showcase their best Agentforce use cases. We had some prizes, and it was just a really great time. Mike: Right. It was. You had one vivacious MC. Should hire him back. Let's talk about this year though, because Eliza, you wrote a blog post to help admins get ready and write down their list of stuff they can't miss for TDX. And the first thing is the Sneak Peeks area, which you and Jennifer are working on. So, let's hear a little bit about that first. Eliza: Yeah. So, Sneak Peeks is this really special interactive theater experience. And these are really building on the success that we saw at Dreamforce. So, if any of you attended Dreamforce last year, Jen did an incredible job in the Admin Meadow creating this special exclusive look at what's coming next for Salesforce products. So, we're building on the success of that this year, and we're going to be showing you quick demos of all of our in-progress innovations, and then, opening it up for live Q&A with the product teams. And so, what's really cool about this for those of you attending in person is that you might be some of the first people to actually see these developments in action. And then, if you're not able to join us and you're watching from home or tuning in later, we'll be covering some of these on the admin blog as well. So, you definitely won't be missing out on any of the fun. Mike: Oh, nice. Jen, you got to peel back a layer. Tell me, give me something. Give me a sneak at the Sneak Peek. Jennifer: Well, first I want to say that as a former customer, when I went to TDX, one of the things that I look forward to was seeing the roadmap and interacting with the PMs. So, I'm really excited to be able to bring this to all our technical audiences. But a couple of things that you will be able to peek into, we'll be introducing the new App Studio. There's also Salesforce Release Manager. So, think of this as being able to say, for these releases, "I want to enable these things in my org." That's the idea behind that. And then, we're just bringing on a lot of... We have three sessions on flow, like thinking about new flow design or what's coming up with screen flows or how to manage your flows. We're also bringing in set up with Agentforce, not only in Salesforce itself, but also in Slack. So, there's just a lot of cool things, but I'm just going to tease a few. Mike: Yeah. No, thanks. You got to show up, but that's why it's called a sneak peek, right? I'm excited for this. I agree. When I was a customer, being able to just see what's new, take those notes, most of the time feel, like the plane ride home, you could be like, "Oh, cool. I don't have to build this because it's already going to come as a feature," is something that I always look forward to. Now, you mentioned we could do some Q&A with the product teams at your Sneak Peeks, but we also have something called Ask the Expert Zone. Can we talk a little bit about that? Jennifer: Yeah. So, we had that also in the Admin Meadow at Dreamforce, and it was a huge success. So, think of it as you come to TDX and you have this burning question in the back of your head or this problem that you're trying to solve for and you're just hitting a wall, you can come and talk to our experts. And the difference between what we did at Dreamforce and TDX is now, we have specific topics. So, instead of going to, let's say a generalist that's supposed to know all the platform, and who possibly can because Salesforce is so huge? There's no way. You're going to go and talk to a specialist. You have that burning of question about automation. You're going to talk to the flow expert. Or you need help with getting started with Agentforce. You're going to talk to the Agentforce expert. So, we have these various topics, six different topics, and you come during that scheduled time and you'll be able to have one-on-one discussions with those experts. Mike: I like that because we did a version of that, and I volunteered for it, and I think it was just about every other person, I could answer questions. Jennifer: Yeah, it's hard. Mike: I know. Man, I just felt bad, and I was like, "Well, I can't really answer your question, but do you want to work through the problem together and maybe we'll stumble across something?" One of the things that I think is important and along those same lines, at a surface level, it's like, "Oh, cool. So, I'm going to be able to talk to Data 360, or flow, or user access and governance." I see those as topics. Waiting until you're at the event, Jennifer, is not the best idea. If you were a customer today, you have 14 days to Dreamforce, oh my goodness, to TDX, what would you do as a customer to get ready for those Ask the Expert sessions? Jennifer: I would hone in on what are the top things that I want to know from that expert? Come up with some questions to bring to the table versus just showing up and coming up with questions off the top of your head. Or if you have a problem with the solution, bring your laptop and show the person, "Here's my problem. Can you show me where I'm going wrong?" That way, you're not generalizing it, and then, they could really help you because they're actually seeing the thing versus saying like, "Oh, well, I think it might be this," or, "Maybe it's this, but I don't know because I don't know the details of your problem." Mike: That's really good. And when we did that version of Ask the Experts, I had somebody print off their entire org schema and bring it. Jennifer: Wow. Eliza: Oh, wow. Mike: So, yeah, it was awesome and also kind of sad because I was like, "Man, it's a whole forest of trees you just killed, but I know exactly how your org's set up." It's wonderful. Speaking of experts, we have something new, and I know Kate's been on to talk about it, but Eliza, True to the Core Deep Dive, that sounds new. What's that? Eliza: Yes. This is one of our new activations or tracks that we're really excited about this year. So, True to the Core Deep Dive is essentially just an extension of the larger True to the Core keynote that we all know and love. So, it's going to give everybody the chance to just go a little bit deeper into specific topics. So, they're essentially extended breakout sessions letting you connect with the product leaders and ask your really specific questions. So, we will have breakouts on flow and automation, reporting and analytics, Agentforce, and low code and pro code development. And actually, a couple of these are going to be live on Salesforce Plus. So, it's a really great chance to connect with product leaders and just be able to attend that extended Q&A. Mike: Yeah. There's definitely a theme developing here across all three things that we talked about, which is access to the product leaders. Eliza: Definitely. I think that's a really key differentiator at TDX this year. I would say that there are just really more opportunities than ever for you to actually connect with the people building the features that you're working with every day. Mike: Now, one of the things is the virtual TDX Hackathon, which I know Josh on our team has been managing a lot. If you're not participating, that's something really cool to go see because I think we have... Correct me if I'm wrong, but I think we have an actual kind of showcase where they're going to get up and pitch their hacks. Am I right, Eliza? Eliza: Yes. And it's not just a showcase. It's actually even bigger than we've done before. So, it's going to be live in the keynote room. So, really getting everybody up on that big stage. And the three finalists will actually be pitching their builds live in front of a panel of judges. Mike: Wow. No pressure there. Eliza: Yeah, seriously. Mike: But I think that's really cool. Jennifer, if you were a customer and you're like, "Well, I didn't participate in the Hackathon," sometimes going to see what other people are envisioning might actually spark an idea for something that you're trying to solve back at your org, right? Jennifer: Oh, exactly. At Dreamforce, we had the Hackathon and I attended that. And it's always interesting to see how people solve for things and you're like, "Huh, I didn't even think about that piece, and maybe I should consider that and go back and use that in your implementation." So, yeah, it does definitely inspire and get those creative juices going. Mike: Right. On top of just watching people try to pitch, I think that's really fun too because I always love to learn watching other people speak because I would envision, well, here's what it could be like if I had to pitch my app to a board of directors or a president of a company as we're really going enterprise-wide as an admin. The last thing that I see is Agentforce Vibes, which I've had people on vibe coding on the podcast, and I've seen some dry runs. I can't tell you the session because you need to go to them, but there are some presenters in the admin track that have some really cool use cases for vibe coding. And so, I think we have the Agentforce Vibes Zone. Eliza, do you know anything about that? Eliza: A little bit. Yeah. So, it's an immersive hands-on space. And I think what's really cool about the Agentforce Vibes Zone and what we've done a really good job with is just making sure that it's not just for developers. I think no matter your role, you can definitely benefit. And so, it's really just designed for anyone that's ready to expand on how they build using natural language. So, there will be a series of Agentforce Vibes demos, and then, I think they're doing a guided hands-on project so you can apply what you've learned because as you know, if you've come to a Salesforce event, it's all about getting hands-on. But there's a lot of great vibes content across the event from sessions to this specific zone. So, I think if you're an admin and you're just trying to dig in or get started, it's definitely a great place to do that. Mike: Yeah, I'm excited for it. Let's talk about conferences in general, because it's been a while since we've done Dreamforce, and we've had winter and a time change. Jennifer, if you were a customer today listening to this podcast and thinking, oh, I got to pack for TDX, what are some things that maybe you bring now that you wouldn't have brought five years ago? Jennifer: Unless you really need to use it, I leave my laptop in the hotel just because lugging that around all day isn't fun. Mike: They still haven't gotten any lighter, have they? Jennifer: No. Mike: They're still 10 pounds. Jennifer: No, they feel like a brick, ton of bricks. I would definitely bring your most comfortable walking shoes. Don't bring the pair that you just bought. No, that's not a thing. Bring your most comfortable shoes. Definitely bring a water bottle. Walking around, you want to stay hydrated. Bring some snacks in your backpack because sometimes you think you have time to run and grab something and you're running between sessions. Have that little candy bar or whatever it is, a pick-me-up. Yeah, that's helpful. And then, I also bring a bag just in case you pick up any swag along the way because they'll- Mike: Just in case, as if it's an option. Come on. Jennifer: But bring a thing where you could take notes. So, whether that's electronic, or a notebook, or old school, bring something that you can jot notes or take screenshots of things. There's also will be available in the app, PDFs afterwards, but I always like taking a screenshot, and then, writing notes afterwards. Mike: Yeah, I definitely... So, there will be AI-generated session summaries on all of the sessions in the app, but being there and taking notes is usually... The notes that I take always make more sense to me, which is exactly how it should be, I suppose. Eliza, is there any special prep you do to get ready for TDX? Eliza: Well, I would say definitely pack your headphones because we have some sessions where you'll want your headphones to catch that session audio. Mike: Oh, that's a good one. Eliza: Yeah, that's one that people forget. You don't think about it, but got to have those headphones. I think for me, with these conferences, it's so good to have a game plan. I think when you roll up first thing in the morning, you just have this whole day in front of you, and it can be hard to think about what you'd like to do. So, I'd highly recommend using Agenda Builder to really plan out your perfect schedule, but I think you should also leave room for spontaneity because you're going to be connecting with people. You might see a cool activation that catches your eye. Sometimes there are robots wandering around that you want to stop and grab a picture with. Jennifer: Or characters. Eliza: Or characters. Yep, absolutely. So, don't jam pack it, but it helps to come in with a little bit of a game plan. Mike: Yeah. Dreamforce had puppies for a little while too. I know. Eliza: I missed those. Mike: We probably won't [inaudible 00:16:32] puppies this year. I know. One thing that I think is different that I'd like both your perspectives on. So, travel budgets are tightening. Companies are sending you to... Sometimes you have to pick and choose, do I go to TDX or Dreamforce? And sometimes it's, well, we can only afford to send you. We can't afford to send the other three admins. And so, you're there flying solo. What would your advice be, Jennifer, on making friends at TDX and introducing yourself? Jennifer: Oh, Mike, you asked the introvert of the team. Mike: I know. All of us admin evangelists are really introverts. We just play extroverts [inaudible 00:17:21]. Jennifer: I know, right? I tend to look for a familiar face, but also for someone who might be by themselves, because if I'm by myself and they're by themselves, why not connect? And then, you could be a team, and then, figure out, hey, what sessions are you going to? Because maybe they might be going to sessions that you didn't even think of. But also if you're attending a conference and your teammates don't go, I would take copious notes so that then, when you go back to your company, you can then knowledge share, right? You weren't there, but here's the things that I learned and here's the PDF to that presentation, and give them a little walkthrough of what they missed, but also we're going to be recording a bunch of sessions this year, right? Mike: Oh man, we're recording so many sessions this year. It's insane. You have no idea. Eliza, how about you? How do you make friends at events or how would you advise admins to connect with each other? Eliza: Oh, I consider myself a little bit of an introvert as well. So, I think if I'm in a specific area or session that is really, really interesting...
/episode/index/show/buttonclickadmin2/id/40773910
info_outline
What Is My Trust Center and How Does It Help Admins?
04/02/2026
What Is My Trust Center and How Does It Help Admins?
Today on the Salesforce Admins Podcast, we talk to John Maxey, Senior Product Manager at Salesforce. Join us as we chat about how My Trust Center can help admins communicate incidents, plan releases, and operate with transparency. You should for the full episode, but here are a few takeaways from our conversation with John Maxey. From static status pages to personalized trust When I was early in my admin career in 2008, keeping track of status updates was as simple as loading up Salesforce Trust. These days, with so many different products and services, it’s gotten a lot more complicated. That’s why I was so excited to sit down with John Maxey. He’s working on My Trust Center, a personalized, authenticated experience that only shows you information that’s relevant to your org. Reducing noise and creating clarity for admins With the new My Trust Center, you’ll be able to get more specific information about upcoming maintenance and how it affects your org. Everything is tailored to what products and services you’re actually using, instead of having to sift through unrelated incidents and interpret whether or not they apply to you. As John explains, Salesforce can be much more granular about any specific maintenance or updates and how they will affect you. And that makes it easier to make decisions like when to promote new features, when you need to do testing, or when there might be downtime. You can coordinate better with your team and avoid surprises. Greater transparency through targeted communication At its core, My Trust Center is about improving transparency both internally and externally. For admins, it will provide more visibility into what’s going on when something doesn’t work and when a particular service will be back online. If there’s an incident, you won’t need to ask your CSM or contact customer support to figure out what happened. RCAs will be attached to each incident, so the entire process is self-serve. And you can configure notifications via SMS, Slack, or email to keep your entire team up to speed. Make sure to listen to the full episode for more from John about what’s coming with My Trust Center. And make sure you’re subscribed to the Salesforce Admins Podcast to catch us every Thursday. Podcast swag Learn more Salesforce Admins Blog Post: Admin Trailblazers Group Social Love our podcasts? Subscribe today or ! Full show transcript Mike Gerholdt: This week on the Salesforce Admins Podcast, I am joined by John Maxey to unpack the evolution of the Trust Center into something far more than a status page. That's right. It's becoming a personalized command center for how you run your org. I mean, let's be honest, it's not just about uptime anymore. It's about how you design systems that balance data, automation, and AI while keeping your stakeholders informed and confident. We're going to dig into what My Trust Center means for how you communicate incidences, plan releases, and operate with clarity across increasingly complex environments. So if you're the person everyone turns to when something breaks or when they just think something's broke, this episode's for you. Let's get John on the podcast. So John, welcome to the podcast. John Maxey: Thanks, Mike. Thanks for having me. Mike Gerholdt: Well, this is exciting. So I like it when I can have a podcast and a blog post on the same subject in the same day. And all of this stuff around trust and security, I feel like admins are right there, we're the Sentinels every day. But before we talk about some of the cool stuff that you're working on, let's learn a little bit about John Maxey. So John, how did you get to Salesforce and what is the cool thing that you oversee? John Maxey: Oh, well, thank you for that. So I came to Salesforce in late 2007. I joined as a customer support rep in CSG in our customer success group. I had just come from the FinTech, and if folks remembered, FinTech was kind of not doing well at that time in 2007. So it was an opportunity to switch industries and come to Salesforce. And that was pretty exciting being the ... At the time, our moniker was no software, sort of breaking the mold of traditional software and sort of moving to the cloud. Mike Gerholdt: Yeah. We were talking before I hit record. I think if you do the math, our Salesforce experience is definitely in high school at some point. John Maxey: Seems that way. Mike Gerholdt: They graduated from high school, which is kind of scary at some point. John Maxey: I wish. Mike Gerholdt: I know. Well, it's about to head off to college and make questionable decisions and maybe be a paleontology as a major. Who knows? But we're going to talk about ... So the blog post that went up today on admin.salesforce.com is the same topic as this podcast, which is My Trust Center, which I can't tell you how excited I am for this. Because I remember back to my days early admin, like '08, just going to having to pay. It never dawned on me until one of my users couldn't log into Salesforce a long, long, long, long time ago. And I was like, oh, I wonder why that is. But I never thought about like, oh, cloud services can go offline. I need to pay attention to this. And at the time, trust.salesforce.com was literally just like a handful of blinky lights. That's all it was because there was a handful of pods that you paid attention to and you just checked to see if yours was up and that was it. And then over the years, I mean, there's so much more to pay attention to. Everything that goes into trust.salesforce.com. So can you kind of take us on that journey of like Mike from 2008, just having to remember if NA1 is up to everything that the new My Trust Center is going to give us? John Maxey: Sure. Yeah. I remember using the Trust site when I first joined Salesforce as well way back in 2007, and it has changed a lot. So if you think about it, in 2007, Salesforce was really sort of selling one product, CRM, Salesforce automation. We had, like you say, we had just a handful of instances where we had customer installations. So even the field of boxes that we had there was small enough for folks to be able to find out what was going on with their stuff. And even in the URL of their application, it would say which instance you were on. So fast-forward 18 years and we've acquired companies, we've developed new technologies and new products. Some of them are on the platform and others are what we call off core or they're not directly in our application. They're separate different types of architecture. And then we've also moved into the public cloud. We've also been selling to enterprise customers and we think about an enterprise customer and their implementations are far more complicated, multi-cloud. So they may have marketing and commerce, as well as sales and service. And then we have all our industries. So in talking to customers when I became the product manager of the trust site in 2018, just sort of realized that their experience, especially for our larger customers was harder to deal with. When you look at, I mean, I think we have 950 some odd instances in our sales service industry, we have over a thousand DBs in marketing cloud engagement. It's just kind of daunting to try and figure out where you are. And so at the time we were figuring out tools to make it easier to find that. But really the answer was to get personal and to create an authenticated site. So then we know our customers. I believe that's like CRM 101, know your customer. And then when we know who they are, when you log in, we can present you with what you have with the things you already purchased, the products and services. So in this first release, we're starting that path, that journey to true personalization. And so there's still some gaps here and there, but one of them is the support for all our products. So we have requests out to all of our different products like MuleSoft and Tableau to do a little bit of work to get them ready for the My Trust Center. But yeah, so that's, I mean, it's just grown and this My Trust Center really just has come out of customer feedback and wanting a better experience. And the other thing about the personal, I know a lot of folks are going to probably jostle a little bit at the move away from a purely public site to the authenticated site. But there's an opportunity there to not only provide the personalization, but also be able to expand the types of services we can provide, product communications, things like that, that we may do via email today, but we can provide an experience to consolidate all that into one single spot, seeing as we will know who those customers are, being able to target the communications. As if we did it today and it was public, it would just be too much. It would be information overload. And so being able to segment that because we know who you are is really a powerful driver for that. Mike Gerholdt: Well, if you think about it, so I remember going to a user group, this'll totally date me. But they were like, "Well, you can subscribe to the RSS feed for your server status." And that was it for me. I was like, "Dude, I'm set. This is great. And I'm going to get the emails. It's perfect." And then you kind of don't know what you're missing until you don't know what you're missing. And there was rarely a case, but this also speaks to why My Trust Center makes so much more sense. If I were to go there, "Oh, my instance is down, but these three instances aren't." Well, it's not like I could do anything. It's not like if my lights are out in the neighborhood, but my neighbor's lights are on, I can grab my dog and I can put my slippers on and walk across the street and be like, "Hey, can we sit at your house until our lights come on?" It never dawned on me when I would go to trust.salesforce.com and see, "Oh, well, everyone else is online, just this one pod is off." Okay, cool. Next. Right? And that matters now because now if you think about it from what admins, developers, architects, they have so much to pay attention to. And all of a sudden, especially in a highly regulated industry, you talked about being in Finserv, why is this down? And you can feel that user looking over your shoulder and then you having to sift through a trust site, multi-layers, multi-things, and kind of give them an answer. This is, why can't you just present me with the dashboard that makes sense? I mean, the dashboard in my car only tells me about my car. It doesn't tell me about every other car on the road. So it kind of feels like a natural evolution. John Maxey: Yeah. And that was definitely part of it as well. The information overload as part of a growth and when you have a company that sells many more products than you started with. And then also we find that sometimes somebody will see an issue and then they go into the trust site and they see another issue going on and maybe they attach themselves to that. And so that can kind of confuse things when they reach out and report that. If there is an issue, we'll have ways to report that. But you shouldn't just assume that because somebody else is having an issue that it's the same issue that you're having. So yeah, definitely making sure that we're giving you the information. And then also being able to expand on it more. Like I mentioned, the public nature of that, we've got press watching it, we've got competitors and things like that. And sometimes we just don't want ... We don't have to be guarded with what we say because of how that could be used. When we know we're talking to customers, we can be a lot more open, even drafty as they might say. We know that something's going on. Maybe we don't know exactly what it is. And that's not really necessarily appropriate when you're speaking to a public audience. But when you're talking to customers and they just want to know that you know that there's a problem and that Salesforce is working on it. Like your analogy, when the power goes out, typically the customers don't need to know when the application is having an issue. They know that the application's that. They want to know that Salesforce knows that there's an issue and what are we doing to fix it? Mike Gerholdt: Yeah. I mean, ironically, it's just like the power company. John Maxey: It's just like the power company. Mike Gerholdt: So I'm looking at the screenshot and the other thing I noticed that I think is really neat that before back in the days of the blinky lights, it was like, it's on or it's off. Cool. And then we would pay attention to releases and you always got like a release date window. This shows a tab upcoming maintenance for the next 90 days. Tell me more about some of the thought that went into that. John Maxey: Yeah. So we look at the different personas that we want to support on the trust side, on My Trust, and we think about the jobs that they need to do. And so you have an admin. Admin is obviously concerned about any incidents going on to make sure they can communicate with their user base. But they're also working on developing new functionality for their user base. And so they want to know what's coming up, what would impact them. And in the past, it would have been as much of how much downtime would there be, but that's almost a thing of the past. But really it's more about when will my features? Maybe I've been working on those in Sandbox and I'm ready to promote them. When do I know to promote them? If we're talking about an operations persona, they need to know when there need to be a little more diligent because there's a release going on. Some of our customers do testing after we do a release to make sure that there's no conflicts or anything. Obviously as people customize their orgs, we do our best at Salesforce to make sure that there's no conflicts in the code that we release, but there's always, folks are very inventive in the way they do their solutions. And so there could be a conflict. A lot of customers like to test that, they want to know when. Especially if you have a large application, a lot of people in to test, you want to know the best use of their time because it's usually on a weekend. Mike Gerholdt: I know. Yeah. And I mean, even scrolling down, we could talk more about this too. I'm looking at a maintenance window of four hours. I remember before we would get a release as an admin, I'd always tell my users, every now and then that scheduled maintenance window would come up when you'd log in and be like, "Okay, well, just don't log in this weekend." And it's kind of like it's fun to think of the days when companies would only work Monday through Friday. Please salespeople just ... I know you're not working on Saturday, right? Wink, wink. John Maxey: Right. Well, a lot of the ... The major releases now, especially in Hyperforce are zero downtime. It's just really, it's more of a notification, "Hey, this is when your features would be ready," as opposed to it actually being downtime. The first party, it does have a little bit more. But I think we've got most customers off of first party now. And then we have some others that we're still working with to get their messaging better and because now we can target. So those timeframes, those windows will start to shrink because we'll be able to target folks at a better granularity and make sure they know exactly when they're going as opposed to a more generic sort of announcement, "Hey, we're doing a bunch of work. You may or may not be impacted in this time." We'll get it down to, we know when you're going to be deployed and exactly when the impact may happen. Mike Gerholdt: Yeah. And this is also going to help our inboxes because they're not full enough. John Maxey: I hope so. Mike Gerholdt: I know. Man, I'm telling you. The one line, say goodbye to instance wide email blast. Well, those were just fun. Okay, I think it ... Does it mean us or not? But still, one of the features is you can still subscribe to notifications, right? John Maxey: Yep, exactly. Yeah. Today we support email. We're looking to expand that in the near future to support SMS like we do in the legacy status site. And looking to add some more as well. I mean, obviously Slack is top on our list to investigate how to do that in a meaningful way so folks can subscribe to their notifications. Mike Gerholdt: Oh, like a Slack notification? John Maxey: Yeah, exactly. Like a Slack channel you subscribe to and get your notifications right in Slack. I mean, another one of our goals in our group in general is to try and push our information into the workplaces where folks are working. So if you spend your time in Slack, why not get that stuff in Slack? And then it's more meaningful and you don't have to switch to a different application. I mean, I love developing the trust site and the portal. But the main goal is to make sure folks are informed and get what they need. Mike Gerholdt: Well, so that was exactly ... I mean, to kind of ask you a best practices question, it could be, and in my case, I was the only admin, so it was easy for me to subscribe to everything. But there are a lot of companies that have teams, right? There's admins, developers. So putting it to Slack, obviously then it's anybody can join that Slack channel and get the status update. And if you need to know that, then join that channel, that makes sense. In the interim, how do you address that as a best practice for organizations with maybe multiple admins or multiple developers? John Maxey: Sure. That is a challenge. I mean, the quick and easy answer is we use Trailblazer ID, which is the same authentication method for Trailhead or for help, for AppExchange, all of our external facing portals. So there's a good, better experience there and one authentication through all those portals. But then because Trailblazer ID just takes an email address, you could use your group email to sign up for a Trailblazer ID. And then that ID, that email address, would have to be attached to a license in the orgs you want to see. So that's the way to do that. Today, we understand it's a challenge. Not everybody has a bunch of extra licenses to use for this type of purpose for folks who are monitoring. So we are working on a solution for a license that would have very limited or maybe no access to the org at all. But you could attach it to say a group email and then be able to get all the monitoring information you needed from that. Mike Gerholdt: I like that. John Maxey: Yeah. Mike Gerholdt: That's awesome. It says one of the plans is to have major release notes and root cause analysis for eligible incidents. How is that beneficial? Like what were customers asking for that we weren't providing root cause analysis on? John Maxey: As much of anything, it's a delivery mechanism. So if a customer is impacted by an issue, they may have to engage with their CSM or go to customer support and say, "I need an RCA." And so instead of that, we have certain criteria on incidents when an RCA is going to automatically be provided. So our first iteration would be that when that RCA is provided, we would attach it directly to the incident and you would get a notification that it's been attached. And so you could then go reference it. No need to ask anybody. In the future, we're thinking about ways maybe we could provide some visualization to say that it's in process and maybe how far in the process. I mean, the more we can self-serve, the better. And then we'll look at other ways of being able to surface that type of information and similar type of communications directly in the portal and through notifications and all of that. Mike Gerholdt: Before we press record, you said some customers already have their hands on it. What was some of the feedback they gave you? John Maxey: Oh, we were in Pilot for about a year with a handful of customers, and then we were in beta for ... Our open...
/episode/index/show/buttonclickadmin2/id/40698675