> For the complete documentation index, see [llms.txt](https://docs.biuwer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.biuwer.com/integration-guide/how-do-i-integrate-biuwer-into-my-application/data-access-security.md).

# Data access security

When asked how to configure data access security?, once the user can access content, it is necessary to know **how to specify what data that content will be able to display**.

In Biuwer, this configuration is done using the **Data Policies**, present in the [**Data Sets**](/managing-data/datasets.md). In a very summary way, it is about specifying to the users and/or groups of users, the filters that limit the data displayed in the content.

In a multi-tenant application, it is common to have shared data entities for different clients and it is **necessary to filter the data for each client to ensure that each user has access only to their data**. This aspect is very important, given the seriousness of sharing data that does not correspond to an end user.

The configuration of Data Policies can also be done using the Biuwer interface, when the registration of a client and its end users in the service does not require it to be in real time and there is not such a volume that it is very tedious. In other words, manually configuring Data Policies makes sense in the Biuwer interface itself for integrations that have up to a few hundred users, and their addition/ modification/ deletion does not need to be done in real time.


---

# 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://docs.biuwer.com/integration-guide/how-do-i-integrate-biuwer-into-my-application/data-access-security.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.
