A Salesforce administrator is the person, internal or external, who looks after your Salesforce org. Day to day they keep it running, customise it as the business changes, and help people across the company actually use it. Without one, even a well-implemented Salesforce org gets messy fast.
Most of the time you only notice good admin work when it’s missing. Reports stop matching dashboards. New users wait three weeks for a profile. A field that used to be required gets quietly dropped, and nobody notices until the quarterly close goes wrong. By then it’s an expensive problem instead of a thirty-minute fix.
What admins are responsible for
The core remit covers users, data, security, analytics, and the product itself. In practice, that means:
- Maintaining the platform. Keeping it customised to current needs, automating the right pieces, keeping the security model intact as the org grows. Most of this is invisible when it’s done well.
- Helping users get value out of it, regardless of their technical level. Training, documentation, the daily “why doesn’t this report work?” support that platform success depends on. The admin is often the only person in the building who knows both the business and the system.
- Staying current on new tools, capabilities, and updates. Salesforce releases three times a year. Without somebody tracking those releases and adopting what’s relevant, an org drifts behind quickly. Two years of neglect and you’re paying for licences whose features you haven’t touched.
- Aligning Salesforce to company objectives as a product leader. The best admins do not just react to tickets. They identify where the platform should go next and bring the business along.
That last responsibility is what separates a good admin from a great one. A good admin builds what people ask for. A great admin builds what people will need in six months, before they have to ask, then explains why so the team can use it.
A typical admin week
To make this concrete, here is what a typical week looks like for an admin running a mid-sized Sales Cloud org:
- Reviewing inbound requests in Slack or Jira. Triaging which are real, which are misunderstandings, which are training opportunities, which need a developer.
- Running a release-readiness check on the latest sandbox before it gets deployed.
- Auditing user permissions for the new joiners that started Monday.
- Updating a flow that broke when the sales team changed how they qualify deals.
- Sitting with one of the regional sales managers for thirty minutes to understand why the forecast pivot is wrong, then realising the underlying record types are misaligned and writing the ticket to fix them properly rather than patching the report.
- Building the custom report the CFO needs by end of quarter.
- Doing a release sandbox test for the next Salesforce upgrade.
Notice how much of that is not technical work. It’s translation: between the business and the system, between what people asked for and what they actually need.
Internal admin or external?
Either works. The choice depends on org maturity and budget.
An internal admin makes sense when the platform is core to operations and the company has enough volume to justify a full-time hire. They build deep institutional knowledge, sit close to the business, and are available for the small daily requests that keep users productive.
An external admin or admin-as-a-service arrangement works when you want senior expertise without committing to a full-time role, when your org is in a transitional period (post-implementation, pre-scale), or when your internal admin needs occasional reinforcement on harder work.
Many of our clients run a hybrid model: internal admin for daily operations, external for strategic projects, complex automation, and the work where deep platform expertise pays for itself. That split is usually more cost-effective than either extreme, especially for companies in the 200 to 2,000 employee range.
How to recognise a good admin
Salesforce’s certification ladder is a useful but partial signal. The Salesforce Certified Administrator credential is the baseline. Beyond that, advanced certifications cover specific paths (App Builder, Architect, Consultant, Developer, Specialist), each with progressively narrower depth.
Certifications alone do not make a great admin. Look for someone who:
- Asks “why” before “how” when handed a request, because the right Salesforce solution often is not the one originally requested.
- Documents their work, in the org and outside it. A working org you cannot reason about is a liability waiting to happen.
- Treats data quality as a first-class concern. Bad data in Salesforce is worse than no data, because you’ll trust it.
- Knows when to use clicks and when to use code. The platform has been declarative-first for a decade, but there are still cases where Apex or LWC is the right answer. A good admin knows the difference and is not precious about either side.
- Has opinions, and is willing to push back. The admins we’ve worked with longest are the ones who say “I wouldn’t do it that way, here’s why” before they say “yes.”
Our team includes experienced administrators and consultants who provide implementation, managed services, integrations, and optimisation. The clients we work with longest tend to be the ones who treat the org like a product that gets better over time, not a ticket queue.