# Access control

Projects, global roles and project permissions.

> Section: Platform

## The project boundary

Every resource belongs to exactly one project. There is no cross-project access setting, which means there is no cross-project access to accidentally leave enabled.

## Two levels

A global role describes the kind of account. Project permissions describe what that account may do inside a particular project. Both are evaluated on every operation, including operations made with an API key.

## New accounts are not superusers

A new managed account receives Admin and ownership of its first project. It never receives global Master User privileges automatically.

## Use projects to separate environments

Staging and production as separate projects gives you separate credentials, separate keys, separate audit trails and separate blast radius. It costs nothing and prevents the most expensive category of mistake.