AdminCenter is where leadership manages the people side of the platform itself — team accounts, roles, a screen-by-screen access matrix, PIN-gated sensitive centers, and where the shared drive actually points — instead of access being whatever it happened to default to.
Access control, roles, and where files live shouldn't be tribal knowledge — AdminCenter makes them a screen leadership can actually see and change.
Add or deactivate people, set their role, and keep one account list instead of asking around who still needs access.
A role list that drives Team Accounts, the Estimator/Role field in Project Center, and the columns of the access matrix — one place, not three.
Check a box to let a role see a given screen or nav group. Nothing is enforced until you explicitly turn it on — access starts fail-open, on purpose, so nobody gets locked out by accident during setup.
HR Center, Finance Center, and Admin Center itself carry their own PIN gate on top of role access — a role still needs the PIN to get past it.
A read-only view of the sender roster from Project Center's Estimators & Sending panel — who a proposal comes from, and the role Project Center checks against the access matrix.
Where each center reads and writes on the shared drive, under one fixed team root. Change a folder name here and every center picks it up next sync — nothing to reinstall.
Every admin change is logged, with a date-range view and print output across every center — not just this browser's short recent list.
One shared record everyone in the company reads from — not a settings file that only reflects whoever last opened it.
Define the roles your operation actually uses, then add each person's account and assign their role — the same role list feeds Project Center's own Estimator/Role field.
Check which screens each role can see. Until you save and enforce it, the system stays fail-open — everyone sees everything — so building the matrix is a deliberate, reviewable step, not a risk of locking someone out mid-setup.
Flip the enforce switch once the matrix looks right, and Project Center starts checking it — screen by screen, role by role.
HR, Finance, and Admin get an additional PIN on top of role access — a second, deliberate gate for the centers that hold the most sensitive data.
Set the shared-drive file locations once, and every center reads and writes from the same place — no separate configuration to keep in sync by hand.
Most shops manage access with a mental list of who's allowed to see what. That works until someone leaves, someone gets promoted, or someone new needs to know why they can't see a screen.
| Capability | Informal / by memory | Generic user-management software | AdminCenter |
|---|---|---|---|
| Role-based screen access matrix | ✕ | ~ | ✓ |
| Deliberate fail-open until enforcement is turned on | ✕ | ✕ | ✓ |
| Extra PIN gate on the most sensitive centers | ✕ | ~ | ✓ |
| Shared file-location config, no per-machine setup | ✕ | ✕ | ✓ |
| Printable, date-ranged activity log | ✕ | ~ | ✓ |
| Same login & database as production scheduling | ✕ | ✕ | ✓ |
| Requires its own vendor contract & login | ✕ | ✓ | ✕ |
✓ present · ~ partial / manual · ✕ not covered — for the last row, ✕ is the good outcome
Every deployment starts with the core platform — CRM, estimating, scheduling, production, billing. AdminCenter is one of the modules Rock River Consulting turns on based on what your operation actually runs and needs, alongside things like HR onboarding, machine maintenance, and the GM home page. Same database, same users, same login — nothing new to stand up or administer separately.