Mobile Configuration
Mobile Configuration in Salesforce is the umbrella term for the Setup-side configuration that controls how the Salesforce mobile app and Mobile Publisher-deployed apps behave for end users.
Definition
Mobile Configuration in Salesforce is the umbrella term for the Setup-side configuration that controls how the Salesforce mobile app and Mobile Publisher-deployed apps behave for end users. The configuration spans several Setup nodes: Salesforce Mobile App Quickstart for the standard mobile-app setup, Mobile Publisher for white-label apps, Mobile Notifications for push-notification routing, Mobile App settings for global mobile behavior, and the broader Lightning App Builder for mobile-specific record pages.
Mobile Configuration matters because the Salesforce mobile experience is meaningfully different from desktop Lightning Experience. Mobile users see smaller screens, work in shorter sessions, often without reliable connectivity, and need offline data access. The mobile configuration tunes the experience for these constraints: which pages render on mobile, which actions appear in the global actions menu, which notifications fire, and which data caches offline. Without thoughtful configuration, the mobile experience defaults to a phone-sized desktop UI; with it, mobile users get a tailored experience that matches how they actually work.
The Setup nodes that drive Salesforce Mobile Configuration
Salesforce Mobile App Quickstart
Setup, Salesforce Mobile App Quickstart is the entry point for basic mobile configuration. It surfaces the most-common settings: which app branding shows, which apps users can switch between, which notifications fire. The Quickstart is the daily admin tool for mobile setup; deeper configuration lives in other nodes.
Mobile-specific Lightning Pages
Lightning App Builder lets admins build separate page layouts for mobile vs. desktop. A record page can have a Phone variant with different components, different component ordering, and mobile-specific Lightning Components. The dual-layout pattern is the foundation of any serious mobile customization.
Mobile Notifications
Push notifications drive mobile engagement. Setup, Mobile Notifications, configures which events fire notifications, which users receive them, and what action the notification triggers (open a record, open a Flow). Modern Salesforce orgs configure notifications around critical-path events: approvals to action, cases assigned to me, opportunities at risk.
Mobile Publisher
Mobile Publisher is the Salesforce-supplied product for white-labeled mobile apps. Customers build their own branded apps on top of the Salesforce mobile platform: their logo, their colors, their app-store listing. The Publisher handles the app-store submission and the ongoing publishing pipeline.
Offline configuration
Mobile users frequently lose connectivity. The mobile experience can cache the user''s active records locally and let them view and edit while offline. The configuration is part of the mobile app settings; admins decide which objects cache, how much data, and how conflicts resolve on sync.
Per-persona configuration
Different personas need different mobile experiences. Outside sales reps need voice capture and offline (the Seller-Focused Experience); service technicians need work order details and route maps (Field Service mobile); executives need dashboards and approval queues. Salesforce supports per-persona mobile configuration; tune each one based on the workflow.
Mobile App Security
Mobile devices are theft-prone and may run untrusted networks. The mobile configuration includes security settings: passcode requirement, biometric authentication, session timeout, remote wipe via MDM integration. The combination protects sensitive data even when devices are lost.
Configure Salesforce Mobile for the org''s users
Mobile Configuration is a multi-node Setup workflow. Plan a few days of configuration plus testing on real devices before rolling out broadly.
- Open Salesforce Mobile App Quickstart
Setup, Quick Find, Mobile App Quickstart. Confirm Salesforce Mobile is enabled and basic settings are correct.
- Build mobile-specific Lightning Pages
Lightning App Builder, create Phone-variant pages for record types where mobile users need a different layout than desktop.
- Configure Mobile Notifications
Setup, Mobile Notifications, set up notifications for critical-path events: approvals, case assignments, opportunity changes.
- Enable Offline behavior
Configure offline caching for the objects users frequently touch while disconnected. Test sync behavior carefully.
- Apply security settings
Setup, Session Settings, configure mobile-specific timeouts, passcode requirements, biometric authentication.
- Test on real devices
Install the Salesforce mobile app on iOS and Android. Test the full workflow as a real user; emulators miss real-world friction.
- Real-device testing catches issues emulators miss. Test the full workflow on iOS and Android before rolling out.
- Mobile Notifications respect user-level notification preferences. Configuring notifications globally doesn''t guarantee users see them.
- Offline sync conflicts need configurable resolution rules. Default rules may not match business needs.
- Mobile-specific Lightning Pages must still respect field-level security. Hiding fields on mobile via FLS works; hiding via mobile-only layout is less restrictive.
Trust & references
Cross-checked against the following references.
- Salesforce Mobile AppSalesforce Help
- Set Up the Salesforce AppSalesforce Help
Straight from the source - Salesforce's reference material on Mobile Configuration.
- Mobile PublisherSalesforce Help
Hands-on resources to go deeper on Mobile Configuration.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Mobile Configuration control?
Q2. Why does mobile configuration matter?
Q3. How can mobile pages differ from desktop?
Discussion
Loading discussion…