Study guide
2.5 UI Settings, Home Pages, Apps, and Navigation
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.5 UI Settings, Home Pages, Apps, and Navigation
Key Takeaways Explain This Topic AI
Lightning apps, navigation items, home pages, record pages, utility bars, themes, and UI settings shape user workflow but do not replace object, field, or record permissions.
Lightning App Builder activation matters because a page can be assigned by app, record type, profile, or org default depending on the page type and activation choices.
App Manager controls app-level experience such as app visibility, navigation, branding, app options, and utility bars, while Object Manager controls object-specific configuration.
A clean admin design starts from user jobs and frequent tasks, then aligns navigation, home page content, record pages, and permissions around those tasks.
Last updated: May 2026
The UI is workflow, not security by itself
Salesforce admins configure the user experience so people can get to the right work quickly. Lightning apps, navigation items, home pages, record pages, compact layouts, actions, utility bars, themes, and UI settings all influence how the platform feels. They do not, by themselves, grant secure access to data. A user might have an object tab in navigation but no permission to read the object. Another user might have object permission but not see the tab because the app navigation does not include it.
The core Setup split is App Manager versus Object Manager. App Manager is where admins create and edit Lightning apps, choose navigation style, select navigation items, configure branding, assign user access to the app, and add utility bar items where appropriate. Object Manager is where admins configure object fields, page layouts, record types, buttons, links, actions, compact layouts, search layouts, and other object-specific behavior. Lightning App Builder sits across the experience layer by designing home pages, app pages, and record pages.
UI configuration map
Need Setup area What to verify
Change tabs in a Lightning app App Manager Navigation items, app type, app visibility, and user access.
Design a record page Lightning App Builder Activation by app, record type, profile, or default where available.
Add a field to an object layout Object Manager Field existence, field-level security, page layout, and Lightning page components.
Change highlights panel fields Object Manager compact layouts Compact layout assignment and record page usage.
Add quick productivity tools App Manager utility bar App context and user permission for the underlying feature.
Change org-wide UI behavior Setup UI settings and related pages Impact on all users or broad groups.
Home pages are useful when they help a user start work, not when they become decorative bulletin boards. Sales users may need tasks, recent opportunities, dashboards, assistant components, or pipeline views. Service users may need case queues, today's work, knowledge access, and performance dashboards. Executives may need high-level dashboards and approvals. The admin should design from role-based workflows and then activate the page for the right app and user audience.
Lightning record pages introduce a common scenario trap. A field may be on the page layout, but a Lightning record page may use components, dynamic visibility, tabs, or related record components that affect whether the user sees it. Dynamic Forms, where available, can move fields and sections onto the Lightning page and apply visibility rules. Field-level security still applies. If a user cannot see a field, check field-level security before assuming the page is wrong.
App navigation should be intentionally narrow. A sales app should foreground leads, accounts, contacts, opportunities, tasks, dashboards, and other sales workflow items. A support app should foreground cases, contacts, accounts, knowledge, reports, queues, and service tools. Adding every object to every app creates noise and increases training cost. Removing a navigation item does not secure the object; it only removes a path. Security must still be handled through permissions and sharing.
Utility bars are powerful in console and productivity apps because they keep tools close at hand, such as notes, history, softphone, macros, or custom components. The trap is adding a utility without confirming that the target users have access to the underlying feature and that it supports their workflow. A utility bar should reduce clicks for a repeated task. It should not become a drawer of unrelated tools.
Themes and branding can help users distinguish apps and environments, but branding is not a replacement for training or access control. A production app and a sandbox may look similar unless the team intentionally labels and communicates them. Admins should avoid making environment recognition depend only on memory. In practice, clear app names, appropriate branding, login messaging where used, and release communication all help reduce mistakes.
Agentforce-related UI features should be introduced with the same discipline. If an assistant, agent action, or AI panel appears in a user workflow, the admin should understand the use case, permissions, grounding data, testing process, and monitoring expectations. Do not add AI entry points only because they are available. Add them when they serve a clear task, respect data access boundaries, and have an owner who will review outcomes.
UI troubleshooting checklist
Can the user access the app at all through profile, permission set, or app assignment.
Is the object included in app navigation, and does the user have object read permission.
Is the record visible through ownership, role hierarchy, sharing, team, queue, or manual share.
Is the field visible through field-level security and included on the relevant layout or Lightning page.
Is the correct Lightning page activated for the app, record type, and profile combination.
Are component visibility filters hiding content based on field values, device, or user attributes.
Does the user have access to utility bar features, dashboards, reports, or embedded components.
A good hands-on lab is to build two Lightning apps in a practice org: Sales Workspace and Support Workspace. Give them different navigation items and home pages. Put the same object in one app but not the other, then test what changes for a user who still has object permission. Next, remove object permission and observe that navigation alone cannot create access. This exercise makes the exam distinction concrete.
The strongest admin answers balance usability and control. If users cannot find a tab, check app navigation. If users find the tab but cannot open records, check object and record access. If the record opens but the page looks wrong, check page activation, record type, profile, and component visibility. If users ask for a custom app, ask which jobs the app should make faster before copying an existing app and adding more tabs.