Why this panel exists. Administration is the screen nobody opens until something is already broken. Surfacing the four or five things that are quietly wrong turns it from a settings dump into a queue, the same way the Action Center does for operations.

Two decisions worth naming. First, permission is scoped by region as well as by role: Sarah Monroe has Edit on maintenance, but only for the 349 units in Northeast and Southeast. A role alone is not an answer in a multi-region fleet. Second, Approve repair over $2,500 is its own capability rather than a consequence of Edit on maintenance. Approval authority is a financial control, not a workflow step, which is why Finance holds it and the Maintenance Manager who opens the work order does not.

Field mapping is a column, not a settings page. A source can be green and still be feeding you a partial picture. Toll Aggregator is connected and healthy, and 24% of its fields are unmapped, which quietly understates cost per mile. Connected and complete are different questions, so the table answers both.

An error screen should answer three questions. What broke, what is still working, and how long you have before it costs you something. Most integration screens answer only the first, which is why an amber dot sends someone hunting through logs to find out whether it matters.

Rotation policy: 180 days. Keys past policy stay active and surface on the Overview queue rather than failing silently at renewal time.

Recipients are roles plus region, never named people. Naming an individual means the rule silently breaks the day they change jobs, and in a fleet that is how a critical fault ends up notifying nobody. Escalation exists for the same reason: an unacknowledged HOS violation is a citation, so it does not get to sit in one person's queue.