> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/user-guides/getting-started/developer-portal/tenant-list.md).
# Tenant List
View and manage your tenants.
The **Tenant List** view of the Emporix Developer Portal is the place where you can see all the tenants assigned to your account or you can create a new one.
## Creating additional tenants
When you create an account on Emporix and verify your email address, you are asked to set up a tenant — your business subscription to Emporix services. This tenant acts as a **production environment** that your customers will interact with directly.
You can create more tenants for different purposes, such as a **staging environment** for testing. This way, you can try out new APIs, get familiar with New features, or verify your assumptions about our system without the risk of breaking the production environment.
{% hint style="warning" %}
Depending on your contract with Emporix, additional tenants may be subject to billing.
{% endhint %}
1. Go to the **Tenant List** view.
2. Choose **Add Tenant**.
3. Provide required details and your preferences and confirm with **Create a tenant**.
Result: When the tenant is created in the system, you receive an email notification. You can start working with your new tenant.
---
# 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://developer.emporix.io/user-guides/getting-started/developer-portal/tenant-list.md?ask=&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.
