> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/users/data-restriction.md).

# Data Restriction

Users-rail entry. The comparison of restriction vs dynamic user filters vs per-list disable is the canonical data page: [Data restriction vs filters](https://docs.notionapps.com/databases/data-restriction-and-filters).

## What this is

Personalization: rows on a database match the logged-in user. Set the match fields here, then read the data page for disable-on-screen, nested lists, and in-app filters.

## Build it

1. Users → Data restriction.
2. Map user fields to row fields.
3. Publish. View as a client.
4. For staff exceptions and filter types, open the [data page](https://docs.notionapps.com/databases/data-restriction-and-filters).

## Disable data restriction on selected screens components

On a screen or component, turn personalization off when that surface should show all rows the user is otherwise allowed to see. Nested-list exceptions and filter types live on [Data restriction vs filters](https://docs.notionapps.com/databases/data-restriction-and-filters).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.notionapps.com/users/data-restriction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.