The Salesforce Certified Administrator is the entry credential of the Salesforce ecosystem, and it tests one core capability: can you configure and maintain a Salesforce org with clicks, not code? That covers managing users and a security model, customising objects and pages, automating processes, managing data and reports, and now configuring AI through a dedicated Agentforce domain. The exam is practical in spirit; the questions describe administrative situations and ask what a competent admin would do. This guide is a full, self-study course. It walks through all eight domains in the proportion the exam tests them, teaches the security model and Flow automation in depth because they are the conceptual core, and then turns everything into a study plan and an exam-day routine. It is original teaching material and study guidance only. It contains no real or simulated exam questions, and you should confirm the current domains, weights, and passing score on the official Salesforce Certified Administrator exam guide before you book, because Salesforce updates this credential regularly.
Chapter 1: Exam overview and how to use this guide
What the exam measures, and the eight domains
The Administrator exam measures whether you can run a Salesforce org day to day using declarative tools. Salesforce organises it into eight domains with official weightings, and those weightings are the most important planning fact in this guide. They are: Configuration and Setup (15%), Object Manager and Lightning App Builder (15%), Sales and Marketing Applications (10%), Service and Support Applications (10%), Productivity and Collaboration (10%), Data and Analytics Management (17%), Automation (15%), and Agentforce (8%). The single largest domain is Data and Analytics at 17%, and three domains, Configuration and Setup, Object Manager, and Automation, sit at 15% each, so the bulk of the exam concerns security and setup, building the data model, working with data and reports, and automating with Flow.
A renaming and a new domain you must know about
Two changes from the 15 December 2025 update matter before you study. First, Salesforce renamed the credential the Salesforce Certified Platform Administrator; it is the same certification and the same exam code (Plat-Admn-201), and older material may still call it simply the Administrator. Second, the update added the Agentforce (AI) domain at 8% and reduced the Configuration and Setup weighting to make room. The practical consequence is that older seven-domain study material with no Agentforce domain is out of date, and some legacy guides showing, for example, Configuration and Setup at 20% reflect the previous version. Use current eight-domain material, and treat Agentforce as a genuine part of the exam rather than an optional extra.
Format and how certifications stay current
The exam runs 105 minutes and contains 60 scored questions plus 5 unscored questions (65 in total), in multiple-choice and multiple-select formats, proctored through Pearson VUE at a test centre or online. The passing score is around 65% (published figures vary between roughly 65% and 68%, so confirm it on the official exam guide when you book). Unusually, Salesforce certifications have no fixed expiry date; you keep this one active by completing the free Trailhead maintenance modules Salesforce releases with its updates. Miss the maintenance window and the credential can become inactive, so watch your Trailhead dashboard for deadlines.
How to use this course, and the one habit that matters most
Read the chapters in order; the security model in Chapter 2 underpins much of what follows, and the data model in Chapter 3 is assumed by the automation and data chapters. The bold terms are your checklist. The single most valuable study habit for this exam is to work in a free Developer Edition org and do everything hands-on: create a user and grant access, build a custom object, write a validation rule, build a flow, import data, and build a report. Reading about these is no substitute for doing them, especially for the heavier Data and Automation domains. A short worked example appears where something is easy to confuse, but none of these are exam questions. They are teaching illustrations.
Chapter 2: Configuration, setup, and the security model (15%)
This domain covers company-wide settings and user management, but its conceptual heart, and the most-tested area in the whole exam, is the security model. Getting it straight resolves a large share of questions.
Company settings and users
At the simplest level, an admin configures org-wide settings such as the fiscal year, business hours, and currencies, and manages users: creating them, deactivating them, and controlling login access. These are foundational and largely mechanical, but they set the stage for the security model, because every access question is ultimately about what a user can see and do.
Profiles versus permission sets
Access in Salesforce is layered, and the first distinction the exam tests is profiles versus permission sets. A profile is a user’s baseline set of permissions and access, and a user has exactly one. A permission set grants extra access on top of a profile and can be assigned to many users. The modern best practice, which the exam favours, is to keep profiles lean and grant additional capabilities through permission sets, because that scales: rather than cloning a profile every time one person needs one extra permission, you assign a permission set. As a teaching example: if most of a team shares a profile but three of them also need to export reports, you grant those three a permission set rather than building a whole new profile. Profile equals baseline (one per user); permission set equals additive (many users).
Object access versus record access
The deepest idea in this domain is that Salesforce security works at two distinct levels, and confusing them is the classic error. Object- and field-level security (set through profiles and permission sets) controls what kinds of data a user can access at all, can they see the Account object, can they edit the Phone field. Record-level security controls which specific records of an object a user can see, this account but not that one. You configure record access with three tools. Organisation-wide defaults (OWD) set the baseline visibility per object, Private, Public Read Only, or Public Read/Write, and best practice is to start restrictive (Private) and then open access deliberately. The role hierarchy opens records upward, so managers can see their subordinates’ records. Sharing rules open records sideways, to groups beyond the hierarchy. The mental model the exam rewards: OWD locks the doors, the role hierarchy opens them upward, and sharing rules open them sideways. As a teaching example: if OWD on Opportunities is Private and a salesperson cannot see a colleague’s deal, that is by design; to let one team see another team’s deals, you add a sharing rule, not a change to the hierarchy.
Chapter 3: Object Manager and the Lightning App Builder (15%)
This domain is about shaping the data structure and the interface that sits on top of it. It is where you turn Salesforce from a generic CRM into something fitted to a business.
Objects, fields, and relationships
The data structure is built from objects (tables of records), fields (columns on those objects), and relationships (the links between objects). Standard objects such as Account, Contact, and Opportunity ship with Salesforce; custom objects you create for data specific to the business. The exam expects you to know the common field types and to understand relationships at an admin level, particularly the difference between a lookup (a loose link where the child can exist without the parent) and a master-detail (a tight parent-child link with ownership, cascade delete, and the ability to roll up summary values to the parent). That lookup-versus-master-detail distinction recurs across Salesforce exams, so anchor it: only master-detail gives cascade delete and roll-up summaries.
Record types and page layouts
Two customisation tools shape how a single object behaves for different users. A record type lets one object support different business processes, offering different picklist values and a different process to, say, two sales teams using the same Opportunity object. A page layout controls the arrangement of fields, related lists, and buttons a user sees on a record. The exam wants you to grasp that record types plus page layouts let you tailor one object to multiple use cases without creating separate objects, which is a core admin technique.
The Lightning App Builder
The Lightning App Builder is the drag-and-drop tool for building app pages, home pages, and record pages from components, without code. The exam expects familiarity with assembling a Lightning record page and an app, and with the idea that the interface, like the data model, is configured declaratively. Build one yourself in a Developer Edition org so the components and the page types are concrete rather than abstract.
Chapter 4: The application domains - Sales, Service, and Productivity (10% each)
Three domains cover the standard Salesforce applications an admin supports. Each is 10%, so together they are 30% of the exam, but they are largely about knowing the standard features and the lifecycles they support rather than deep configuration.
Sales and Marketing Applications
This domain covers the sales process and the objects behind it. The key flow is from lead (an unqualified potential customer) through lead conversion, which turns a qualified lead into an account, contact, and opportunity. An opportunity is a potential sale tracked through stages of the sales process. The domain also covers products and price books (what you sell and at what prices), forecasting basics, and campaigns for marketing. The exam wants you to understand the lead-to-opportunity flow and what each object is for, since that is the backbone of how Salesforce supports selling.
Service and Support Applications
This domain mirrors the sales side but for customer support. The central object is the case, a customer issue tracked through its lifecycle to resolution. Supporting features include queues (holding locations that route cases to the right team), and the automation rules that move cases along: assignment rules (who gets a case), escalation rules (raising a case that has waited too long), and auto-response rules (automatic replies). The domain also covers Knowledge (a library of help articles) and support productivity tools. Understand the case lifecycle and what each routing rule does, because that is what these questions probe.
Productivity and Collaboration
This domain covers the everyday tools that help users get work done: activities (tasks and events), the Salesforce mobile app, Chatter (internal collaboration), email integration, and templates. It is the lightest domain conceptually; the exam wants awareness of what these features are and when an admin would enable or configure them, rather than deep setup detail.
Chapter 5: Data and Analytics Management (17%)
This is the largest single domain, so it deserves real attention and plenty of hands-on practice. It splits cleanly into managing data and reporting on it.
Getting data in and keeping it clean
An admin regularly imports, exports, updates, and de-duplicates data, and the exam tests the right tool for the job. The two import tools are the Data Import Wizard, which is built into the interface, handles the common standard objects (and custom objects) up to a row limit, and includes matching to prevent duplicates; and the Data Loader, a separate client application for large volumes and all objects, including inserts, updates, and deletes. The rule of thumb the exam rewards: Data Import Wizard for smaller, simpler imports of common objects; Data Loader for large volumes or objects the Wizard does not support. Data quality is supported by duplicate and matching rules, which detect and block duplicate records, and by sensible backup practices. As a teaching example: importing fifty thousand records across several objects is a Data Loader job, while adding two hundred leads with duplicate-checking is a Data Import Wizard job.
Reports, report types, and dashboards
Analytics rests on three concepts. A report returns a set of records meeting criteria. A report type is the template that decides which objects and fields a report can use, and understanding it is key, because if a field is missing from a report, the cause is usually the report type. A dashboard is a visual summary built from one or more reports. The exam expects you to know how report types constrain what you can report on, the common report formats, and how dashboards visualise report data. Because this domain is the largest, build several reports and a dashboard yourself, and deliberately hit the moment where a field is unavailable because of the report type, so the concept sticks.
Chapter 6: Automation with Flow (15%)
Automation is 15% of the exam and one of its two conceptual cores. The crucial modern fact is that Salesforce has consolidated declarative automation onto Flow, and is retiring the older Workflow Rules and Process Builder, so this domain is overwhelmingly about Flow.
Flow and its types
Flow, built in Flow Builder, is Salesforce’s single declarative automation tool, and the exam expects you to recognise the main types and when each fits. A screen flow guides a user through input screens, used when a person needs to interact, for example a guided form. A record-triggered flow runs automatically when a record is created, updated, or deleted, used for behind-the-scenes automation such as updating related records or sending a notification. A scheduled flow runs on a set schedule, used for recurring batch work. The judgement the exam tests most is matching the flow type to the requirement: if a user must enter data through screens, that is a screen flow; if something should happen automatically when a record changes, that is a record-triggered flow.
Validation rules and approval processes
Two further automation tools round out the domain. A validation rule enforces data quality by blocking a save when data fails a condition, for example requiring a close date whenever an opportunity reaches a certain stage. An approval process routes a record to people for approval or rejection, automating sign-off such as a discount that needs a manager’s agreement. The exam wants you to know what each does and to pick the right tool: validation rules guard data at the point of entry, approval processes route human decisions, and Flow handles broader automated logic.
Choosing the right tool, and what is retired
Because Salesforce now centres declarative automation on Flow, a recurring exam theme is choosing the right tool for a requirement within the current toolset, and knowing that Workflow Rules and Process Builder are being phased out. The practical study guidance is to learn Flow thoroughly rather than the retired tools, build a record-triggered flow and a screen flow yourself, and be able to say, for a given requirement, whether the answer is a validation rule, an approval process, or a flow, and which flow type.
Chapter 7: Agentforce, the new AI domain (8%)
Added in December 2025, this is the newest and smallest domain, but it is genuinely on the exam and should not be skipped. It introduces AI from an administrator’s point of view.
What Agentforce and Einstein are
Agentforce is Salesforce’s AI agent layer that administrators set up and govern, and Einstein refers to Salesforce’s built-in AI features for predictions and assistance. The exam’s framing is administrative: not how to build AI, but how an admin describes the capabilities and use cases of these features and decides when it is appropriate to use AI in an org. You should be able to explain, at a high level, what an AI agent can help with and recognise scenarios where AI assistance fits.
Trust, data access, and guardrails
The part the exam emphasises is governance: the trust, data-access, and guardrail considerations that come with AI. An admin must think about what data an AI feature can access, who is permitted to use it, and how to keep its behaviour within safe bounds, which ties directly back to the security model from Chapter 2. The domain also touches lightly on maintaining and configuring prompts or instructions and on troubleshooting agent permissions. The teaching point is that, for an administrator, AI is as much about control and trust as about capability: enabling helpful AI while governing its data access responsibly is exactly the judgement these questions test.
Chapter 8: Study plan, final preparation, and exam day
With the eight domains understood, the remaining work is pacing your study so the heavy and conceptual domains get the time they need, and confirming you are working from current material.
A six-week plan, weighted to the core
A realistic plan for someone with some Salesforce exposure runs about six weeks at roughly eight hours a week, with a free Developer Edition org open throughout. A sensible shape is: week one on company setup, users, profiles, and permission sets; week two on the security model (OWD, role hierarchy, sharing rules) until you can explain why one user sees a record and another does not; week three on objects, fields, relationships, record types, and page layouts; week four on automation with Flow, validation rules, and approval processes; week five on data and analytics (the largest domain), the Sales and Service apps, and Agentforce; and week six on free Trailhead practice and full-length timed reviews. If you are new to Salesforce, extend this to eight to twelve weeks. The security model (weeks one to two) and Flow (week four) are the conceptual core and deserve the most time, while Data and Analytics, the largest domain, needs enough hands-on repetition to become mechanical. To turn this into dated study days for your own start date, use the free study-plan generator.
Practise hands-on, and use current material
The most effective preparation is doing the work in a Developer Edition org: build users, the security model, objects, flows, and reports yourself, because that is what makes the heavier domains stick and what the scenario questions reward. Use the free Trailhead trailmix and the official exam guide as your scope, and make sure your material is the current eight-domain version that includes Agentforce, since older seven-domain content is out of date. Avoid any site claiming to sell the actual questions; it breaches Salesforce policy and will not teach you the platform. When you are ready to plan a next step, the Salesforce Platform App Builder credential builds on these same declarative skills toward custom app design.
Exam day and keeping the credential active
On the day, the exam is 60 scored questions plus 5 unscored (65 total) in 105 minutes, in multiple-choice and multiple-select formats, proctored through Pearson VUE at a test centre or online. You need around 65% to pass, so confirm the exact figure on the official exam guide when you book. Read each scenario for what it is really asking, often which security tool, which flow type, or which data tool fits the situation, and choose the option that reflects current Salesforce best practice (lean profiles plus permission sets, restrictive OWD opened deliberately, Flow over the retired tools). After you pass, remember there is no fixed expiry, but the credential stays active only if you complete the free Trailhead maintenance modules each release; diarise those deadlines so the certification does not lapse, and confirm the current format and passing score on the official guide before you sit, since Salesforce updates this credential regularly.