What Will a Salesforce Admin Actually Do in 2027?

Over the course of 2026, we’ve spent a lot of time trying to unpack and understand what is happening to the Salesforce Admin role. We’ve asked whether admins are being expected to do too much, whether they should learn code, whether they’re becoming architects by accident, and what AI actually means for their long-term prospects. At this point, there probably isn’t much value in asking the same question over and over again, which is “Will AI replace Salesforce Admins?”

In my opinion, the more useful question now is what the job will actually look like if it doesn’t. Salesforce is continuing to push further into AI, while admins are already being pulled into new areas like data, architecture, security, and so on. There won’t be one answer that applies to every admin, of course, but the direction of travel is slowly becoming clearer.

In 2027, the role may involve less time producing the first version of something and more time deciding what’s built, reviewing what AI has produced, understanding the wider impact, and making sure orgs remain something businesses can actually trust.

2026 Changed the Admin Role More Than We Realized

If 2026 has shown us anything, it’s that the Salesforce Admin role is very hard to define. For years, the job was relatively simple to explain from the outside – admins managed users, built reports, created fields, maintained automation, handled permissions, and generally kept Salesforce running. That work was by no means easy, but the boundaries of the role were clear enough.

Now, however, those boundaries have gotten lost a little bit. Our 2026 Salesforce Admin Survey found that 58.6% believe Salesforce is becoming increasingly complex to work with, while 53.1% said too much is now expected of Salesforce Admins.

That pressure is also applying to teams that often don’t have much additional technical support. 42.8% of respondents work in admin-only Salesforce teams, while 19.4% are working alone. AI has only made this change more obvious.

Vicki Moritz-Henry, a Salesforce Architect, Consultant, and Trainer, told SF Ben that admins are indeed using AI more, even if that doesn’t necessarily mean they have completely bought into the CRM giant’s agentic vision just yet.

“At the entry level, admins are using AI for the everyday stuff: writing formulas, troubleshooting validation rules, figuring out why a flow isn’t firing,” Vicki explained. “It’s taken on a lot of the work the community used to do for each other.”

At the other end of the spectrum, she is seeing a much smaller group of advanced admins go considerably further. Vicki said: “At the advanced end, some admins are connecting Claude or similar tools to Salesforce via MCP and using them to do configuration work directly in the org. That’s a real shift, but far fewer admins are operating at that level.”

This explains why things for admins feel so unsettled at the moment. AI can make familiar admin tasks quicker, but the further it moves into the org, the more questions it creates around security, trust, and oversight. 

As Vicki put it: “The gap between those two groups isn’t really about skill. It comes down to three things: comfort with setting up the integration, confidence about the security implications of giving an AI tool access to the org, and trust that the AI is actually doing the right thing once it’s in there.”

And despite some productivity gains, there are signs that admins are reconsidering where they really fit in the modern Salesforce landscape. Some 60.3% of survey respondents said they would consider moving into a non-admin role within the next two years.

That doesn’t necessarily mean the admin role is disappearing, but it may mean that the work has expanded so far that people are starting to find other titles for what they already do.

What Will Salesforce Admins Actually Spend Their Time Doing in 2027?

If the admin role has already widened this much, the next question is what starts to take up less time. For Salesforce Consultant and former accidental architect Jeremy Carmona, some of the clearest candidates are the first drafts of work that used to keep admins busy in setup – formula fields, validation rules, simple Flows, reports, field descriptions, and release notes. AI can already produce a passable starting point for much of that work in seconds.

What matters more, he told SF Ben, is everything around the build. “My prediction for 2027,” he stated, “[is that] admins spend less time in Setup and more time in the conversation that happens before anyone opens Setup.”

This lines up with what Senior Salesforce CRM Strategist Leanne Botwright has seen in her move from Salesforce administration into a Technical Business Analyst role.

In her view, knowing how to build something is only part of the job, and understanding what needs to change, why, and what the consequences might be is becoming just as vital. This then means more time spent on discovery, process mapping, stakeholder conversations, and challenging requests before anything is built.

She told SF Ben: “If building becomes easier, that discovery work becomes even more important, because we can also build the wrong thing faster.”

The same then applies after something has been built too. AI may reduce the time needed to produce a Flow or a piece of code, but someone still needs to understand what it does and if it’s safe to deploy.

Jeremy summed this up quite nicely, stating: “AI made building cheap and left comprehension at full price.”

So really, what technical ability looks like for admin could be reshaping itself. It may become less about writing everything yourself and more about understanding enough to review it properly. Jeremy pointed to areas like order of execution, sharing and permissions, Flow fault paths, Apex at a reading level, and how agents and prompt templates affect business outcomes.

“If you can’t read it, you can’t approve it,” Jeremy detailed. “An admin who can’t approve changes isn’t administering the org. They’re hosting it.”

This doesn’t mean that every admin suddenly needs to become a hands-on developer. Almost 70% of survey respondents work mainly or entirely with declarative tools. But it does suggest that the admins of 2027 may spend more time reviewing, governing, and making decisions around what gets built, rather than doing every piece of the building themselves. 

Expectations Are Rising. Can the Role Keep Up?

While we may be quick to question whether admins can adapt, it’s also worth questioning whether the way companies value the role adapts too.

Our Admin Survey suggests that plenty of Salesforce professionals already feel the boundaries have stretched too far. When asked which responsibilities should sit elsewhere, 44.2% pointed to business analysis, 40.4% to project management, and 37.3% to user training and documentation. Yet when respondents were asked which role their team would hire first if budget allowed, the most common answer was a developer. 

If this is happening at scale, then it certainly feels off. Admins are constantly being encouraged to understand more code, AI, security, and DevOps, but many are still working in teams without the specialists who would usually own some of that work.

SF Ben Technical Content Writer Christine Marshall raised exactly that concern when we discussed whether Salesforce Admins should learn code earlier this year. She said: “My fear is that if admins learn to code, people will continue to employ admins on the same wage, but with a higher expectation of them doing coding and taking on a lot more development responsibility.”

That concern is particularly relevant when you look at some of the current Salesforce job listings. One Senior Salesforce Admin role, for example, asks for a mix of Administrator, Platform Developer, OmniStudio, Industries CPQ, Marketing Cloud, and Sales Cloud certifications, alongside skills covering Lightning Web Components, SQL, integrations, automation, and DevOps.

One job advert obviously doesn’t represent the entire market, but it does raise a fair question. At what point does a Salesforce Admin job become several Salesforce roles bundled under one title?

We have already seen something similar with the rise of the “accidental architect”. Admins can find themselves making decisions around solution design, governance, data models, integrations, and security without necessarily having the architect title, authority, or support that normally comes with that responsibility.

In fact, we’ve actually reached a point where some are questioning whether the Salesforce Admin title should exist at all. In a recent article titled “It’s Time to Retire the Salesforce Admin Title”, Salesforce veteran Bill Greenhaw argued the role has evolved so much that the title no longer accurately reflects what many admins actually do. 

After analyzing 118 Salesforce Admin job postings, he found that 54% included responsibilities related to architecture, product ownership, or coding, even when business analysis was excluded.

His argument raises some interesting concerns, particularly around hiring and career progression. Admins who spend years taking ownership of integrations, solution design, and platform strategy may find themselves overlooked for more senior positions simply because their job title doesn’t reflect their experience. 

Employers, meanwhile, risk advertising very different jobs under the same title. Whether retiring the title altogether is the answer is another question, but Greenhaw makes some compelling points, and his article is well worth reading as we head into 2027.