> 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/2025.4/multi-tenancy/domains.md).

# Domains

Domains in <code class="expression">space.vars.product\_name</code> enable you to create multiple sub-organizations within your current organization.

A large company may have multiple sub-organizations, such as multiple business units, each requiring to operate in an isolated manner, with it's own isolated infrastructure and users. Domains enable this use case.

A **Domain** is a logical grouping of isolated infrastructure and users. Each Domain has it's own infrastructure of physical servers, networks, storage etc that is not shared with other Domains. It also has one or more tenants within it, that are completely owned by that Domain. Tenants are not shared across Domains.

A default deployment of <code class="expression">space.vars.product\_name</code> comes with a single domain called the `default` domain. This is the domain you will see selected when you log into <code class="expression">space.vars.product\_name</code> UI. If you need multiple domains enabled, work with your Solutions Architect or Support contact to request additional domains to be enabled.


---

# 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/2025.4/multi-tenancy/domains.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.