Organizations and projects
Structure teams, environments, roles, and project access without mixing scopes.
Organization roles
Owners control the organization and its membership. Administrators manage members, invitations, and project configuration. Members can use resources permitted by their project and credential scopes. Platform administrators are separate from organization roles and operate the UnrealOS service itself.
- Do not share an owner account.
- Use the smallest role that supports the task.
- Review membership and invitations regularly.
- Use a separate project for experiments that should not access production.
Project environments
Environments provide a clear boundary for editor devices, API keys, provider policy, and operational data. The default development, staging, and production environments are a starting point; add additional environments only when their policy and lifecycle are understood.
Scope rules
The API derives organization and project access from the authenticated session or credential. A project ID in a request body is not permission. Every project route verifies that the caller is a member of the owning organization and meets the required role.