> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/private-cloud-director/identity-and-multi-tenancy/tenant.md).

# Tenants & Region

## Tenant

`Tenants` (also called Projects in API) represent the base unit of `ownership` in <code class="expression">space.vars.product\_name</code>, in that all resources in <code class="expression">space.vars.product\_name</code> are owned by a specific tenant. A tenant itself must be owned by a specific domain, and hence all tenant names are **not** globally unique, but unique to their domain. If the domain for a tenant is not specified during creation, then it is added to the `default` domain.

## Region

A region generally represents a physical location, such as a data center, where your compute resources are physically located.

Regions are deployed during your Platform9 onboarding and initial setup. To add more Regions to your cloud, connect with your Platform9 Solutions Engineer or Support contact.

### Infra Region

When you create a multi-region deployment of <code class="expression">space.vars.product\_name</code>, an internal or systems region named `Infra` is provisioned behind the scenes and used to host the <code class="expression">space.vars.product\_name</code> identity service (Keystone). This region will not be visible or accessible when using <code class="expression">space.vars.product\_name</code> UI. However, you will see this region in a multi-region deployment when using OpenStack CLI.

When you are deploying a self-hosted installation of <code class="expression">space.vars.product\_name</code>, the internal `Infra` region is always required.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform9.com/private-cloud-director/identity-and-multi-tenancy/tenant.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.