> 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/v1/dataos-operator/operator.md).

# Overview

The Operator manages the DataOS Instance and prepare and setup the Tenants for use in the Instance Admin application.. This includes provisioning the Instance, setting up Tenants and their resources, and handing them over to Tenant Admins.

Before you create anything, DataOS must be connected to your identity provider so users can sign in with their enterprise identity. This is a one-time setup. See Authentication and authorization.

{% hint style="info" %}
Access to Tenant and it's Tenant resources is managed separately through Tenant roles.
{% endhint %}

Use the phases below as your checklist. Each phase links to the detailed runbook.

## Provision Data Plane

After the customer provisions the cloud infrastructure, install the Data Plane: the execution layer that runs in the customer cloud.

* [AWS](/operate/v1/dataos-operator/provision-data-plane/aws.md)
* [Azure](/operate/v1/dataos-operator/provision-data-plane/azure.md)

{% hint style="success" %}
**Phase 1 complete:** the Data Plane is provisioned.
{% endhint %}

## Set up Tenant

Set up and configure Tenants to organize workloads, connect resources, and manage access:

* [Plan the Tenant model](/operate/v1/dataos-operator/design-tenants.md): choose the slicing model, and Tenant vs. separate Instance.
* [Creat Tenant](/operate/v1/dataos-operator/design-tenants/create-tenants.md#1-create-the-tenant) in **Instance Admin**.
* [Attach the Data Plane and Compute](/operate/v1/dataos-operator/design-tenants/create-tenants.md#2-attach-the-data-plane-and-compute) to the Tenant.

See [Roles & Permissions](/operate/v1/access-model.md) for role definitions and the capability matrix.

{% hint style="success" %}
**Phase 2 complete:** the Tenant is created, the Data Plane and Compute are attached, and users have roles assigned.
{% endhint %}

## Configure Tenant resources

Install the required stacks, connect data sources to support Data Product workloads:

* [Stacks](/operate/v1/dataos-operator/design-tenants/create-tenants.md#3-install-the-required-stacks): install the Vulcan engine Stacks and Data Product MCP.
* [Data source access](/operate/v1/tenant-admin/add-data-sources-and-secrets.md): create Secrets and the corresponding Depots for the Tenant.
* [Lakehouse(optional)](/operate/v1/data-admin/manage-lakehouse.md): provision managed Iceberg storage.

{% hint style="success" %}
**Phase 3 complete:** the required stacks are healthy, at least one data source connection is active, and the Lakehouse is provisioned if needed.
{% endhint %}

## Hand over Tenant

Hand the configured Tenant to the person who will run it day to day.

* [Invite a Tenant Admin](/operate/v1/dataos-operator/design-tenants/create-tenants.md#invite-a-tenant-admin) once the readiness checklist passes.

A Tenant is ready to hand over when:

* The Data Plane and at least one Compute are attached and active.
* The required Vulcan stacks are healthy.
* At least one data source Secret and Depot are active.
* A sanity Data Product deploys and runs without errors.

{% hint style="success" %}
**Phase 4 complete:** the Tenant Admin owns a deployment-ready Tenant.
{% endhint %}

## Manage access

Once Tenants are handed over, your ongoing scope is the Instance and the planes everything depends on:

[Manage access](/operate/v1/dataos-operator/governance.md): assign Tenant Admins, keep Tenant role design consistent, and audit access.

## Monitor Instance

[Monitoring](/operate/v1/dataos-operator/monitoring.md): Instance and Data Plane health.

## Where to start ? <a href="#where-to-start" id="where-to-start"></a>

* [Set up Access control](/operate/v1/access-control.md): Configure authentication and access control for the DataOS.
* [Provision Data Plane:](#provision-data-plane) Set up the Data Plane required to run workloads.
* [Plan Tenant model](/operate/v1/dataos-operator/design-tenants.md): If the Dataplane is already provisioned, skip to this step to create and configure Tenants.


---

# 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 dynamically by asking a question.

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

```
GET https://v2.dataos.info/operate/v1/dataos-operator/operator.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.