# Step 2: Create a Tenant

Now that the [Infrastructure and Plan](/docs/automation-platform/overview-1/quick-start/step-1-infrastructure.md) exist and a Kubernetes GKE Cluster has been enabled, create one or more Tenants that use the configuration DuploCloud created.

[Tenants ](/docs/automation-platform/application-focused-interface-duplocloud-architecture/tenant.md)in DuploCloud are similar to projects or workspaces and have a subordinate relationship to the Infrastructure. Think of the Infrastructure as a virtual "house" (cloud), with Tenants conceptually "residing" in the Infrastructure performing specific workloads that you define. As Infrastructure is an abstraction of a Virtual Private Cloud, Tenants abstract the segregation created by a [Kubernetes Namespace](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/), although Kubernetes Namespaces are only one component that Tenants can contain.

*Estimated time to complete Step 2: 10 minutes.*

## Tenant use cases

DuploCloud customers often create at least two Tenants for their production and non-production cloud environments (Infrastructures).

For example:

* Production Infrastructure
  * Pre-production Tenant - for preparing or reviewing production code
  * Production Tenant - for deploying tested code
* Non-production Infrastructure
  * Development Tenant - for writing and reviewing code
  * Quality Assurance Tenant - for automated testing

In larger organizations, some customers create Tenants based on application environments, such as creating one Tenant for Data Science applications and another Tenant for web applications, and so on.

Tenants are sometimes created to isolate a single customer workload, allowing more granular performance monitoring, scaling flexibility, or tighter security. This is referred to as a *single-Tenant* setup.

## Prerequisites

Before creating a Tenant, verify that you accomplished the tasks in the previous tutorial steps. Using the DuploCloud Portal, confirm that:

* An [Infrastructure and Plan](/docs/automation-platform/overview-1/quick-start/step-1-infrastructure.md) exist, both with the name you created.
* The Infrastructure has [Kubernetes (GKE) **Enabled**](/docs/automation-platform/overview-1/quick-start/step-1-infrastructure.md)**.**

## Creating a Tenant

Create a Tenant for your Infrastructure and Plan:

1. In the DuploCloud Portal, navigate to **Administrator** -> **Tenants**.
2. Click **Add**. The **Create a Tenant** pane displays.

<div align="left"><figure><img src="/files/38KUs5kZAnbWgmWTEC9h" alt=""><figcaption><p>The <strong>Create a Tenant</strong> pane</p></figcaption></figure></div>

3. Enter a unique name for your Tenant in the **Name** field. Choose unique names that are not substrings of one another, for example, if you have a Tenant named `dev`, you cannot create another named `dev2`. We recommend using distinct numerical suffixes like `dev01` and `dev02`.
4. Select the **Plan** that you created in the previous step.
5. Click **Create**.

{% hint style="info" %}
It may take 1-2 minutes for the Tenant to be set up. While the Tenant is setting up, a temporary fault may show up under **Administrator** -> **Faults**. This fault can be ignored, as it should clear within the first 2 minutes.
{% endhint %}

## Checking your work

From the DuploCloud portal, navigate to **Administrator** -> **Tenants**, and verify that a Tenant exists with the name and Plan you created.

<figure><img src="/files/KfAOBtNJEKk0gnd89tmG" alt=""><figcaption><p>The <strong>Tenants</strong> page showing the Dev01 Tenant</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.duplocloud.com/docs/automation-platform/overview-1/quick-start/step-2-tenant.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.