Skip to content

Mobile setup

Generate pairing QR codes so mobile devices can connect to your company's installation in one scan.

Required role

Admin (primary). Mapper can also access if your Admin delegates.

Overview

Every mobile device — technician phones, mapper tablets — needs to be paired to your company's installation before it can sign in. The Mobile Setup page is where you generate the QR codes that pair them.

A QR code encodes:

  • The API URL (e.g. https://api.customer.sm-tm.app).
  • The company context (so users who belong to multiple companies land in the right one).
  • Optionally a pre-filled username (useful for shared devices).

Scanning the QR code in the mobile app during Pairing and setup one-shot configures the app.

Prerequisites

  • You have the Admin role (or delegated access).
  • The user(s) whose devices you're pairing already have accounts — see User management.

Open the Mobile Setup page

Mobile Setup in the sidebar, or sometimes nested under Settings → Mobile pairing depending on your installation.

You see:

  • The current installation URL at the top.
  • A large QR code that encodes the installation.
  • Optional fields to customise what the QR encodes.
  • A Print button for physical hand-outs.

Generate a generic QR code

For devices where the user will sign in manually after pairing:

  1. Open Mobile Setup.
  2. Leave the username field blank.
  3. Display the QR code on your screen.
  4. The user scans it from the mobile app's Setup → Scan QR code screen.
  5. They enter their email and password on the app's login screen.

Done. A single generic QR is enough for an entire company.

Generate a user-specific QR code

If you want to pre-fill the username for a technician (shared device, kiosk mode):

  1. Open Mobile Setup.
  2. Type the username (or pick from the user dropdown) into Pre-fill username.
  3. The QR code regenerates.
  4. Show or send to the user.
  5. When they scan, their username is already filled — they only type their password.

Pre-filled username is not authentication

The QR code doesn't log the user in — it only pre-populates a field. The user still types their password. Don't treat it as a credential.

Printing QR codes

For field distribution without sending each user a link:

  1. Click Print.
  2. The portal opens a print dialog with the QR code on an A4 page.
  3. Print and distribute to the team (or post at the entrance of the shop floor).

Each printed QR carries the same data as the on-screen version.

Pairing from the mobile app

The technician's side:

  1. Install the app.
  2. Launch → Setup → Scan QR code.
  3. Point the camera at your QR code.
  4. The app decodes and pre-fills everything.
  5. Sign in with email / password.

See Pairing and setup (mobile).

Regenerate the underlying token

The QR code embeds the installation's API token. If the token is rotated — because of scheduled rotation, suspected leak, or a security incident — the QR code also changes. Any previously-scanned QR becomes invalid on the next token refresh.

Token rotation is typically done by PegotecUser on the Companies page. Customer Admins don't rotate tokens themselves.

When to re-issue QR codes

  • On installation: once, generic QR for the whole company.
  • On token rotation: after a rotation, every device needs re-pairing. Issue a fresh QR.
  • On user account creation: not needed — the QR is installation-scoped, not user-scoped (unless you use pre-filled username).
  • On factory reset: the affected device needs to re-pair. A fresh QR scan does it.

Security considerations

A QR code is not a secret but it is sensitive

Anyone who scans it can sign in to your installation if they have credentials. Don't post a QR on a public-facing noticeboard.

Generic QR on shop floor, personalised QR for named users

Post the generic QR inside the controlled area where devices are provisioned. Send a user-specific QR direct to the user when they receive a new device.

QR-based pairing doesn't imply user identity

Pairing is a one-time device-to-installation handshake. Authentication (who is using the device) happens at sign-in. A paired device without a signed-in user can't do anything.

Things to watch for

  • QR code won't scan — display size too small, camera can't focus, or the printed copy is too small. Enlarge to at least ~4 cm on paper or full-screen on a browser.
  • Wrong installation after scan — you're showing a QR from a different environment (staging instead of production). Always confirm the installation URL shown above the QR.
  • Pre-filled username doesn't populate — the mobile app may be an older version that ignores that field. Update the app.

Troubleshooting

Problem See
Mobile can't reach the installation Confirm the URL on the QR matches what the device should connect to
Device pairs but login fails I can't log in
Scan decodes but opens the wrong company Admin may have generated the QR while scoped to a different company; regenerate
QR unreadable Print quality / size — regenerate and enlarge