One login for staff
One sign-in, every system you use
A code officer signs into one vendor for permits, another to look up a payment, a third to see whether the crew closed the work order, and keeps a spreadsheet for the truck. Four passwords for one afternoon's work — and a teacher at the August council meeting said the same thing about five.
What a Public Works supervisor sees after signing in
214
Open service requests
31
Past due over 14 days
19
Units out of service
288
Overtime hours this period
$92,050
Fuel this month
1
Sign-in for all of it
Why one login is the whole argument
- One directory. Staff accounts live in the city's own directory, with roles by department. Nobody keeps a private list of who has a vendor login.
- Offboarding is one action. When somebody leaves, access to everything ends the same afternoon. Today a departed employee can keep a vendor login for years, because nobody outside that vendor knows it exists.
- One audit trail. Who changed the water rate table, who voided the citation, who approved the pay application — one log, in the city's hands, not nine logs in nine companies'.
- Two-factor once, not nine times. Multi-factor authentication on one login is a policy the city can actually enforce. On nine vendor logins it is a memo nobody follows.
- Role-gated, not all-or-nothing. The city manager sees a count of accounts eligible for shut-off. The clerk who has to make the calls sees the list. Same system, different role.