# Administration overview

Organization owners and administrators configure the structure around each production. Ordinary operators should receive only the applications, studios, and access window required for their work.

## Recommended Setup Order

1. Create the organization and invite another administrator.
2. Create an environment for each cloud account, region, or operational boundary.
3. For self-hosted AWS, create least-privilege credentials and add them to the environment.
4. Enable and configure the applications required by the production.
5. Create studios and assign resources.
6. Grant application and studio permissions to members.
7. Test instance access, signal flows, monitoring, and alerts before show day.

The organization and environment switchers set the scope for administrative changes. Confirm both before editing settings.

## Access Model

- **Owner** controls the organization and its membership.
- **Admin** can access organization and environment administration.
- **Member** has no administrative access by default.
- Environment permissions add an application role and optional studio scope for a member, with optional start and end dates.

Do not share user accounts. Invite each operator separately so access can be changed or removed without disrupting the rest of the crew.