Salesforce Certified Platform Administrator Roadmap

Separate organization settings, user entitlement, object capability, field access, and record visibility.

• Review company information, locale, currency, fiscal year, business hours, session settings, identity verification, login hours, and Setup Audit Trail.
• Understand usernames, locales, user licenses, feature licenses, activation, freeze, deactivation, and why users are not deleted.
• Keep profiles as a baseline; add capabilities with permission sets and permission set groups, using muting where appropriate.
• Start record sharing with organization-wide defaults, then open access through role hierarchy, sharing rules, teams, queues, public groups, and manual sharing according to the requirement.
• Test object, field, and record access separately with realistic personas. A hidden component is not a security control.

Translate business processes into maintainable data and user experiences.

• Model standard and custom objects with lookup, master-detail, and junction relationships; understand ownership, cascade, reparenting, and roll-up implications.
• Create fields, formulas, dependent picklists, record types, sales and support processes, page layouts, quick actions, and Lightning pages with component visibility.
• Use Path to guide stages without confusing guidance with enforcement.
• Practice lead assignment, conversion, campaigns and campaign members, opportunities, forecasting, and supported sales productivity features.
• Practice case queues, assignment, auto-response, escalation, business hours, support processes, and supported Einstein for Service capabilities.
• Configure tasks, events, Chatter groups, Lightning apps, mobile navigation, and a governed AppExchange evaluation process.

Make mass changes reversible and analytics faithful to sharing.

• Choose Data Import Wizard or Data Loader based on objects, volume, operation, automation, and required error handling.
• Use stable external IDs for repeatable upsert and reconcile every source row to success or rejection.
• Combine matching rules and duplicate rules; use validation rules to block semantically invalid saves with actionable messages.
• Back up and rehearse imports, updates, transfers, mass deletes, exports, and recovery in a non-production environment.
• Create standard and custom report types with correct with-or-without relationships.
• Distinguish row-level and summary formulas, joined reports, buckets, grouping, charts, filters, subscriptions, dashboard running user, and dynamic dashboards.
• Test reports as each persona because sharing determines which records enter results.

Select automation by trigger, interaction, data change, and authority.

• Use before-save record-triggered flows for efficient updates to the triggering record.
• Use after-save flows for related records and downstream actions, with precise entry conditions and change detection.
• Use screen flows for guided interaction, autolaunched flows for reusable logic, and schedule-triggered flows for time-based record evaluation.
• Add fault paths, diagnostics, bulk-safe data operations, and idempotency.
• Understand order of execution and test interactions among validations, flows, assignment rules, and other automation.
• Use approval processes for explicit human submission, approver selection, record locking, rejection, recall, and final actions.
• Run negative tests for missing permissions, recursion, bulk input, failures, and rollback.

Administer bounded AI capability without weakening platform controls.

• Select Agentforce for a clear conversational task grounded in approved data, not as a replacement for deterministic controls or authorization.
• Define topics, instructions, knowledge, actions, uncertainty, escalation, and prohibited behavior.
• Validate effective user, object, field, record, flow, action, and agent permissions.
• Use conversation preview and representative tests for normal, ambiguous, unsupported, adversarial, and denied cases.
• Review third-party agent templates for publisher trust, permissions, data use, prompts, actions, dependencies, licensing, and uninstall behavior.
• Recheck the live guide because the current public document still says Summer '25 while the platform evolves through rolling releases.
• Complete the required Platform Administrator maintenance badge annually and verify the live due date.
• Finish all three projects, review 40 cards, and answer the bank by its exact 8/7/5/5/5/9/7/4 allocation.