Upper Help
Settings

App Config

Set what drivers see and do in the Upper mobile app — proof of delivery, navigation, and stop fields — from one place in Settings.

"App Config" is the set of Settings that decide what your drivers see and do in the Upper mobile app — the proof they collect at each stop, the navigation app their phone hands off to, and the fields they fill in. These controls aren't on a single screen; they live across a few Settings areas, and together they define how every driver behaves on every route.

If a driver opens a stop and sees a signature pad, a photo prompt, or a notes box, that's App Config at work. Set it once at the account level and every driver on every route follows the same playbook.

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

What App Config covers

AreaWhat it controlsWhere it lives
Proof of deliveryWhat drivers must collect to complete a stop — signature, photo, notesSettings > General > Delivery Options
NavigationThe default map app the driver's phone opens for turn-by-turnSettings > General > User Settings
Stop fieldsExtra information drivers capture at a stop, including barcode/QR scanningSettings > Customization

Where to configure each area

App Config isn't one menu. Each piece lives in its own Settings location.

Open Settings

In the left sidebar, go to Manage > Settings. The Settings page opens with a sub-navigation grouped into sections (General, Notifications, Customization, and more).

Set proof of delivery

Open General > Delivery Options to choose what drivers must collect before completing a stop — Signature Upload, Image Upload, and Service Notes, each toggled independently. This is also where you manage custom completion statuses.

Set the default navigation app

Open General > User Settings and set Default Navigation Map. Upper supports Google, Apple, Waze, Maps.Me, Yandex, Sygic, and in-app navigation. This is the app the driver's phone hands off to for turn-by-turn directions; the driver can also change it on their own device.

Add stop fields and scanning

Open the Customization section to define the extra fields drivers fill in at a stop. Barcode Fields turns on barcode or QR scanning at stops. Some Customization items, such as barcode scanning, may need to be enabled on your account before they appear — see Enable barcode scanning for drivers.

Why it matters

  • Consistency — Every driver follows the same playbook on every stop.
  • Clean data — Standardized proof of delivery means the records you collect are the records you wanted.
  • Faster onboarding — Set behavior once at the account level instead of correcting each new driver.

Configure these settings before onboarding new drivers. Test the workflow with one driver first, then roll it out fleet-wide once it's right. Revisit App Config as your operational requirements change.

Common scenarios

  • You're onboarding a new fleet and want everyone consistent from day one — Set proof of delivery, navigation, and stop fields before sending the first dispatch. The first day's data lands the way you wanted from the start.
  • A new rule requires a signature on every delivery — Turn on Signature Upload in Delivery Options once. Every driver picks up the change on their next route.
  • Your field crew needs to document each visit — Turn on Service Notes so drivers record context after completing each stop.

Troubleshooting

On this page