> For the complete documentation index, see [llms.txt](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/documentation/emcp-core-concepts.md).

# EMCP Core Concepts

Everything you do in the Enclaive Multi Cloud Platform (EMCP) happens inside a clear hierarchy. Understanding it helps you decide where to sign in, who can see what, and where your confidential workloads live and are billed.

```mermaid
graph TD
    T["Tenant<br/>(own console URL)"] --> U["Users"]
    T --> TM["Teams"]
    U -. "member of" .-> TM
    TM --> P["Projects"]
    TM --> Q["Quotas & Billing"]
    P --> R["Resources<br/>VMs · Databases · Kubernetes · Applications"]
```

| Concept  | What it is                                                       | Belongs to |
| -------- | ---------------------------------------------------------------- | ---------- |
| Tenant   | An isolated EMCP environment with its own URL                    | –          |
| User     | A person with an EMCP account                                    | Tenant     |
| Team     | A group of users that shares projects, quotas and billing        | Tenant     |
| Project  | A workspace inside a team that groups resources                  | Team       |
| Resource | A confidential workload: VM, database, Kubernetes cluster or app | Project    |

### Tenant

A Tenant is a dedicated, isolated EMCP environment for one customer. Each tenant has its own console URL, its own users and its own teams. Nothing is shared between tenants. The idea is similar to Cloud Solution Providers like an Azure tenant that a company sets up for its own domain.

There are two kinds of tenants:

<table><thead><tr><th width="215.96484375">Tenant type</th><th>URL</th><th>Typical use</th></tr></thead><tbody><tr><td>Dedicated tenant</td><td>Customer-specific URL (for example: acme.enclaive.cloud)</td><td>Live customers and Proofs of Concept (PoCs)</td></tr><tr><td>Public tenant</td><td><a href="https://console.enclaive.cloud">https://console.enclaive.cloud</a></td><td>Self-service sign-up, trying out EMCP, enclaive demos</td></tr></tbody></table>

> **Which tenant should I use?** If your organization has a dedicated tenant, always sign in at your tenant URL. Your teams, projects and resources only exist there. If you just want to evaluate EMCP, register at [here](https://console.enclaive.cloud).

> **Note:** Accounts are bound to a tenant. An account on [EMCP](https://console.enclaive.cloud/) cannot sign in to a dedicated tenant, and vice versa.&#x20;

### Users

A User is a person who signs in to a tenant. See [Registration](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/tutorials/emcp-account/registration) and [Login](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/tutorials/emcp-account/login).

* A user can be a member of several teams within the same tenant.
* At any time, a user works in exactly one current team. All actions (creating projects, launching resources, viewing costs) apply to the current team. Switch the current team to work in another one.
* Users join a team by [invitation](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/tutorials/settings/manage-team/invite-team-members).

### Teams

A Team is the central unit of collaboration and accounting in a tenant. A team consists of members and projects.

The team holds everything that is shared:

* **Members and their roles** – who belongs to the team and what they may do.
* **Projects** – every project belongs to exactly one team.
* **Billing settings** – payment method, address and VAT are configured per team. See [Billing](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/tutorials/billing).
* **Quotas** – limits per cloud provider, e.g. the number of VMs, Kubernetes nodes, databases and applications the team can run.

#### Roles

| Role           | Permissions                                                                                                        |
| -------------- | ------------------------------------------------------------------------------------------------------------------ |
| Owner          | A team owner with complete administrative control. Subscription secrets remain creator-only.                       |
| Admin          | A team administrator who manages members, resources and billing but cannot delete the team or remove another Admin |
| Member         | A technical user who manages projects, cloud resources and their own subscriptions but not billing or members.     |
| Biller         | A finance user who manages billing information, payments, invoices and billing alerts without access to workloads. |
| Billing viewer | a finance or audit user who can review billing information without making changes.                                 |

> **Note:** A team can only be deleted when it has no active resources. Only the team administrator can remove members.

#### How-to guides:

* [Create a team](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/tutorials/settings/manage-team/create-a-team)
* [Invite team members](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/tutorials/settings/manage-team/invite-team-members)
* [Remove team members](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/tutorials/settings/manage-team/remove-team-members)
* [Delete a team](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/tutorials/settings/manage-team/delete-a-team)

### Projects

A Project is a workspace inside a team that groups related resources, for example by application, environment or use case.

* Every project belongs to exactly one team, and all members of that team have access to it.
* A team can have multiple projects.
* Each project has a name, an optional description, a purpose and an environment (e.g. Development).
* Resources can be moved between projects of the same team, e.g. when you create a new project and want to transfer existing workloads into it.
* A project can only be deleted when it contains no active resources.

> **Tip:** Use separate projects for separate environments (e.g. dev, staging, prod) so that resources, activity and costs stay clearly separated.

### Resources

Resources are the confidential workloads you run with EMCP. Each resource lives in exactly one project.

| Resource type                   | EMCP feature                        | Guide                                                                                                                                                      |
| ------------------------------- | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Confidential VM                 | Buckypaper                          | [Create a Buckypaper VM](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/tutorials/buckypaper/create-a-buckypaper-vm)                            |
| Confidential Kubernetes         | Dyneemes                            | [Create clusters](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/tutorials/dyneemes/create-clusters)                                            |
| Data-in-use encrypting database | MongoDB, MariaDB, PostgreSQL, Redis | [Create a database cluster](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/tutorials/data-in-use-encrypting-database/create-a-database-cluster) |
| Application                     | Nextcloud Hub                       | [Create Nextcloud Hub](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/tutorials/applications/create-nextcloud-hub)                              |

Resources run either on enclaive-managed cloud capacity or in your own cloud account via [Bring your own Subscription](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/tutorials/settings/bring-your-own-subscription). Their usage counts against the team's quotas and appears on the team's invoice.<br>
