> 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/governance/adminstration/operator.md).
# Operator
After DataOS is created, you tailor the environment to your organization. This page describes the key administrative actions. You need the Operator role to perform them.
### What is an Operator?
An **Operator** is the highest-privileged role in DataOS. It gives unrestricted access at the DataOS Instance level and is required for Instance administration. Instance-level authority does not grant access inside a Tenant. Tenant access is granted separately through Tenant-level roles. This separation lets you centralize platform administration without giving every Instance administrator access to each Tenant.
### Operator responsibilities
As an Operator, you set up and manage DataOS so the platform fits your organization, governance rules, and user needs. The role covers Tenant creation, Tenant configuration, infrastructure association, and initial user onboarding.
### Tenant creation
Tenant creation is one of your primary responsibilities. Create a Tenant for a team, line of business, project, or any unit that needs a distinct operating boundary in DataOS.
When a request for DataOS access comes in, evaluate the team's purpose, data requirements, and administrative needs. Decide whether to create a new Tenant or grant access to an existing one. To create a Tenant, use the CLI or the Instance Admin application. The Instance Admin application is the recommended path.
To create a Tenant in the Instance Admin application:
1. Open the DataOS Instance interface.
2. Select the Instance Admin application from the profile menu.
3. Select **Create new tenant**.
4. Provide the Tenant title.
5. Provide the Tenant description.
You can update the Tenant title and description later, but use stable naming. Frequent changes confuse downstream users and disrupt references and operational workflows.
### Tenant setup
After you create a Tenant, view it in the **All Tenants** section of the Instance Admin application. Start setup by selecting the gear icon labeled **Configure this tenant**. During configuration, connect the Tenant to a Dataplane, then create Compute for that Tenant. A **Dataplane** is the infrastructure layer associated with the Tenant. **Compute** refers to the node pools provisioned in that Dataplane for workload execution.
#### Dataplane connection
In the Dataplane section, select the Dataplane to associate with the Tenant. Add a short description to document the purpose. This step defines where the Tenant's workloads run and sets the infrastructure boundary for the Tenant.
#### Compute creation
After the Dataplane connects successfully, go to the Compute section and select **Create compute**. Provide the relevant node pool selector and infrastructure details. The Compute configuration determines which node pools the Tenant can use, so Tenant execution capacity matches your infrastructure standards. Once Compute is created, the Tenant is ready for user onboarding.
### Tenant invitation
After Tenant creation and setup, invite users to the Tenant with a pre-assigned role. This step turns the configured Tenant into a usable environment. If a user does not show up in search, enter the user's email address and send an invitation directly. The invited user gets an email with a link to accept access. After the user accepts, they receive the Tenant base role and can start working in the Tenant.
### Delegated administration
In smaller operating models, Operators manage Tenants directly. In larger or distributed organizations, delegate Tenant-level administration by assigning the **Tenant Admin** role to a suitable user. A Tenant Admin manages that Tenant's administrative work without holding Instance-level authority. Delegation keeps central control over the DataOS Instance.
### Operational flow
The Operator journey follows a clear sequence:
1. Evaluate the access or environment request.
2. Decide whether to create a new Tenant or use an existing one.
3. Create the Tenant.
4. Connect the Tenant to a Dataplane.
5. Create Compute for the Tenant.
6. Invite users with the appropriate Tenant role.
7. Delegate Tenant administration when needed.
This model gives you a consistent way to structure onboarding, governance, and administrative ownership.
---
# 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/governance/adminstration/operator.md?ask=&goal=
```
`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.