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

# Operator Journey

An **Operator** is the highest-privileged role at the DataOS Instance level. Operators create and configure Tenants, attach Data Planes and Compute, and invite users — all through the Instance Admin application.

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

***

## Journey at a glance

{% stepper %}
{% step %}

### Provision Data Plane

After the customer provisions the infrastructure, install the Data Plane.

[Overview](/operate/phase-1-provision-data-plane/overview.md): review the full deployment sequence and prerequisites.

#### Choose your cloud

Use the runbook for your target cloud.

<table data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><strong>AWS</strong></td><td data-object-fit="fill"><a href="/files/v23nCHqS2LJVKiNSEi6o">/files/v23nCHqS2LJVKiNSEi6o</a></td><td><a href="/pages/WShFn1ZNUkzQX7yK4KXA">/pages/WShFn1ZNUkzQX7yK4KXA</a></td></tr><tr><td align="center"><strong>Azure</strong></td><td data-object-fit="fill"><a href="/files/hgr7Fxc1K7YYzzbqg2Sy">/files/hgr7Fxc1K7YYzzbqg2Sy</a></td><td><a href="/pages/rARoSVCcFh9iHzKLyI8e">/pages/rARoSVCcFh9iHzKLyI8e</a></td></tr></tbody></table>

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

{% step %}

### Set up Tenant

After provisioning the Data Plane:

* Create a [Tenant](/operate/core-concepts/tenant.md) in **Instance Admin**.
* Attach the Data Plane and Compute to the Tenant.
* Invite users and assign a Tenant Admin.

[Phase 2 overview](/operate/phase-2-setup-tenant/phase-2-setup-tenant.md): full setup steps for Tenant creation and configuration.

{% hint style="info" %}
See [Roles & Permissions](/operate/governance/roles-and-permissions.md) for role definitions and the capability matrix.
{% endhint %}

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

{% step %}

### Configure Tenant resources

Install the required stacks, connect data sources, and provision Lakehouse if needed.

* [Stacks](/operate/phase-3-configure-tenant-with/stacks.md): install the required Vulcan stacks.
* [Data source access](/operate/phase-3-configure-tenant-with/data-source-access.md): create Secrets first, then create matching Depots for the Tenant.
* [Lakehouse](/operate/phase-3-configure-tenant-with/lakehouse.md): provision managed Iceberg storage for tenant analytics workloads.

{% hint style="success" %}
Phase 3 complete: required stacks are healthy, data source Secrets and Depots are active, and Lakehouse is provisioned if needed.
{% endhint %}
{% endstep %}
{% endstepper %}


---

# 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/operator-journey.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.