🔎 Find
🧾 History 0 shown
newest first · click a row for the full detail
What this history does not contain. Every edit a person makes on any page, in the field app or
through a WhatsApp link is recorded here — including edits from the old IMS page, which has no login,
so those rows name a connection and a device but no person.
Two things are missing on purpose: the field app's automatic telemetry
(six background signals) written by phones on a timer with nobody touching
them, and the scheduled jobs that run on the clock — nobody starts those,
so they have no user, no connection and no device to record. Full details at the bottom of this page.
| When (IST) | User | What | Where | Device | Result |
|---|---|---|---|---|---|
| Loading… | |||||
📍 Places — name your internet connections
The system stores the IP address every edit came from. It does not ask anyone's phone for its
location and nobody is prompted for permission — so there is nothing for anyone to switch off.
An IP you name below shows as that name; every other IP shows as Outside with the address beside it.
The office runs on one connection, so this answers “from the factory, or from outside?” — not which desk.
Nothing is pre-filled and no outside geo-IP service is ever contacted: the list below is only what has
actually appeared in your own history. Renaming applies to old rows too.
Internet connection
Who used it / on what
Call it
Loading…
How this history works, and what is deliberately left out of it
Every edit, with no way to opt out. The system answers requests on two addresses, and both are
captured — so a change made from any page, the field app, the old IMS page or a WhatsApp link is
recorded the same way. Of all … server actions,
… change data or send something out and are recorded;
… only read data and are not.
- The old IMS page has no login at all, and neither does the purchase form (…). Those edits are recorded, but the endpoint they use asks for no user, so the row can only name the connection and the device — never a person. Filter the User box to Old IMS page to see them. They also answer “done” even when they refuse the edit, so a green result there means the call finished, not that it was accepted.
- Failed attempts are kept too, marked red — a refused edit says as much as a successful one. On a failed row the user name is what the caller claimed: the call never went through, so nothing confirmed it — the sign-in itself may be what failed.
- Passwords, photos and file uploads are never stored. Each row keeps the action, the user, and at most one short record id (an order number, a staff id). Nothing else from the request is written down.
- Nothing here can be deleted or edited — not by staff, not by an admin, not by the backup tools. The only thing this page can change is what an IP is called.
- Sign-ins are kept as well as edits. … They change no data, so they are marked view and can be hidden with the Show filter — but they answer “was this person in the factory when he signed in?”, which is the whole point of the page.
- This page is admin-only, on the server as well as in the browser.
- If an action ever appears marked not yet classified, it is a new feature nobody has described yet. It is still recorded, with its raw internal name — a new action can never go silently unlogged.
Deliberately excluded — the field app's automatic telemetry. These are written by phones on a timer,
not by a person, and run to … calls a day against roughly
… real edits. Recording them would bury the history 25–50× deep in GPS pings:
Not here at all — the scheduled jobs. These run on the clock, not on a request. Nobody presses
anything, so there is no user, no internet connection and no device to record, and a history row
would have to invent all three. They send WhatsApps and e-mails, and the day-close sweep marks
unanswered checklist points ✗, so their effects are real — but the record of what a scheduled job did
lives in that module's own log, not here: