Manual / Getting started
What your role lets you do
- For
- a controller, and whoever is asked "why can't I see that?"
- Status
- current
- Covers
- the four tabs, the Admin Console button, and the New diversion button
- Last checked against the app
0963ac5(2026-08-19)
Your account carries one of three roles — viewer, ops or admin — and it is printed beside your username at the right of the top bar. This page says what each of them puts on the screen, in buttons rather than in permissions, because buttons are what you will actually notice missing.
What you are looking at
Five states, not three. "No accounts at all" and "signed out" are as common as the three roles, and they look different from each other.
| Your situation | What is on screen |
|---|---|
| This deployment has no accounts | Everything the deployment has, with no account block in the top bar. Nothing is locked and nothing asks who you are |
| Signed out (accounts exist) | Map Explorer and Timetable in full, the ⚙ Settings panel, the version chip and this manual. Operations Analysis and Diversions each wear a padlock and ask you to sign in when clicked |
| viewer | The above, plus the Diversions tab to read: the register, each record, its map and its documents |
| ops | Everything a viewer has, plus the whole Operations Analysis tab and every control that changes a diversion — starting with New diversion |
| admin | Everything, plus the Admin Console button beside your name |
The three differences you will actually notice
Operations Analysis is the ops line. It is built from the confidential driver roster, so a viewer cannot open it. The tab stays in the bar wearing a padlock, and clicking it tells you why: "Signed in as … (…). The Operations tab needs the ops role — ask an administrator." Note that the message calls it "the Operations tab" while the button says Operations Analysis; they are the same tab.
Diversions splits read from write. Any signed-in account can open the register and read a record, its map, its steps and its documents. Changing one needs ops, and the app does not hide that with an error — the New diversion button is not drawn at all, and the panels that would let you edit say so in place: "Drafting one needs the ops role", "Placing anchors needs the ops role", "Read-only: changing the bulletin layout needs the ops role".
Admin Console is the admin line. It is one button beside your name, and it opens a panel headed Users & access holding four things: the list of accounts with Reset password, Disable, Sign out and Delete on each; Add an account; Data versions, where a newer timetable or roster is promoted and the server told to Reload from disk; and Recent activity, the record of who did what.
What they do not mean
A missing button is not always a role. Three different things remove a control from this app, and they look identical:
- your role — the case this page is about;
- your deployment has no data for it — no roster loaded, no live feed configured, no road extract built. The Operations Analysis tab goes faded with a tooltip naming what is missing; an overlay with no source has no tile in the Layers panel at all;
- nothing is selected yet — several panels only exist once you have picked a route, a stop or a bus.
Before assuming a permission problem, hover the control. This app puts the reason in the tooltip where it has one.
The roles are stacked, not separate. ops can do everything a viewer can; admin can do everything ops can. Nobody has to hold two accounts.
Nothing in the app changes your own role. Only an administrator can, from the Admin Console, and the change reaches you without signing out and back in: the tabs you gained appear, and if you were sitting on a tab you have just lost, the app moves you back to the Map Explorer rather than leaving you on a screen that no longer works.
A role is not an audit exemption. Every sign-in and every administrative action is written to the record the Admin Console shows under Recent activity.