Study guide

8.3 Salesforce Mobile Navigation, Actions, and Page Design

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

8.3 Salesforce Mobile Navigation, Actions, and Page Design

Key Takeaways Explain This Topic AI

Mobile administration starts with the tasks users must complete away from a desk, not with copying the desktop page onto a phone.

Navigation items, compact layouts, actions, Lightning pages, and dynamic visibility determine whether mobile users can work efficiently.

Mobile support requires testing with real user profiles, record access, device constraints, network conditions, and form-factor behavior.

Security decisions for mobile include login policy, session behavior, device posture, data exposure, and whether a mobile use case is appropriate.

Last updated: May 2026

Design for the mobile job

A mobile user is usually trying to complete a specific task under constraints. A sales rep may need to check an account address before a meeting, log a visit afterward, update opportunity stage, scan recent activities, or call a contact. A service manager may need to review a high-priority case, approve an exception, or check a dashboard during travel. If the admin simply exposes the full desktop page, the mobile experience becomes slow and hard to scan.

Mobile design starts with the question: what should the user be able to do in less than a minute? The answer drives navigation, actions, compact layouts, page components, and field placement. The first fields shown on a record should identify the record and next action. Related lists should support common mobile decisions, not every possible relationship. Actions should be specific and safe. A mobile quick action for Log Visit may be better than asking users to open a full task editor.

Mobile design layer What it controls Admin judgment

Salesforce app navigation Main items users can reach quickly Put high-use objects and apps first for the user group.

Compact layout Key fields in record highlights Choose fields that identify status, priority, owner, and next step.

Quick actions Fast create, update, log, or custom workflows Use concise layouts and defaults for mobile tasks.

Lightning record page Component arrangement by app, profile, and form factor Avoid heavy desktop-only pages on phones.

Dynamic forms and visibility where available Field and component relevance Hide noise while preserving required data capture.

Global actions Cross-object creation or logging Use when the action is not naturally tied to one record page.

Admins configure pieces in several places. App navigation is managed in App Manager for Lightning apps and through Salesforce mobile app navigation settings where applicable. Compact layouts are managed in Object Manager. Quick actions are created globally or on objects and then placed on page layouts or Lightning pages depending on the action type and experience. Lightning App Builder lets the admin activate pages by app, record type, profile, and form factor. The right setup path depends on the symptom.

Testing by form factor is not optional. A record page that looks clean on a laptop can be frustrating on a phone if the important fields are buried below several components. A screen flow with many required fields can be hard to complete outdoors. A custom component can work in desktop Lightning but fail or perform poorly in the mobile app. Admins should preview mobile form factors and, for important workflows, test on actual devices with representative users.

Mobile security and support workflow

Mobile is a security boundary because Salesforce data leaves the desk environment. The admin should coordinate with identity, security, and device management owners when mobile use involves sensitive records. Login policies, multi-factor authentication, session settings, connected app controls, IP restrictions, and mobile device policies can affect whether users can access the app and how often they must authenticate. The exam-level point is that productivity never overrides access control.

A mobile rollout checklist:

Identify the mobile personas, such as field sales, executives, service managers, or partner-facing users.

List the top tasks each persona must complete from a phone or tablet.

Confirm object permissions, field permissions, record access, and approval access for those tasks.

Configure navigation, compact layouts, quick actions, and Lightning pages for the relevant apps and form factors.

Test with realistic data, slow network conditions, and at least one user from each permission model.

Document login, device, notification, and support expectations.

Monitor adoption through activity creation, mobile-specific feedback, and support tickets.

Support questions should be diagnosed systematically. If a user cannot see an object in the mobile app, check app navigation, app assignment, object permission, tab visibility, and profile or permission set access. If the user can see the record but cannot edit a field, check field-level security, page layout, dynamic visibility, validation rules, and record ownership. If an action is missing, check whether it is a global or object-specific action, where it is placed, whether the page is activated for mobile, and whether the action type is supported in that context.

Performance is part of usability. Large record pages with many related lists, report charts, rich text components, and custom components can load slowly on mobile. Admins should keep mobile pages focused and use component visibility to show what matters. Do not hide critical required fields so deeply that users abandon the workflow. Conversely, do not place every field at the top because one team may occasionally need it. Mobile page design is about priority.

Mobile notifications can help time-sensitive work, but they should be governed like Chatter notifications. An approval request, high-priority case assignment, or meeting reminder may be useful. Frequent low-value notifications train users to ignore the app. The admin should coordinate notification behavior with process owners, especially when Flow, approval processes, and collaboration features send messages.

Hands-on practice: create a mobile-focused Lightning record page for a custom object in a playground. Add a compact layout with status, owner, and next action. Add a quick action that captures a short visit note and follow-up date. Activate the page for phone form factor if your setup supports it, then preview and test with a lower-permission user. The goal is to see how page design, permissions, actions, and adoption fit together.

Study trap: do not answer every mobile complaint with a custom app. Salesforce standard mobile configuration often solves navigation, page density, and quick-action problems. Custom development may be appropriate for specialized offline, barcode, geolocation, or device-native needs, but the administrator should first use standard app, action, page, and security controls.