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

# Data Row-Level Security

The **FPT Data Suite** system enables access control not only at the **functional level** (via **RBAC**) but also at the **data level**, ensuring that users only see the information relevant to their **role** and **scope**—even when viewing the same report.

#### Authorization via Data Filters

You can configure **row-level data filtering rules** directly within the report, based on attributes such as:

* **Branch**, **Region**, **Organization**
* **User Roles**
* **User ID** or other **custom attributes**

**Example**:\
A revenue report will automatically show **only data for the Central region** if the user belongs to that region.

Refer: [Role-Based Sercurity](/english/sharing-and-access-management/permission/role-based-security.md)

#### **Authorization by User Group**

Reports can also be configured to display data based on the **User Group** of the viewer. This provides a more granular control mechanism, aligning access with organizational structure and user responsibilities.

Refer: [User Group](/english/sharing-and-access-management/permission/user-group.md)


---

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

```
GET https://docs.datasuite.vn/english/sharing-and-access-management/permission/data-row-level-security.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.