# RLS in Table reports

#### Understanding Row Level Security (RLS)

RLS is a powerful feature that allows you to restrict data visibility in reports based on user roles or attributes. This ensures that users only see the data relevant to them.

Sprinkle supports RLS for Table, SQL, and Model-based reports.

### To apply RLS to a table report:

1. **Create an RLS Attribute**: Define an RLS attribute on the RLS page, mapping users to specific values. Refer to the detailed RLS documentation for more information.
2. **Open the Report**: Access the table report where you want to apply RLS.
3. **Navigate to RLS modal**: Navigate to the report's "More options" menu and select "Row Level Security."
4. **Map RLS Attribute**: In the RLS modal, choose the created RLS attribute and the corresponding column in your data from their respective dropdowns.
5. **Apply RLS**: Click the "Link" button to apply the RLS to the selected column.

#### Example:

* If you want to restrict sales data visibility to managers of respective countries, create an RLS attribute mapping managers to their countries. 
* Then, apply this attribute to the "Country" column in your sales report.

{% hint style="success" %}
**Key Benefit:** RLS applied to a column in a table report is automatically applied to all visualizations using that column in the same report, even if it's in a different tab of the report.
{% endhint %}

<br>


---

# Agent Instructions: 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:

```
GET https://docs.sprinkledata.com/product/analysing-your-data/reports/build-using-tables/advanced-features/rls-in-table-reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.