Some of this screen could not be read
the list of people, outstanding invites, command permissions, corridor coverage did not answer, so those readings show n/a rather than a number. Nothing above is a measured zero.Needs you
Things only an administrator can put right. An empty list is the correct state, not a missing one.
Can everybody actually sign in?
Where sign-in and this system disagree about someone's role
A role is kept in two places. When they disagree, nobody gets extra access — the person is locked out instead, silently, and to them it looks like being signed out the moment they sign in.
Checking every account…
What each corridor is allowed to do
This is a safety setting, not a label. A corridor set to watch only, or to watch and suggest, refuses every instruction outright.
What the network can report
Corridors that have been surveyed, and the smaller number of those with a planned gap set.
The control service did not answer, so coverage could not be counted at all.
Two things only an administrator can set
Both refuse rather than guess. Read this before treating either as a broken form.
Depot. Somebody with a depot role sees only their own depot's buses, and that narrowing happens on the server before any bus data is sent. Someone with no depot set is refused outright rather than shown the whole state's buses, because the fallback that looks helpful is the one that hands 143 depots' buses to whoever was set up last.
Bus. The bus set on a driver decides which instructions reach them. If a driver could set their own, they could send another bus's instructions to their own cab — so only an administrator can set it, and a bus number sent by the driver is never trusted instead.
Manage people and what they are set to