CertifyDeck
All cheat sheets
Platform Administrator · CHEAT SHEET

Salesforce Certified Platform Administrator

Key concepts grouped by official exam weight.

Download as PDF (free, no sign-up)

1. Configuration and Setup

15–15%

Configuration and Setup

  • The Company Information page holds the default locale, time zone and currency, the address, storage used and licenses; the fiscal year drives reporting and forecasting, and business hours and holidays decide when cases escalate. Multiple currencies cannot be disabled once activated, and Advanced Currency Management keeps dated exchange rates on opportunities.
  • Lightning apps are built in App Manager with branding, navigation items and profiles, and opened from the App Launcher. Global actions go on the global publisher layout and appear on every page; object-specific actions relate the new record to the current one. Lightning App Builder pages must be activated, and list views support charts and inline editing.
  • Usernames use email format and must be unique across Salesforce; users are never deleted, only deactivated (freeing the license and losing record access) or frozen. Each user has one user license plus optional permission set licenses, and profiles and permission sets cannot exceed them. Users set their own locale, and SSO uses a Federation ID unique within the org.
  • MFA is required from Identity Verification, and Session Settings assigns standard or high assurance levels used to restrict resources. Profile login hours and IP ranges block access, while Network Access trusted IPs only skip the verification code. Setup Audit Trail tracks admin changes, Health Check scores security, and employee agent access is granted through Agent Access.
  • Org-wide defaults set the access of the most restricted user; the role hierarchy, sharing rules (with public groups or roles and subordinates), teams and manual sharing only open access up. A detail object inherits its parent's sharing, and reports and dashboards inherit access from their folder, which is shared with roles or groups.

2. Object Manager and Lightning App Builder

15–15%

Object Manager and Lightning App Builder

  • Standard objects ship with Salesforce and custom objects hold business-specific data. A lookup links objects that can stand alone; in a master-detail relationship the detail inherits sharing and is deleted with its master, and a junction object with two master-detail fields creates a many-to-many relationship. Schema Builder shows and edits the model, and record types vary processes, layouts and picklist values.
  • Before deleting a field, remove it from layouts and permissions, mark it deprecated, wait for feedback and review dependencies, because it cannot be deleted while other metadata depends on it. For picklists, deactivating keeps the value on records, blank-replacing removes it and replacing a controlling value breaks the dependency. Page layouts control related lists and buttons; field-level security controls visibility.
  • Record types determine the business processes (sales, support), page layouts and picklist values available per profile. The page layout editor controls related lists, buttons and quick actions; Lightning App Builder controls components, Dynamic Forms, visibility rules and activation by app, record type, profile and device. Global actions live on the global publisher layout.

3. Sales and Marketing Applications

10–10%

Sales and Marketing Applications

  • Leads are unqualified prospects; converting one creates an account, a contact and, optionally, an opportunity. Opportunities move through stages that carry a probability and forecast category, and support contact roles, teams and splits. Path shows the stages of a process with key fields and guidance for success per record type, and Kanban lets users move records by dragging.
  • Einstein Lead Scoring scores leads from conversion history and Einstein Opportunity Scoring predicts which opportunities will be won; Account Engagement grading measures fit with the ideal customer. Collaborative Forecasts lets managers adjust without changing opportunities, Sales Territories assigns accounts by rules, and the Home page offers the Assistant and the performance chart.
  • Leads arrive manually, by import or through Web-to-Lead, and assignment rules route them by criteria to users or queues. Converting a lead creates an account, a contact and, optionally, an opportunity. Campaigns group marketing efforts: Parent Campaign rolls results up, and members (leads, contacts, accounts) use statuses marked as Responded.

4. Service and Support Applications

10–10%

Service and Support Applications

  • Cases arrive by phone, Email-to-Case or Web-to-Case, and Case Origin records the channel. Queues are shared lists (with Case as a selected object and users as members) that a team works from. Only one assignment rule can be active: its entries run in sort order, the first match assigns the case, and criteria can use account, contact or user fields.
  • Support processes limit Status values per record type; auto-response rules email the customer using the first matching entry, and escalation rules reassign and notify when a case passes a set age within business hours. Einstein Case Classification predicts fields from subject and description; Case Wrap-Up, Article and Reply Recommendations help reps during and at the end of service.

