The builder configures the existing Field Service mobile app rather than creating a new object. You draft a configuration on the canvas, then publish it to reach workers. Here is the core path an admin follows.
- Open the builder
From Setup, search for Field Service Mobile App Builder in the Quick Find box and open it. Field Service must be enabled, and you need the right permissions to edit configurations.
- Create or clone a configuration
Create a new configuration or clone the default one to start from a known-good layout. Give it a clear name that signals which role or crew it targets.
- Build tabs and screens
On the canvas, set the tabs a worker sees and arrange fields, related lists, actions, and components on screens like the Work Order Overview Screen. Trim to what the task actually needs.
- Add actions, flows, and extensions
Place Quick Actions and Global Actions, add any screen flows, and wire up App Extensions for URLs or native apps. Order them so the most-used action sits at the top.
- Assign by profile and publish
Assign the configuration to the relevant user profiles, then publish. Workers receive the changes on their next sync.
Top-level navigation such as schedule and search tabs; you choose which appear and their order.
Record detail views like the Work Order Overview Screen, where you arrange fields, related lists, and components.
Quick Actions, Global Actions, and screen flows surfaced on each screen for tasks like signature capture or completion.
Links to a URL, a native iOS or Android app, or another Salesforce app, opened with record context.
Logo, key colors, and background image so the app reflects your company identity.
- Changes do not reach workers until you publish the configuration, so test on a draft first.
- Fields and components only display offline if they are on a primed screen; test with real network conditions.
- One configuration for everyone rarely fits; assign per profile so each role gets a relevant layout.