Organizations, projects & environments
The tenancy tree, roles and what is scoped where.
| Level | Holds | Notes |
|---|---|---|
| Organization | Members, billing, invoices, the audit trail | Usage from every project rolls up into one invoice. |
| Project | Environments, project members and their roles, retention | Roles are granted per project. |
| Environment | API keys and all product data | Events, errors, rooms, flags, campaigns… are all environment-scoped. |
Roles
Access is granted per project on a four-step ladder:
| Role | Can |
|---|---|
| Owner | Everything, including deleting the project and managing owners. |
| Admin | Manage members, keys, settings and every product. |
| Developer | Use and configure every product (including Telescope settings). |
| Viewer | Read data in the console. |
Invite people from IAM in the console; an invitation link adds them to the organization and project with the role you picked.
Names and slugs
An organization or project has a name and a slug. The slug never changes. Renaming is limited — an organization once every 12 months, a project once every 6 — so links and reports stay recognisable.
Data retention
Each project has a retention window. Telemetry older than the window is no longer returned by the console or the API. Telescope keeps its own, shorter retention (48 hours by default, up to 14 days) configured under Telescope → Settings.