Study guide
2.4 Setup Navigation, Release Readiness, and Change Control
Salesforce Admin Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Platform Administrator Orientation and Official Source Control
1.1 Credential Name, Current Outline, and Search Language 1.2 Exam Format, Fee, Score, and Reference Rules 1.3 Trailhead, Trailhead Academy, and Pearson VUE Delivery Workflow 1.4 Domain Weights, Agentforce, and Study Prioritization 1.5 Maintenance Modules, Credential Ethics, and Exam Security 1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow
2 Chapter 2: Configuration, Setup, User Management, and Org Controls
2.1 Company Information, Fiscal Year, Business Hours, and Locale 2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access 2.3 Login Security, Session Settings, and Identity Basics 2.4 Setup Navigation, Release Readiness, and Change Control 2.5 UI Settings, Home Pages, Apps, and Navigation 2.6 Configuration and Setup Case Lab
3 Chapter 3: Security, Access, Identity, and Sharing Model
3.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams 3.2 Profiles, Permission Sets, Permission Set Groups, and Muting 3.3 Field-Level Security, Page Layouts, and Dynamic Forms 3.4 Record Access Troubleshooting and Login-As Workflow 3.5 Identity, Login History, MFA, and Session Risk 3.6 Data Visibility, Reporting, and Analytics Security 3.7 Security and Access Case Lab
4 Chapter 4: Object Manager, Lightning App Builder, and Data Modeling
4.1 Standard Objects, Custom Objects, and Schema Fit 4.2 Fields, Formulas, Rollups, Validation, and Requiredness 4.3 Lookup, Master-Detail, and Junction Relationships 4.4 Record Types, Business Processes, Page Layouts, and Lightning Pages 4.5 Dynamic Forms, Dynamic Actions, and User Experience 4.6 Schema Change Risk, Data Quality, and Deployment Readiness 4.7 Object Modeling Case Lab
5 Chapter 5: Sales, Marketing, Service, and Support Applications
5.1 Lead, Campaign, Account, Contact, and Opportunity Flow 5.2 Sales Processes, Path, Products, Price Books, and Forecasting 5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation 5.4 Knowledge, Entitlements, Service Console, and Support Productivity 5.5 Sales-Service Data Quality and Automation Boundaries 5.6 Application Configuration Troubleshooting 5.7 Sales and Service Applications Case Lab
6 Chapter 6: Data and Analytics Management
6.1 Data Import Wizard, Data Loader, Export, and Backup 6.2 Duplicate Management, Validation, and Data Quality Controls 6.3 Data Transfer, Ownership, Mass Update, and Mass Delete 6.4 Report Types, Filters, Summary Formulas, and Buckets 6.5 Dashboards, Components, Subscriptions, and Sharing Impact 6.6 Analytics Security, Visibility, and Executive Reporting 6.7 Data and Analytics Case Lab
7 Chapter 7: Automation, Flow, Approval, and Operational Processes
7.1 Automation Tool Selection and Order of Execution 7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows 7.3 Approval Processes, Email Alerts, and Notification Patterns 7.4 Validation Rules, Assignment Rules, and Escalation Rules 7.5 Automation Testing, Debugging, and Governance 7.6 Automation Performance, Recursion, and Maintainability 7.7 Automation Case Lab
8 Chapter 8: Productivity, Collaboration, Mobile, and AppExchange
8.1 Activities, Tasks, Events, Calendar, and Email Productivity 8.2 Chatter, Feeds, Groups, Notifications, and Collaboration Governance 8.3 Salesforce Mobile Navigation, Actions, and Page Design 8.4 List Views, Kanban, Path, and User Adoption Tools 8.5 AppExchange Evaluation, Installation, Permissions, and Risk 8.6 Productivity and Collaboration Case Lab
9 Chapter 9: Agentforce for Platform Administrators
9.1 Agentforce Use Cases, Admin Boundaries, and Fit 9.2 Trusted AI, Security, Data Access, and Permission Implications 9.3 Agent Builder, Prompt Builder, and Grounding Concepts 9.4 Testing, Deployment, Monitoring, and Feedback Workflows 9.5 Agentforce Service, Sales, and Internal Productivity Scenarios 9.6 Agentforce Risk, Troubleshooting, and Governance 9.7 Agentforce Case Lab
10 Chapter 10: Integrated Salesforce Admin Scenario Labs
10.1 New Sales Org Setup Integrated Lab 10.2 Service Team Case Management Integrated Lab 10.3 Data Quality and Analytics Integrated Lab 10.4 Security, Access, and Reporting Integrated Lab 10.5 Flow Automation and Change Control Integrated Lab 10.6 Agentforce and Adoption Integrated Lab 10.7 Full Admin Simulation Strategy
11 Chapter 11: Final Review, Maintenance, and Test-Day Strategy
11.1 Final 30-Day Salesforce Admin Review Plan 11.2 Trailhead Playground Hands-On Drill Plan 11.3 105-Minute Exam Timing, Flagging, and Review Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Maintenance Modules and Next Certifications 11.6 Salesforce Admin Final Mixed Review
2.4 Setup Navigation, Release Readiness, and Change Control
Key Takeaways Explain This Topic AI
Setup navigation is a skill: admins should know when to use Setup search, Object Manager, App Manager, Security, Company Settings, and release-related pages.
Salesforce releases require admins to review release notes, test enabled and upcoming changes, evaluate release updates, and communicate user impact.
Change control separates metadata changes from data changes and uses sandbox testing, deployment planning, Setup Audit Trail, and stakeholder signoff to reduce production risk.
The best answer in change scenarios is often to test, document, and deploy through a controlled path rather than editing production reactively.
Last updated: May 2026
Setup is an operating console
Setup is not a single menu to memorize from top to bottom. It is the operating console for configuration, security, metadata, identity, release readiness, and many admin diagnostics. Setup search helps locate pages quickly, but strong admins also know the major neighborhoods: Company Settings for org defaults, Users for user records, Security for authentication and session controls, Object Manager for object and field configuration, App Manager for Lightning apps and connected apps, and Flow for automation.
The exam often describes a symptom and expects the admin to choose the right Setup path. If the issue is object fields, record types, page layouts, compact layouts, or buttons, start in Object Manager. If the issue is app visibility, navigation items, utility bars, or app branding, start in App Manager. If the issue is login, password, sessions, or network trust, start in Security and Users. If the issue is org identity, fiscal year, business hours, or language defaults, start in Company Settings.
Setup navigation guide
Symptom First Setup area Why
A field is missing from a record page Object Manager and Lightning App Builder Field existence, field security, page layout, and Lightning page activation may all matter.
Users cannot access an app App Manager, profile, and permission sets App visibility and permissions are separate controls.
A user cannot log in from a location Login History, profile login IP ranges, Network Access Evidence should come before changing security policy.
Reports show the wrong quarter Company Settings > Fiscal Year Date filters depend on fiscal definitions.
A new release update may affect automation Release Updates, sandbox testing, Flow, affected metadata Release changes need validation before enforcement.
A production setting changed unexpectedly Setup Audit Trail Audit data helps identify what changed and when.
Release readiness is part of admin work because Salesforce is a multi-release platform. Admins should read release notes for features used by the org, review release updates, test in sandboxes or preview environments when available, and understand when changes become enforced. A release note is not a task list by itself. The admin must translate it into org impact: which profiles, apps, automations, reports, integrations, mobile users, and support processes could be affected.
Release Updates deserve special care because they can change platform behavior. Some updates can be enabled, tested, postponed within allowed windows, or enforced by Salesforce at a later date. The admin should not wait until the last day. Review the update description, identify affected metadata or users, test in a sandbox, fix dependencies, document decisions, and communicate timing. If an update affects security or automation, involve the owner of that process.
Change control means knowing the difference between metadata and data. Metadata is configuration such as custom objects, fields, page layouts, Lightning pages, flows, permission sets, profiles, apps, and validation rules. Data is business records such as accounts, contacts, cases, opportunities, products, and custom object records. A deployment tool may move metadata, but it does not automatically migrate production data records unless specifically designed to do so. This distinction prevents many failed deployments and user surprises.
For many admins, change sets are still a familiar deployment tool, especially between related Salesforce environments. Other teams may use DevOps Center, source control, Salesforce CLI, managed packages, or third-party release tools. The exam focus is usually not command syntax. It is the judgment that configuration should be built and tested outside production when risk is meaningful, dependencies should be included, validation should be planned, and users should know what is changing.
Setup Audit Trail is useful after a change, but it is not a substitute for change management. It can show many Setup changes and who made them, which helps investigate incidents and coordinate among admins. However, a mature process also uses requests, approvals, release notes, test evidence, and deployment records. In a shared admin team, two people editing the same automation or page in production without coordination is a preventable risk.
Hands-on practice should include a small end-to-end change. In a Developer Edition org, create a custom field on a test object, add it to a page layout or Lightning record page, assign field-level security appropriately, and document the Setup locations touched. Then imagine deploying it: what metadata must move, who must test it, which reports or automations might use it, and how would you confirm success after deployment? This turns Setup navigation into operational thinking.
Controlled change checklist
Define the business problem, success criteria, affected users, and owner.
Identify whether the change is metadata, data, security policy, release update, or a mix.
Build and test outside production when the change affects shared behavior or critical work.
Include dependencies such as fields, record types, flows, permission sets, apps, and Lightning pages.
Validate with representative users and realistic records.
Schedule the change, communicate impact, and monitor after deployment.
Use Setup Audit Trail and deployment records for traceability.
Scenario traps are predictable. Do not edit production because one executive is waiting unless the risk is truly low and authorized. Do not deploy a field without field-level security and page placement. Do not enable a release update without testing affected automation. Do not assume a sandbox contains current data or current permissions. Do not assume a successful deployment means users can use the feature; app access, profiles, permission sets, and page activation may still be required.