Skip to main content

The manager app and manager web

The manager app runs on a phone; manager web does the same work in a browser. Owners, admins and fleet managers sign in to them.

Overview​

  • The figures: vehicles, moving, open alerts, active drivers.
  • Waiting for approval: commands to Approve (asked first) or Deny. See Remote commands.
  • Trackers needing action, with what is wrong.
  • Documents to renew.
  • Licences at risk: drivers near the black-points threshold, with their fines → tap a driver.
  • The open alerts.

Fleet​

Fleet → Active, In the workshop, All: each vehicle moving or parked, its speed, when it last reported. A vehicle:

  • its position, and a banner when an inspection defect keeps it off the road;
  • Locate now (manager web), its alerts, trips, inspections and driver;
  • its Fuel tank, refuels and drains, when measured;
  • Open in the console (manager web).

Alerts​

New alerts arrive live. An alert → Acknowledge, Resolve with a note, Add note. On manager web a stale page is told someone else changed it.

The phone app also receives alerts as push notifications; manager web does not.

Drivers​

Drivers → search → a driver: driving time, licence and keys (iButton, RFID), traffic fines and black points, away … – … when on leave.

Integrations​

Account → Integrations (manager web: Integrations):

  • Installed: the adapters your organisation added from the marketplace, each with its version and state;
  • Included: what ZAITRACK builds in for every organisation, free: the device codecs, ZATCA e-invoicing, toll and fine imports, fuel;
  • Open the marketplace.

Detailed codec preparation​

Manager web and the manager app’s web showcase display the preparation details below. Availability in an installed Android or iOS app depends on that app’s release.

Each installed codec shows Current version separately from Codec preparation and Target version:

  • The installation's state stays separate from the target's preparation result. A suspended installation does not become active merely because preparation is complete. The current version can remain bound while an upgrade is pending.
  • The current-version message distinguishes a recorded preparation receipt, a legacy binding without a receipt, and no receipt. Legacy does not mean the device failed or that a new check succeeded.
  • Attempts, Last attempt and Checked show recorded preparation work when available. Next attempt appears only while preparation is pending. A failed result can have a check time; the timestamp is not live device health.
  • When supplied, the failure reason is shown as text. Preparation not reported means the registry supplied no usable details; unfamiliar states appear as unknown, not as successful checks.
  • Preparation does not prove device connectivity or current runtime health. A codec's active installation label alone does not make that claim either.

This display is read-only. Use Adapter Studio for confirmed retries, upgrades, settings and installation actions; see Codec preparation. The Console's preparation display is already available; see Integrations.

Language and theme​

Six languages, Arabic as written in each GCC country, right to left for Arabic and Urdu; Light, Auto or Dark. Kept on the phone or in the browser. Alert titles and rule names show as the platform sends them.