# Create a tenant and its VDC

Give a tenant its share of a site, isolated on the hypervisor.

## The tenant

1. Open **Cloud services › Customers**, fill in **New tenant name** and, if needed, **Billing reference (optional)**, the tenant's reference in your billing tool.
2. Click **Create the tenant**. It takes the Administration level.
3. On its page, under **Portal gestures**, tick what its users may do from the portal: deploy, power, console, snapshots, reconfigure, disks, network, delete, tags. Click **Apply**.

A tenant is always a **new company** in Naoshift, isolated from yours: an existing company cannot become a tenant. An action is only open if it is also open for your company and on the site.

## The VDC, as a draft

On the tenant's page, click **New virtual data center**, choose a ready site, then **Use this site**.

| Field | Good to know |
|---|---|
| **Name**, **Short name** | The name the tenant sees |
| **Allocation model** | Pay as you go. The other models show as "coming later" |
| **Quotas count** | What is allocated, machine powered on or not, or powered-on machines only |
| **Quotas** | vCPU, memory, machines, snapshots, IP addresses. **Empty: unlimited. 0: forbidden** |
| **Catalog sizes only** | The tenant deploys and resizes with your size templates only |
| **Storage tiers** | A storage class, or a tier declared by hand: storage, disk GiB, snapshot GiB, free space to keep |
| **Networks** | Addresses handed out by the portal or by your DHCP, gateway, DNS. On Proxmox VE 9, VLAN or VXLAN |
| **Catalog** | The published items to offer this tenant |

Click **Save the draft**. Nothing is created on the hypervisor before the onboarding.

## The onboarding

On the VDC's page, click **Launch the onboarding**. The VLANs are reserved in the site's registry, then the operation creates, in order:

1. the tenant's **resource pool**;
2. its **networks**;
3. its **native account**, and its rights on its pool, its networks and the catalog, nothing else;
4. a **check** of these rights, made with the tenant's own account.

The VDC then turns **ready**: the tenant can deploy. The operation's page updates itself, step by step.

### The onboarding is refused at launch

The site has no VLAN pool: declare one on the site's page. The message says so before any write.

### The onboarding fails halfway

Naoshift only undoes what **this** onboarding created and marked. An object it cannot attribute with certainty is never touched: the operation waits for your decision, with the list of what remains.

### A tenant needs more room

Open the VDC's page, then **Edit limits**. A limit set below what is already used is saved and flagged: nothing is stopped, only the next consumption is refused.
