> 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/data-admin/access-control.md).

# Access control on Lakehouse data

The Lakehouse holds shared analytics data, so who can read and write it is a governance decision you own. The underlying mechanics are the same deny-by-default model as everywhere else (see the [Access control](/operate/v1/access-model.md)); this page is how they apply to Lakehouse data.

## What you govern

* **Read and write access** to namespaces, schemas, and tables: grant `Can Use` on the Lakehouse Depot, and structure namespaces so access maps cleanly to teams and products.
* **Column and row controls** where data is sensitive: masking and row-level filtering so different consumers see different slices of the same table. When products expose Lakehouse data through a semantic layer, those controls are authored as policies on the product (see [Governance](https://v2.dataos.info/build/productize/governance) in the Build guide and [Manage Data Product access](/operate/v1/data-developer/governance.md) in the Developer section); at the Lakehouse layer you control the underlying table access.
* **Service identities.** Products and workloads that read or write the Lakehouse should do so under an ApplicationUser, not a person's identity. Coordinate the `runAsUser` grants with the [Tenant Admin](/operate/v1/tenant-admin/governance.md).

## Operating practices

* **Grant to roles, not individuals**, for standard read access; reserve individual grants for exceptions and review them.
* **Separate read from write.** Most consumers and products read; restrict write to the pipelines and owners that produce the data.
* **Align access with namespace structure.** If access keeps needing per-table exceptions, the namespace layout probably needs rethinking.
* **Audit periodically.** The grant history is the audit trail; review who can write to production namespaces.

For the full access model and audit requirements, see [Access control](/operate/v1/access-model.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/v1/data-admin/access-control.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.