> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/operate/tenant-admin.md).

# Tenant Admin

- [Tenant Admin overview](https://v2.dataos.info/operate/tenant-admin/tenant-admin.md): The role that runs a Tenant day to day: resources, access, governance, and health.
- [Create Compute](https://v2.dataos.info/operate/tenant-admin/create-compute.md): Provision additional Compute (node pools) for Tenant Data Product workloads.
- [Add Depots & Secrets](https://v2.dataos.info/operate/tenant-admin/add-data-sources-and-secrets.md): Connect the Tenant to external systems with Secrets and Depots.
- [Manage access](https://v2.dataos.info/operate/tenant-admin/governance.md): Grant developers access to Compute and data sources, onboard users, and set up the ApplicationUser and runAsUser mechanics.
- [Monitoring](https://v2.dataos.info/operate/tenant-admin/monitoring.md): Watch the Tenant's Compute and Resource health, and how to check it.


---

# 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://v2.dataos.info/operate/tenant-admin.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.