> 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/readme.md). # Introduction Operate explains how DataOS responsibilities are divided across roles, from Instance setup and Tenant administration to data governance, Data Product ownership, and governed consumption. These responsibilities are layered across the Instance, Tenant, and Resource levels. The Instance provides the central management layer, while Data Planes run workloads and data operations. ## Find your role

Role	What you run and maintain
DataOS Operator	Provision the Data Plane, create and configure Tenants, set up authentication, and invite Tenant Admins
Tenant Admin	Compute, data sources, and Stacks; grant access; and keep the Tenant healthy
Data Admin	Create and govern Lakehouse namespaces, schemas, tables, and views
Data Product Developer	Confirm readiness, deploy and promote, operate live products, and author access policies
Data Product Consumer	Consume Data Products within enforced governance, assess trust, and raise issues

## Shared foundations


Access control Control who can access DataOS and what they can do. Access is denied by default, and roles and permissions grant only the required access.	/pages/FNrDcX3LUrYcXfpSBgHo
Observability Monitor Instance, Data Plane, and Data Product health. Each role focuses on the signals and actions for the services it owns.	/pages/gUEkOQypIDb2Ij1cClUY

## Where to start New to the DataOS? Read [Architecture](/operate/architecture.md) Setting up a Instance from scratch begins with the [DataOS Operator](/operate/dataos-operator/operator.md). --- # 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/readme.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.