Today at a glance
Routes
Anything needing attention first, then by delivery date
All routes
POD search
Issues
Operational report
Addresses
Address corrections
Owner-only. When the export's delivery address is wrong or blank for a customer, put the right one here (by customer reference) -- both apps and the printed POD use it, flagged as corrected.
| Customer ref | Delivery address to use |
|---|
Settings
People, company details, the rules drivers work to, and how the app is run. Your own login and notifications are under your name at the top.
Driver profiles
Who can log in to the driver app, and with what PIN.
Vehicle profiles
Offered in the assign-driver dialog and the driver's pick-up screen.
Only an Owner can change these settings. You can view them here, but ask an Owner to make changes.
Only an Owner can change these settings. You can view them here, but ask an Owner to make changes.
Only an Owner can change these settings. You can view them here, but ask an Owner to make changes.
Address corrections are on the Addresses page now.
Only an Owner can change these settings. You can view them here, but ask an Owner to make changes.
Customer texts (SMS)
Owner-only. Texts customers "on the way" messages on the contact mobile from the export (UK mobiles only; landlines are skipped). Each text is charged by your text provider, roughly 4-5p. Start in test mode to see what would be sent without paying for anything.
What customers see it's from: up to 11 letters/numbers. Customers can't reply to a name.
Texts due earlier wait until the start; after the end they're skipped.
A safety cap on cost.
Words you can use in a text
Uses the saved settings, so save first. Goes straight away (ignores sending hours).
Recent texts
Email recipients
Owner-only. Who should be emailed for which events. Email sending is not configured on this server yet -- these are saved so they're ready the moment a mail service is connected; nothing is sent today.
Browser pop-ups on each office computer are chosen by each person under their name at the top -- My settings.
Recipients for each event
API tokens (read-only)
Owner-only. Lets another system read routes (with their photo lists), signed POD PDFs, returns, drivers, vehicles, issue types, settings and health with Authorization: Bearer <token>. Filing PODs on the office drive: create a token labelled "POD filing" and give it to the POD filing program on the office PC (scripts/pod-filer.mjs -- see DEPLOY.md); "Last used" below shows it checking in. It can't read the address book, activity, logins or the security log, and can never change anything. The token is shown once when created and expires after 12 months unless you choose another date. Backup token: a separate kind, only for the backup program on the office server (scripts/backup-puller.mjs) -- it can fetch the backup (the whole database and photos, encrypted) and nothing else.
Webhooks
Owner-only. POSTs each event as JSON to your own system the moment it happens (signed with the secret, if set, as X-Epod-Signature: sha256=<HMAC>). Timeout 8s; every delivery is logged below.
Recent deliveries
Access rules
Owner-only. Session length applies to office and driver logins alike, counted from when they logged in -- after that they enter their password/PIN again, even if the app stayed open. A deploy or restart doesn't log anyone out.
At least 6. Applies to new PINs -- a shorter PIN set earlier keeps working and is flagged under Drivers & vehicles.
Anyone newly included sets it up at their next login -- they're asked to log in again straight away. Drivers use PINs and aren't affected.
Office accounts
Owner manages accounts, settings and data. Staff does everything operational. Planner schedules and assigns but can't resolve issues, authorise exceptions or unlock routes. Viewer is read-only.
Security log
Owner-only. Logins and failed logins, lockouts, account, PIN, settings, token, webhook and text-setting changes, exports and resets -- with who did it and from which address. Kept for the most recent 5,000 events unless changed in Data & backups -> Keeping data; never sent to webhooks.
| Time | Event | Who | Details |
|---|
Hansa link
Owner-only. Routes pulled straight from Hansa through S6K's ColdFusion data page wait in From Hansa (here, or on the Routes page) until an Owner imports them. Nothing goes on the schedule by itself.
Automatic pulls
Only refreshes the From Hansa list. Pull now is always there too.
3 = today and the next 2 days.
Lines shown but never ticked
Delivery charges, notes, adjustments and services -- shown to the driver as reference lines. Separate with commas. Lines with no item code are always headings.
Routes and exports
Import a day's route from its 3 Hansa export CSVs (no redeploy needed), or download every POD with its photos. Routes pulled straight from Hansa are on the Hansa link tab.
Clearing up the schedule
Owner-only. Hide the built-in demo routes, and put back routes removed by mistake. A route can be removed from its own page if nobody has started it; one with any loading, photos, issues or PODs is archived instead.
Loading...
Import rules
Owner-only. Column aliases let an export whose headers differ from this app's expected names import without a code change -- one line per canonical column: customer_name: Customer Name, Cust Name. (Auto-archiving moved to Keeping data, below.)
Keeping data
Owner-only. When finished routes are archived, how long things are kept before they're cleared automatically, and when a stopped backup raises the alarm. Signed PODs are never cleared by these.
Finished routes
Archived routes leave the dashboard and route list; they're still in POD search and Reports.
Keeps the working list quick. Stored routes still show with "Show archived" and in POD search.
Clearing up
Shows in the red "needs attention" banner and the uptime monitor.
Logs
Every login, lockout and settings change. More is better for looking back after a problem.
Settings file
Owner-only. Save every setting on this page as one file -- company details and logo, issue types, POD and workflow rules, customer and address overrides, text and email settings -- and load it back here or on another copy of the app (the staging app, a new install). It doesn't contain logins, PINs, vehicles, tokens, webhooks or the text provider's password.
Reset demo
Clears the day's route work -- imported routes, ticks, issues, photos, assignments and PODs -- after archiving every completed POD and its photos. Everything else is kept: all settings, office accounts, drivers and PINs, vehicles, tokens, webhooks and the address book.
Who's logged in
Live = app open and active in the last 90 seconds. Idle = still logged in, but the app isn't open right now (phone locked, tab closed). Updates automatically while this tab is open.
Office
Drivers & loaders
Two-factor login
A code from an authenticator app on your phone (Microsoft or Google Authenticator), as well as your password, each time you log in -- so a password alone isn't enough. Required for Owners, and for other roles if an Owner has chosen that (Access & security); anyone else can turn it on. Lost your phone? Use a recovery code, or ask an Owner to reset it.
Loading…
Notifications on this computer
Pops a desktop notification while this portal is open in a tab. Per browser, not per account -- each office computer chooses its own. Saved as you tick.
About this app
Which build is running, and basic server health -- useful when reporting a problem or checking a device has picked up an update.