5. Productivity and Collaboration

10–10%

Productivity and Collaboration

  • Tasks and events appear in the record activity timeline, with an Upcoming & Overdue section and past activity by month; their compact layouts set the fields shown when an activity is expanded. Shared Activities relates several contacts to one task or event and can only be turned off by Support. The calendar supports object, public, resource and user list calendars.
  • Chatter groups can be public, private or unlisted, and any of them can be broadcast only; private groups can allow external customers, who see only the groups they are invited to. Unlisted groups must be enabled in Chatter Settings and are visible only to members. Feed tracking posts changes to selected fields in the record feed.
  • The Salesforce mobile app reads the org metadata and is tailored with quick actions, compact layouts and the navigation of Lightning apps enabled for desktop and phone. Lightning pages can be assigned to the phone form factor, and visibility rules can show components only on phones. Mobile Publisher creates a branded version of the app with its own store listing.
  • AgentExchange (formerly AppExchange) is Salesforce's marketplace for apps, agents, components, flow templates and actions, Bolt solutions and consultants. Managed packages hide their code, upgrade automatically and don't count against limits; unmanaged ones can be modified. Partners publish from the Partner Console after security review; always test in a sandbox before production.

6. Data and Analytics Management

17–17%

Data and Analytics Management

  • Data Import Wizard imports supported objects from Setup without automation; Data Loader is a client app for any object, scheduled command-line loads and Bulk API, whose hard delete bypasses the Recycle Bin. Validation rules apply during imports. Data Export Service makes weekly or monthly backups; archiving frees space while keeping access, and Backup & Recover restores specific values.
  • Matching rules identify potential duplicates (exact or fuzzy) and duplicate rules decide whether to block or allow with an alert and report. Validation rules stop a save when their formula returns TRUE, run after flows and triggers, are scoped with ISNEW, ISCHANGED or PRIORVALUE, and can be bypassed with a custom permission.
  • The report type sets the records and fields available; a custom report type joins a primary object with related ones, requiring related records or not, and its layout can add lookup fields. Bucket columns categorize without new fields, row-level formulas calculate per record and summary formulas per group. Joined reports place blocks side by side, and charts require groupings.
  • Report and dashboard folders decide who can access each report, not the data: each user sees only the records allowed by org-wide defaults, the role hierarchy and sharing rules. Folders are shared with roles, subordinates or public groups, and subfolders inherit that access. Field-level security hides a field in reports too, unlike page layouts.
  • Each dashboard widget (chart, gauge, metric, table) shows data from one source report, which cannot be a joined report. The running user sets the data every viewer sees; in a dynamic dashboard it is the logged-in user and it cannot live in a private folder. Dashboard filters change the data across widgets, and dashboards can be refreshed and emailed on a schedule.

7. Automation

15–15%

Automation

  • Assignment rules route new leads or cases to users or queues through ordered entries, escalation rules reassign and notify when a case stays open past a set time, and auto-response rules acknowledge the customer. Flow scheduled paths run as the Default Workflow User from Process Automation Settings, and Prompt Builder AI generates text rather than applying deterministic rules.
  • Screen flows collect user input and are distributed on Lightning pages, as actions or in the utility bar; autolaunched flows have no UI and are called by other flows, Apex or the API. In a record-triggered flow, Fast Field Updates runs before the save, Actions and Related Records after it, and Flow Trigger Explorer orders flows that share a trigger.
  • An approval process defines entry criteria, steps and who approves at each one: the manager through a hierarchy field, a user, a related user field or a queue, deciding on the first response or unanimously. Submission locks the record; final approval actions run only when no steps remain, and there are final rejection and recall actions too.

8. Agentforce

8–8%

Agentforce

  • Agentforce deploys autonomous agents built from topics, instructions and actions (flows, prompt templates or Apex) on the Einstein Trust Layer, with zero-data retention and toxicity detection. A good use case has clear rules and reliable data; important decisions stay with a person. Internal agents use the logged-in user's access, while service agents use their agent user's permissions.
  • In Agent Builder you test the agent in the Preview panel: Simulate validates the configuration without running actions or touching data, and Live Test runs real actions; the interaction summary shows subagents and reasoning. Committed versions can't be edited (you create a draft) and only one can be active. In Prompt Builder, you change an active template by saving a new version and activating it.