# Glossary Look up the terms used across the ATLAS documentation. The web app uses US spelling, such as _Organization_. This documentation uses British spelling in prose and quotes labels exactly as the app shows them. ## Tenancy and structure | Term | Meaning | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Organisation | Your company's tenant, with its own sign-in, email domains, people and contract. Each person belongs to exactly one organisation. | | Space | A node in your organisation's hierarchy that holds people, model rules and budget. See [Spaces](https://docs.atlas.ilionx.dev/concepts/spaces.md). | | Organisation (root space) | The top space, created automatically with the organisation. It has no members, keys or budget of its own, but organisation-wide rules such as the maximum key lifetime sit here. | | Division | A governance space under the root or another Division. It has managers only and cannot hold API keys. | | Unit | A governance space under the root or a Division. It has managers only and cannot hold API keys. | | Team | A leaf space where people work. It has managers and members, and is the only space that can hold API keys, spending limits and member budget shares. A Team sits under a Unit. | | Governance space | A Division or Unit. It exists to carry shared rules down the tree. | | Project | A container for one AI deployment, with its own members, model list, API keys and funding. See [Projects](https://docs.atlas.ilionx.dev/concepts/projects.md). | | Funded project | A project that stops at the funds added to it. See [Projects](https://docs.atlas.ilionx.dev/concepts/projects.md#two-funding-modes). | | Tracked project | A project whose spend is recorded, with an optional monthly limit. See [Projects](https://docs.atlas.ilionx.dev/concepts/projects.md#two-funding-modes). | | Archived project | A project that refuses all gateway traffic. Its keys and history are kept, and you can reactivate it. | ## Keys and access | Term | Meaning | | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | API key | Credential that a person, tool or pipeline presents to the gateway. See [API keys](https://docs.atlas.ilionx.dev/reference/api-keys.md). | | Personal key | A key owned by one person. Its secret starts with `atl_sk_`. | | Project key | A key owned by a project rather than a person, so it survives staff changes. Its secret starts with `atl_pk_`. | | Acting context | The one Team space or active project a personal key acts under. It decides the models, budget and audit trail of a request. The web app calls it **Context**. See [API keys](https://docs.atlas.ilionx.dev/reference/api-keys.md#acting-context). | | Model reference | Name that callers use for a model: `provider-slug/model-slug`, for example `openai/gpt-4.1`. A bare model name is not found. | | Provider | An upstream AI service that ATLAS calls on your behalf, such as OpenAI, Azure OpenAI, Anthropic, AWS Bedrock or Ollama. | | Model | A priced configuration of one upstream model on a provider. Admins make models available to spaces and projects. | | Gateway | Service that receives model requests, checks the key, budget and model access, calls the provider and records the result. It offers an OpenAI-compatible and an Anthropic-compatible surface. See [Gateway reference](https://docs.atlas.ilionx.dev/reference/gateway.md). | | Budget | A spending ceiling on a space, a member or a project. The tightest ceiling in the chain wins. An empty budget means unlimited and `0` freezes spending. See [Budgets](https://docs.atlas.ilionx.dev/reference/budgets.md). | | Audit log | Record of every gateway request. Usage statistics, budgets and monthly statements are computed from it. See [Usage and audit](https://docs.atlas.ilionx.dev/concepts/usage-and-audit.md). | ## Roles The roles run from the widest level to the narrowest. For the full reference, see [Roles and permissions](https://docs.atlas.ilionx.dev/reference/roles-and-permissions.md). | Role | Level | In short | | --------------- | ------------------------------ | -------------------------------------------------------- | | Owner | Organisation | Full control. Exactly one per organisation. | | Admin | Organisation | Runs the organisation. | | Member | Organisation | Base role. Uses what spaces and projects give access to. | | Account Manager | Organisation (additional role) | Administers all projects and reads billing. | | Auditor | Organisation (additional role) | Reads audit log, payloads and usage. | | space manager | Space | Manages a space and everything below it. | | space member | Team space | Uses the space's models and budget. | | project manager | Project | Manages a project's members, keys and settings. | | project member | Project | Uses the project's models. | A person has one base role plus any additional roles. Effective capability is the combined permissions of every grant. ## Related - [Concepts](https://docs.atlas.ilionx.dev/concepts.md): how these parts fit together - [Errors](https://docs.atlas.ilionx.dev/reference/errors.md): what the gateway and web app return when something is refused - [Getting started](https://docs.atlas.ilionx.dev/getting-started.md)