> For the complete documentation index, see [llms.txt](https://docs.finout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finout.io/settings/role-based-access-control-rbac/data-access-control.md).
# Data Access Control
Within the RBAC framework, Data Access Control determines the specific data sets visible to users.
By applying filters to a group, you ensure its members access only filtered data. Please note that users can be members of more than one [group](/settings/role-based-access-control-rbac/groups.md). This component ensures users engage only with the data relevant to their roles and responsibilities, avoiding unnecessary data and information visibility.
In Finout, you have the flexibility to create customized user groups, tailoring data access to fit specific requirements. For example, creating a group solely for the R\&D team, ensuring access to only those datasets that are related to their work.
{% hint style="warning" %}
**Important**: Data Access is configured to be 'deactivated' by default. To enable Data access for your account, please contact our support team at .
{% endhint %}
### Enabling data access control
Data Access Control must be enabled in the organization within Finout to start creating user groups based on specific data filters. This can be done only by a user with an Admin role who has permission to manage groups.
1. Log in to Finout as an **Admin** user.
2. Navigate to **Settings**.
3. Select the **Groups** tab.
4. Select or deselect **Allow data access in my organization**.
5. Click **Continue**. Once enabled, you can start creating groups and applying filters to them. See [How to Edit Data Access](/settings/role-based-access-control-rbac/groups/edit-group-data-access.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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.finout.io/settings/role-based-access-control-rbac/data-access-control.md?ask=&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.