Tenant Administration designed
Customer-admin work is distinct from normal user work. The admin path should focus on governance of people, projects, spend, and approved support paths.
Responsibilities
- Maintain project and member access.
- Keep SSH/API key guidance consistent for tenant users.
- Track spending, credits, and low-balance posture.
- Escalate release failures, recovery actions, or policy questions through the approved support path.
- Understand which actions are self-service and which remain operator-assisted.
Admin Checklist
| Area | What to verify |
|---|---|
| Project context | Users are landing in the right tenant/project |
| Access | Membership, roles, and key posture are correct |
| Spend | Budgets, balance posture, and warnings are visible |
| Recovery | MFA/account recovery guidance is known before a user loses access |
| Support handoff | Correlation ids and user-visible state are captured before escalation |
Admin vs Operator Boundary
Customer admins should not need operator-only docs for normal governance. Operator runbooks remain in the internal Operators section and should be linked only through approved support or escalation flows.