Upper Help
Settings

Control driver visibility

Control what drivers can see and access in Upper's mobile app using App Config — Route, Stops, Stop Logs, Parcel Info, Proof of Service, and Navigation permissions.

Upper lets you decide what each driver can access in the mobile app. From one place — the App Config editor — you control the actions and information drivers see across their route, their stops, proof of service, and navigation, so every driver works from the same playbook.

This guide uses Upper's default driver and delivery labels (for example, "Proof of Delivery"). Your workspace may be set to show Technician and Service instead — so you may see "Proof of Service" and "Technician App Config." Both label sets control the same features.

Why this matters

Drivers work faster and make fewer mistakes when their app shows only what the job needs. App Config lets you grant experienced drivers room to add stops or reverse a route, and lock down newer or compliance-heavy fleets so the dispatched plan stays the plan. Set it once and every driver follows the same rules.

Where driver visibility lives

App Config is a single editor that applies to your drivers. You can open it for all drivers at once, or for one driver from the Users/Technicians page.

The editor is organized into sections down the left side. Each section holds on/off toggles that control what drivers can access:

SectionWhat it controls
RouteCreate, delete, duplicate, and clear routes from the app
StopsAdd, edit, delete, and duplicate stops
Stop LogsUndo or update completed and skipped stops
Parcel InfoParcel place-in-vehicle, parcel count, and parcel photos
User SettingsOverride the default schedule, and shift duration tracking (clock in / clock out)
Proof of ServiceWhether photo, signature, and notes are required to complete or skip a stop
OptimizationReverse route and change stop navigation priority
NavigationLive location sharing, in-app navigation, and address-based navigation

A subtitle in the editor reads "All technicians will only be allowed to access the authorized options." Turning a toggle off removes that option from the driver's app.

How to configure driver visibility

Open the Users/Technicians page

In the left sidebar, go to Manage and open the users page. You'll see your drivers listed with their license status and an App Config Status column (General or Modified).

Open App Config

To set permissions for everyone, open the App Config for all Technicians editor. To change one driver, open their row's action menu (the kebab) and choose Technician App Config.

Choose a section

Use the left-hand sub-navigation in the editor to move between sections — Route, Stops, Stop Logs, Parcel Info, User Settings, Proof of Service, Optimization, and Navigation.

Toggle what drivers can access

Switch each option on or off. For example, turn off Delete Stop under Stops so drivers can't remove stops from a dispatched route, or turn off Undo completed/skipped stop under Stop Logs to keep completion records final.

Save

Select Save to apply your changes. Restore Settings resets the editor back to defaults.

Show or hide custom fields in the driver app

If you've set up custom stop fields, you decide whether drivers see them. In Settings > Customization > Custom Fields, use the Show custom fields in Driver App checkbox to surface those fields on the driver's stop screen or keep them dispatcher-only.

Keep the driver app focused on what the stop needs. Turn on only the custom fields a driver has to read or fill in, and leave back-office fields hidden.

Common scenarios

  • You want drivers to follow the dispatched route exactly — Turn off Create New Route, Delete Route, and Clear Route under Route, and Add/Delete Stop under Stops. Drivers run the plan as sent.
  • You need completion records to stay final — Turn off Undo completed/skipped stop and Update completed/skipped stops under Stop Logs.
  • You're rolling out a new driver app policy fleet-wide — Use App Config for all Technicians so every driver picks up the same rules at once.

Troubleshooting

On this page