> 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/concepts-to-take-into-account/data-policies.md).

# Data Policies

One of the key points to **filter the data to be displayed dynamically for each end user** is the correct configuration of the Data Policies. These are filters that are applied to different users and/or groups of users, in sensitive data sets, or in which it is necessary to filter.

It is typical for your application to have a company code, a profile code, a user code, etc. that are also in some database field, which allows **each user to be shown "their data"**. For example, a multi-tenant B2B application, with companies and users associated with said companies. In your application's database you can have a "companies" table where there is a "company\_id" field. If the data usage profile (see examples in the Users section) is that all users of the same company access the same information, a data policy must be configured for each basic user, who will be associated with one of the companies in your application, and precisely, the filter to configure would be "company\_id" = the code of the company associated with the user who is accessing your application.

<figure><img src="/files/UBX5nqf7hJSj6Crih34W" alt=""><figcaption><p>A Data Policy has a name, is associated with users/groups and applies at least one filter</p></figcaption></figure>
