Field Service Mobile Settings
Field Service Mobile Settings is the Salesforce Setup page that controls how the Field Service mobile app behaves for your mobile workers on iOS and Android.
Definition
Field Service Mobile Settings is the Salesforce Setup page that controls how the Field Service mobile app behaves for your mobile workers on iOS and Android. It is where an admin decides which appointment notifications get pushed, which flows appear as app extensions, how the app brands itself, and how it collects geolocation. Settings are tied to user profiles, so two groups of technicians can get two different mobile experiences from the same org.
You reach it from Setup by entering "field service mobile" in Quick Find, then clicking Field Service Mobile Settings. The page lists a Default configuration plus any per-profile configurations you add. Click Show Details on a row to expand and edit it. The Default applies to anyone whose profile does not have its own row, so most orgs tune the Default first and add profile-specific rows only when a team needs something different.
How Field Service Mobile Settings shapes the technician app
Where it lives and how to open it
There are two doors into this page and both land in the same place. From Setup you enter "field service mobile" in Quick Find and click Field Service Mobile Settings. You can also reach it from Field Service Settings, the broader Field Service configuration hub, which links out to the mobile page under its own menu. Once you are there, the layout is a list of settings configurations rather than a single form. The first row is always Default. Below it sit any rows you have created for specific user profiles. Each row has a Show Details control that expands it so you can read and change the values inside. This list-of-configurations model is the thing to understand before anything else. You are not editing one global mobile setup. You are editing a set of named configurations, and the app picks the right one for each technician based on that technician's profile. Getting comfortable with Show Details and the Default row makes the rest of the page straightforward.
Profile-based configurations and the Default
The core idea is profile targeting. A Field Service Mobile Settings configuration is assigned to one or more user profiles, and the app loads whichever configuration matches the signed-in technician's profile. If no row matches a given profile, that technician falls back to the Default configuration. This lets you run different mobile behavior for different teams without standing up separate orgs. Installation technicians might get one set of flows and notifications, while inspection technicians get another, all from the same Field Service deployment. To create a profile-specific row you add a new configuration and tie it to the profiles it should serve. Practically, most teams spend their time tuning the Default first, because it covers the largest group, and then add targeted rows only where a team genuinely needs a different experience. Keep the number of configurations small and intentional. Every extra row is another thing to maintain when a flow name or notification policy changes, and drift between rows is a common source of "why does it work for me but not for her" support tickets.
Appointment notifications: dispatch and assignment
Two of the most-used settings govern when the app pushes appointment notifications to a technician's device. Send Appointment Notifications on Dispatch pushes a notification when a service appointment is dispatched, which is the moment dispatch commits the appointment to the worker. Send Appointment Notifications on Assignment pushes a notification when the appointment is assigned to the service resource, an earlier point in the lifecycle. The two are independent toggles, so you can notify on assignment, on dispatch, on both, or on neither, depending on how your dispatch process actually flows. Teams that assign far in advance but dispatch same-day often turn on dispatch notifications and leave assignment off, so technicians are not pinged about work that is still days out. Teams that want technicians to see their day forming in real time turn both on. These pushes ride on the Salesforce Field Service connected app, so push notifications must be working at the connected-app level for the toggles to do anything. If notifications are not arriving, check the connected app and device push permissions before assuming the toggle is wrong.
App extensions: putting flows in the technician's hands
App extensions are how you add custom actions to the mobile app, and the most common extension type points at a flow. When you create an app extension you give it a type, a launch value, a label, a name, and the scoped object types it should appear under. The type tells the app what kind of thing it is launching. The launch value identifies the specific flow or target. The label is the text the technician taps. The scoped object types control where the extension shows up, so a flow scoped to Work Order appears in the context of a work order and not everywhere. This is the main lever for tailoring what technicians can do in the field beyond viewing and editing records. A pre-work safety checklist, a parts-used capture flow, a customer sign-off step, all of these are typically delivered as flow-backed app extensions. Because extensions live inside a Field Service Mobile Settings configuration, you can give different profiles different extensions. The inspection team and the repair team can each get the flows that fit their job without seeing each other's.
Geolocation tracking and additional settings
The mobile app can report a technician's location back to Salesforce, and that behavior is controlled here under the additional settings for the configuration. Collect Service Resource Geolocation History turns resource tracking on, after which the app uploads the technician's geolocation to Salesforce at regular intervals while the app is running. Two values shape how that tracking behaves. Geolocation Update Frequency in Minutes controls how often the app polls location when it is in the foreground. Geolocation Accuracy controls how precise the collected reading is. Tighter accuracy and shorter intervals give dispatchers a clearer live picture but use more battery and more data, so the right setting depends on how much real-time visibility your operation actually needs. Location data also feeds geolocation-based actions, where the app can prompt or trigger something when a technician arrives at or leaves a site. Because location is sensitive, treat these toggles as a policy decision, not just a feature flag. Communicate to technicians what is collected and why, and align the configuration with your privacy and labor commitments before switching it on.
Branding and the in-app experience
Field Service Mobile Settings also covers presentation. Branding lets you set a brand color so the app carries your company's look instead of the default Salesforce styling, which matters when technicians wear your uniform and represent your company at a customer's door. Alongside branding sit the controls that shape day-to-day use, including how push notifications are customized and which in-app profile settings technicians can change for themselves. The push notification customization goes beyond the simple dispatch and assignment toggles, letting you tune the notifications the app sends so they fit your workflow. None of this changes what data a technician can see, which is still governed by sharing, permissions, and licenses. What it changes is how the app feels and how it communicates. Spending a little time on branding and notification wording pays off in adoption. An app that looks like it belongs to the company and that sends clear, well-timed pushes is one technicians trust and keep open, which is the whole point of putting Field Service in their pocket.
Prerequisites: connected app, license, and offline
Field Service Mobile Settings does not work in a vacuum. Before the toggles matter, the Salesforce Field Service connected app has to be downloaded and set up in the org, because that connected app is what carries push notifications, geolocation, and other app services. Each mobile worker also needs the right access: a Field Service Mobile license and the permissions that let them use the app. Without the license and connected app in place, the cleanest Mobile Settings configuration will not produce a working app. Offline is the other half of the field story. Because technicians often work where there is no signal, the app primes data so records are available offline, and offline considerations sit next to these settings in the Field Service mobile documentation. When you plan a configuration, think about which records a technician needs cached for the day and how that interacts with the notifications and extensions you turn on. A flow that depends on related records the device never primed will frustrate a technician standing in a basement with no bars. Settings, licensing, connected app, and offline priming are four parts of one deployment.
Set up the Field Service mobile experience for a team
Here is the practical path to set up the Field Service mobile experience for a team. You enable notifications, optionally add a flow as an app extension, and decide on geolocation, all inside a Field Service Mobile Settings configuration.
- Open Field Service Mobile Settings
In Setup, enter "field service mobile" in Quick Find and click Field Service Mobile Settings. You can also reach it from Field Service Settings. Confirm the Default row exists.
- Expand a configuration
Click Show Details on the Default row, or add a new configuration and assign it to the user profiles it should serve. Edit the Default first since it covers anyone without a profile-specific row.
- Set appointment notifications
Turn on Send Appointment Notifications on Dispatch or Send Appointment Notifications on Assignment, or both, to match when your dispatch process should ping technicians.
- Add an app extension (optional)
Create an app extension that launches a flow. Give it a type, launch value, label, name, and the scoped object types where it should appear, for example a parts-capture flow scoped to Work Order.
- Decide on geolocation
Under additional settings, choose whether to enable Collect Service Resource Geolocation History, then set Geolocation Update Frequency in Minutes and Geolocation Accuracy to balance live visibility against battery and data.
Pushes a notification when a service appointment is dispatched to the technician.
Pushes a notification when the appointment is assigned to the service resource.
A custom action defined by type, launch value, label, name, and scoped object types that launches a flow in context.
Enables the app to upload technician geolocation to Salesforce at regular intervals while running.
Sets the app's brand color so the mobile experience matches your company styling.
- Notifications ride on the Salesforce Field Service connected app. If the connected app or device push permissions are not set up, the dispatch and assignment toggles do nothing.
- A profile with no matching configuration falls back to the Default. If a technician sees the wrong flows or notifications, check which configuration their profile actually maps to.
- Geolocation tracking is a privacy decision, not just a toggle. Communicate what is collected, and tighter accuracy with shorter intervals costs battery and data.
- An app extension flow that needs related records the device never primed will fail in the field. Align offline priming with the extensions you enable.
Prefer this walkthrough as its own page? How to Field Service Mobile Settings in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Field Service Mobile Settings.
Hands-on resources to go deeper on Field Service Mobile Settings.
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 scope of configuration does the Field Service Mobile Settings page govern?
Q2. What capability does Field Service Mobile Settings provide for a lost or stolen technician device?
Q3. When you add a new service territory in Field Service Settings, why audit Field Service Mobile Settings too?
Discussion
Loading discussion…