Manual / When something looks wrong
A tab is greyed out
- For
- a controller
- Status
- current
- Covers
- the four tabs, and any control that is faded, padlocked or absent
- Last checked against the app
0963ac5(2026-08-19)
A control you cannot use is in one of three states, and they mean three different things. Telling them apart is the whole of this page.
What you are looking at
| State | How it looks | What it means |
|---|---|---|
| Absent | Not in the bar at all | This deployment does not have the thing behind it |
| Faded | Dimmed, and the pointer shows it will not take a click | It exists, but the data it needs has not been loaded |
| Padlocked | Muted, with a small 🔒 after the label, and still clickable | It exists and works; you are not allowed in yet |
Hover any of them. Where the app has a reason, it puts it in the tooltip.
Absent: the deployment does not have it
Diversions is the tab this happens to. A deployment that was not set up with the diversion register does not show the tab at all, and there is nothing to switch on from the app.
The same rule governs everything optional: an overlay with no source has no tile in the Layers panel, the Radio button is not drawn where no station is configured, and the Buses tile is missing where there is no live feed. Nothing in this app is offered as a dead switch.
What to do: nothing, from here. If your control room is meant to have it, ask whoever administers the deployment — it is a setup question, not a fault.
Faded: no roster has been loaded
Operations Analysis is the tab this happens to, and it is deliberately left on screen rather than removed, so that its absence is visible and explainable rather than silent.
Hovering it says, literally:
No roster loaded — run backend/build_shifts.py to enable
That sentence is written for whoever runs the server; the part that concerns you is the first four words. The tab draws entirely from the Kinetic Melbourne driver roster, and this deployment has not been given one.
What to do: ask whoever administers the deployment to load a roster. Until then, the tab cannot show anything, and clicking it does nothing at all.
Padlocked: it is there, and you are not signed in for it
Two tabs do this, and the click is the point — it asks you for credentials instead of dead-ending.
Operations Analysis, while signed out. Clicking it raises the Sign in card saying "Sign in to view the confidential operations roster." Sign in with an account that has the ops role and the app takes you straight to the tab.
Operations Analysis, signed in as a viewer. Clicking it shows a message rather than the sign-in card, because signing in again would not help:
Signed in as … (…). The Operations tab needs the ops role — ask an administrator.
Diversions, while signed out. Clicking it raises the Sign in card saying "Sign in to view the diversion register." Any role can then read the register; changing anything in it needs ops. See What your role lets you do.
When it changes under you
If an administrator changes your role while you are working, the tabs follow immediately — you do not have to sign out and back in. If you were sitting on a tab you have just lost access to, the app moves you to the Map Explorer rather than leaving you on a screen that has stopped working.
What they do not mean
Faded is not "no permission". Nobody can open a faded Operations Analysis, including an administrator. There is no roster to open.
Padlocked is not "broken". The tab is working; the app is refusing you, and saying so in words.
Absent is not hidden from you personally. Nobody using this deployment sees that tab. It is not a role, and there is no setting of yours that brings it back.
A tab you can open is not a tab that is fully populated. Some views inside a tab need their own data — the punctuality view in the Timetable tab needs observed running times to have been loaded, for instance — and they follow the same rule: present where the data is, absent where it is not.