Admin / Operator — First Week
What a new platform Operator does in their first week. Deliberate, slow, audit-first.
Welcome. Operator is the most trusted role on the platform — and the one with the deepest blast radius. Your first week is deliberately slow. Read, watch, ask, and resist the urge to change things. Every operator who got this seriously wrong got there by acting fast in week one.
- Day 1 — Receive your operator credentials from the platform Owner directly. Sign in at /admin/login and complete your forced password change. Change it again at end of week 1 — by then you'll have learned what a strong password feels like in this environment.
- Day 1 — Read the deep Admin Console guidance once, end to end. Don't act on any of it yet.
- Day 2 — Sit beside the current operator for the full day. Watch what they do, not what they say they do. The gap between those two is where most mistakes hide.
- Day 2-3 — Read every audit-log entry from the last 30 days. Patterns matter more than individual events. If something looks weird, ask before assuming.
- Day 3-4 — Pick one low-risk maintenance task (e.g., reviewing the operational-inventory drift dashboard) and walk it under supervision. Do not perform any user-management or backup operation alone yet.
- Day 4-5 — Read the platform's last two incident post-mortems if any exist. Operator work is judged by what didn't happen — knowing past near-misses is how you stay there.
- End of week 1 — Make a list of every system surface you don't yet understand. Bring that list to your weekly check-in with the Owner.
Why this mattersAdmin work is high-trust and high-impact. A first-week mistake on a user record creates a paper trail. A first-week mistake on a role template creates a security gap. A first-week mistake on a backup creates a recovery problem. The cost of going slowly in week one is zero; the cost of going fast can be permanent.
Operator work is a relationship with the Owner, not just a technical job. In your first week, send a short end-of-day summary every day: 'today I did X, Y, Z; tomorrow I plan to do A, B, C; questions I have are 1, 2.' Most operator-onboarding friction comes from gaps in communication, not gaps in skill.
What happens next
- By week 2 you should be performing routine read-only operations independently
- By week 4 you should own one user-management cycle end-to-end with Owner sign-off
- Bookmark the audit log — you'll be living in it
Related guidance