> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/data-management/explorations/row-level-access.md).

# Row Level Access

Row Level Access (RLA) allows Builders to control which rows of data each user can access, based on specific attributes configured at the user level. This ensures that users only see data relevant to their role, location, or other designated criteria. The feature enhances data security and personalization by filtering data dynamically per user.

Row Level Access is configured at the "Exploration" level. RLA binds a specific dimension within an [Exploration](/data-management/explorations.md) (e.g., "Country") to a [User Attribute](/user-management/user-attributes.md), allowing for granular control over the data a user can see in that context.

To implement RLA, you bind a dimension in the [Exploration](/data-management/explorations.md) to a [User Attribute](/user-management/user-attributes.md). A dimension is a field in the dataset, such as "Country," "Department," or "Team." The [User Attribute](/user-management/user-attributes.md) is configured at the user level and determines what value the user has for that dimension. For example, if the "Country" dimension is bound to a User Attribute "user\_country," users will only see rows where the "Country" matches their "user\_country" value.

Example:

* **Dimension:** Country
* **User Attribute:** user\_country
* **Outcome:** A user with "user\_country = USA" will only see rows where "Country = USA."

<figure><img src="/files/Ro5PY5StoRyYrVNZAWBN" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/OaM13NaZZh1op2jEyFgY" alt=""><figcaption></figcaption></figure>

### **FAQs**

#### **Q1: How do I troubleshoot RLA configuration issues?**

Ensure that the correct [User Attributes](/user-management/user-attributes.md) are assigned to users and that the dimension in the Exploration is properly bound to the User Attribute. Check that users have the necessary attribute values set. You can use [User Impersonation](/team/impersonate.md) to validate the setup.

#### **Q2: What happens if a user doesn’t have a User Attribute set?**

#### If a User Attribute is not set, the user will see no data for security reasons. So it's important to properly configure the [User Attribute](/user-management/user-attributes.md) of each users.

#### **Q3: I want some users to see all available data**

The `*` value can be used in [User Attribute](/user-management/user-attributes.md) value to indicate that the user can see everything.


---

# 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.whaly.io/data-management/explorations/row-level-access.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.