> 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/groups/edit-group-data-access.md).
# Edit Group Data Access
You can tailor data so your group can be seen by implementing filters.
1. Log in to Finout as an **Admin** user.
2. Navigate to **Settings**.
3. Select the **Groups** tab.
4. Click on (⋮) next to the desired group and select **Edit Group**.\
The **Group Settings** appear.
5. In the **Data Access** tab, activate the **Data access status**. This action will enable data access for this group.
6. Customize the group data by choosing the cost filter options for the group:
* Select the desired **Cost center**, for example, AWS.
* Select the relevant **key**, for example, Regions.
* Select the relevant **operator**, for example, Contains.
* Specify the necessary **Values**.
7. (Optional) Click **Add new filter** if you wish to add additional filter criteria.
8. Click **Save** to apply the changes.
---
# 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/groups/edit-group-data-access.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.
