> For the complete documentation index, see [llms.txt](https://docs.verbdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verbdata.com/models/building-a-model/row-level-security.md).

# Row-Level Security

Row-level security determines the data from a model that end-users are allowed to access through collections (dashboards, etc). The rules can be set on one or more tables in a model and only data that satisfies all rules will be accessible to end-users.

Row-level security rules are not required on every table in a model. Where relationship paths are drawn, row-level security rules will apply from the referenced table across the model to all related tables.

Row-Level security configurations are set independently on the Static and Active Authentication methods and they are unique per model and environment.

## Configuring Row-Level Security 

To configure row-level security on a table, open the table menu from the canvas or left panel. The Row-level Security configuration panel will open where you may set the rules for the selected table.

To create the rules you will use the Boolean logic format and three different value type options to configure the rule(s). 

#### Column -

#### User Values 

User Values are configured in the Authentication section of Environment Settings. These values are the properties provided through the SDK, Data Access API Key, and iFrame Key that identify the end-user. 

#### Filter Value -

![](/files/bgYXmZiPotS8oMCw7e0m)

![](/files/Jh9bqRBTEegiyIt5L0mY)


---

# 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.verbdata.com/models/building-a-model/row-level-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.