What Is a Salesforce Administrator? The Job, Skills and Exam

A Salesforce administrator, usually shortened to Salesforce admin, is the person who owns how a company's Salesforce org is set up. Salesforce calls the account an "org": the users, objects, fields, automation, reports and data that belong to one company. The admin changes all of that through Salesforce's point-and-click setup tools rather than code, and is the first person users go to when something in Salesforce doesn't work the way their team needs.

The title covers anyone from a sales operations manager who looks after Salesforce part-time to a team of full-time admins at a large company. The work underneath is the same set of jobs, described below.

What a Salesforce admin is responsible for

A Salesforce admin's work falls into a handful of areas, each with its own tools inside Salesforce Setup. Salesforce's admin exam, covered further down, is built around the same areas.

The other half of the job isn't in Setup at all. Salesforce's Admin Skills Kit lists 14 skills, and many are business ones. Communication, problem solving, business analysis, change management, product management and project management are among them, next to user management, security management, data management and process automation. In practice that means interviewing the sales team about what they need before building anything, and training them once it's built.

How access works, and why admins spend so much time on it

In Salesforce, each user has exactly one profile (their base set of access), and admins add permission sets on top to grant extra access. Salesforce's help page calls permission sets "the recommended way to manage your users' permissions" and advises building them around tasks rather than job titles, then bundling them into permission set groups that match a job function.

So instead of cloning the Sales profile five times to make small variations, an admin builds a permission set such as "Edit discount approval fields" and assigns it to the people who need it. When someone changes roles, the admin swaps permission sets instead of rebuilding a profile.

A change request, worked through

Say your head of sales wants reps to record which competitor is in each deal, and wants a weekly report of deals lost to each one. Here's how an admin would usually handle it:

1. Ask what the field is for. Agree the list of competitors, whether the field is required, and at which deal stage, so the report comes out clean.
2. Build it in a sandbox. A sandbox is a copy of the org that's isolated from production, so nothing the admin tries reaches users yet.
3. Add the field in Object Manager. A picklist on the Opportunity object, with the agreed values.
4. Put it on the right screen. Add the field to the opportunity page for the sales team, and make it required at the closing stages with a validation rule.
5. Check who can see it. Grant field access through the sales team's permission set, not by editing every profile.
6. Build the report. Closed-lost opportunities grouped by competitor, filtered to the last 7 days, saved to the sales leaders' folder and added to their dashboard.
7. Deploy and tell people. Move the change to production, then send reps a two-line note on what the field is and when it's required.

None of those steps needs code. The steps people skip are the first and the last, and they're usually the reason a new field ends up half-empty six months later.

Salesforce admin vs. Salesforce developer

A Salesforce admin configures the platform with Salesforce's built-in tools; a Salesforce developer writes code to do what configuration can't. Salesforce describes developers as people who "use code to create scalable solutions, integrate systems" and build custom apps.

The line is practical. A screen, a field, a report or an approval process is admin work. A complex integration with another system, or logic that Flow Builder can't express, goes to a developer.

Salesforce admin certifications

The main credential is the Salesforce Certified Platform Administrator, earned by passing one exam. Salesforce's own March 2025 overview still called it the Administrator certification, so you may meet both names. The exam guide sets out the current terms:

• Questions: 60 scored multiple-choice questions, plus up to five unscored ones.
• Time: 105 minutes.
• Passing score: 68% for the English exam (65% for Japanese).
• Fee: US$200 to register and US$100 to retake, plus applicable taxes.
• Prerequisites: none, though Salesforce recommends at least six months of hands-on experience as an admin.

The exam outline weights data and analytics management highest at 17%, then configuration and setup, Object Manager and Lightning App Builder, and automation at 15% each. Sales and marketing apps, service and support apps, and productivity and collaboration are 10% each, and Agentforce, Salesforce's AI agent product, is 8%. The credential page on Trailhead is where you register. The next step up is Salesforce Certified Platform Administrator II.

What changes under an admin every year

Salesforce ships three releases a year: Spring around February, Summer around June and Winter around October. Before each one, some sandboxes get the new release during a 4 to 6 week preview, which is the admin's window to test that nothing breaks.

Automation is the clearest recent example. Salesforce stopped supporting Workflow Rules and Process Builder on December 31, 2025. Existing automations still run, but Salesforce no longer gives customer support or bug fixes for them, and it asks admins to move them to Flow Builder with its Migrate to Flow tool. An org that still depends on old workflow rules is carrying automation nobody at Salesforce will fix.

Common mistakes admins make

• Building straight in production. A field or rule added mid-day is live for every user at once. Try it in a sandbox first.
• One profile per small exception. A dozen near-identical profiles become impossible to audit. Use task-based permission sets instead.
• Fields nobody asked for. Every extra field is one more thing reps skip. Add a field only when someone has a report or decision that needs it.
• Leaving old automation in place. Workflow Rules and Process Builder no longer get bug fixes; list what's still active and plan the move to Flow.