# Key concepts

> The building blocks you will see across the console, CLI and coding tools.

Source: https://diakrin.com/docs/concepts

These are the building blocks you will meet in the console, the CLI and your coding tool. Knowing them makes every other guide quicker to read.

```diagram concept-model
An organization holds people, optional projects, apps and company cloud setups. People are assigned to apps, and apps run on a setup.
```

## Structure

| Term | What it means |
| --- | --- |
| **Organization** | Your company's tenant in Diakrin. Members, apps, setups and policies belong to one organization, and nothing crosses between organizations. |
| **App** | The unit of work: one internal application with its requirements, audience, budget, releases and deployments. Each app has a stable app ID. |
| **Project** | An optional group of apps that share permissions, budget and policy. Grouping never grants extra access. |
| **Company cloud setup** | A connected cloud account (an AWS account or Google Cloud project today) plus the shared infrastructure created from a reviewed template. Apps deploy into a setup. |
| **Template** | A reviewed, versioned blueprint for a setup or a starter app. Its version and digest are pinned when you choose it, so it never upgrades silently. |
| **Environment** | The exact target a release goes to, such as a preview or production. |

## People and access

| Term | What it means |
| --- | --- |
| **Role** | What a member may do across the organization: Owner, IT administrator (Admin), Technical administrator, Builder or Member. See [Invite your team and set roles](/docs/team). |
| **Technical owner** | The owner, admin or Technical administrator responsible for running an app or a setup. The title alone grants no cloud, spending or approval rights. |
| **Audience** | Who can open a deployed app: named people, directory groups, access groups or everyone in the organization. |
| **Directory group** | A group pushed from your identity provider through SCIM. It is read-only in Diakrin. |
| **Access group** | A business group IT manages in Diakrin. It can follow a directory group. |
| **Connection token** | A personal token that lets your coding tool act as you over MCP. It never grants more than your own access. |

## Building and shipping

| Term | What it means |
| --- | --- |
| **Capability** | Something an app needs, such as reading a company data source. A requested capability is not an approved one. |
| **Grant** | IT's approval for a named operation, with resource and field limits. The app and each employee need their own grants. |
| **Release** | An immutable image built in your cloud from an exact source commit. A checked release has passed the customer-side checks. |
| **Preview** | A bounded, expiring deployment of a checked release, used to inspect it before production. |
| **Plan** | The exact release, target, cost estimate and access implications that a reviewer approves or denies. |
| **Operation** | A tracked build or deployment with an ID, stages and states. The console, CLI and MCP show the same operation. |
| **Deployment** | A release applied to an environment. It counts as live only with fresh, verified evidence. |

## Saved is not the same as live

Diakrin keeps intent and evidence apart. Each state below proves only what it says, so check the state of the exact app and environment before you rely on it.

```steps
Saved | | The app definition is stored. Nothing is built or approved yet.
Requested | | The app asks for a capability. Nothing is granted.
Approved | | Policy or IT permits the capability. It still needs a configured, verified connection.
Built and checked | | An immutable image exists in your cloud and passed its checks. It is not deployed.
Previewed | | A bounded, expiring preview ran. It does not replace production approval.
Deployed | | The approved release was applied to the environment.
Verified live | | Fresh, server-verified evidence matches the promoted image, and an authorized employee can open the app.
```
