Configure role-based access control for ZopNight scheduling. Define who can create schedules, apply overrides, and manage policies across teams.
This is the practical version, the one you can follow in a single sitting. It starts read-only, touches no production resource by default, and every step is reversible, so there is no point at which you are committed to something you cannot undo. Budget about 15 minutes. Before you start you will want: A ZopNight account with multiple team members; Defined organizational team structure; Understanding of who should manage which resources.
The steps
- Define your role hierarchy.
- Create teams in ZopNight.
- Assign roles per team.
- Configure approval workflows.
- Test and iterate.
Why this is safe to do today
The reason this is a low-stakes change is that nothing here is destructive. Scheduling stops and starts resources; it never deletes them, and your data persists across a stop exactly as it does across a normal reboot. Production is excluded by default, actions run in dependency order, and every state change is logged with what triggered it.
If you want the fuller context behind this task, the FinOps guide covers where it fits, and the AWS EC2 scheduling page shows the same loop applied to a specific resource.
Getting started
Getting started is intentionally low-stakes:
- Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
- Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status.
- Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
- Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.
Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
Can RBAC be scoped to specific environments?
Yes. ZopNight RBAC supports scoping by environment tag, cloud account, or resource group. A team lead can have Operator access to their dev environment but only Viewer access to staging.
What happens when someone leaves the team?
Remove their ZopNight access or change their role. Audit trails preserve the history of their actions. If using SSO, deactivating their identity provider account automatically revokes ZopNight access.