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

# Manage access

As an Operator, you manage Instance-level access and keep it auditable. Your responsibility is to assign Tenant ownership, keep role assignments consistent, and review high-privilege access.

## Assign Tenant ownership

Every Tenant needs an accountable **Tenant Admin**. To keep ownership clear:

* Assign a Tenant Admin when the Tenant is created or handed over.
* Confirm the Tenant Admin can sign in and operate the Tenant.
* Ensure every Tenant has an accountable owner.
* Review or retire Tenants that no longer have a clear owner.

## Review high-privilege access

Operator access and Tenant Admin access are high-privilege. Review them regularly and keep the reason for access clear.

As an Operator:

* review who holds Operator access;
* review who holds Tenant Admin access across Tenants;
* confirm high-privilege access still has a valid owner and purpose;
* remove or update access when responsibilities change.

## Review delegated identities

ApplicationUser and runAsUser access allows a resource to act through another identity. Review these grants to:

* Confirm the access is still required.
* Verify it is approved and has an accountable owner.
* Remove or update grants that are no longer needed.

For the full model and audit requirements, see [Access control](/operate/v1/access-model.md).

## Manage Tenant lifecycle

* Create Tenants as new teams, environments, or domains require them.
* Review Tenants regularly and retire those that are no longer in use or required.


---

# 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/governance.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.