> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/guides/administer-an-organization/grant-access-to-data.md).
# Grant access to data
One strength of Redivis is that researchers can apply for and gain access to data on the same page they discovered it. Moreover, all access applications are tracked, both for administrators' reference and to provide transparency and timely notifications to researchers.
Responding to access requests in a timely manner creates a great environment for researchers and takes full advantage of these automatic systems.
## 1. Configure notifications
You can configure multiple email addresses to receive a notification when a request for access is made. The frequency of these notifications can be adjusted here as well. If your organization is small and isn't getting access requests every day, it's important have at least one administrator receiving emails so you know when to respond to a request.
*Learn more in the* [*Settings*](/reference/organizations/settings.md#additional-settings) *reference section.*
## 2. Approve membership requests
Users must be approved as members of your organization before any other access requests can be approved.
When a membership request is pending you will see an Alert **(!)** on the Members tab of your workspace. Select any member with an alert to see their pending submission awaiting approval.
You have the option to Approve or Reject Pending members when you select their page. Here you can see the authentication information they submitted when requesting to be a member. It is important to verify that this person has a genuine email that seems consistent with who they say they are.
## 3. Approve requirement submissions
As users ask for approval you will receive an alert **(!)** in the administrator panel where your attention is needed.
Member requirements and export restriction exceptions will appear on the **Member** tab.
Project requirements will appear on the **Projects** tab.
Direct access requests will appear on the **Datasets** tab.
When all of the pending requests are resolved, the alert will disappear.
For each request you will have the option to approve or reject the submission. You can always come in later to revoke the approval if needed. You may also see that the member has submitted updates to their existing approval. In that case, the approval is still valid while updates are pending unless it is otherwise revoked or expired.
*Learn more in the* [*Approving access*](/reference/data-access/approving-access.md) *reference section.*
## 4. Leave comments for clarity
Both administrators and members have the option to leave a comment on any requirement submission. This will trigger an alert for administrators and a notification for members.
When you are rejecting or revoking a requirement submission, it's best to leave a comment to let the member know what they did wrong or what they still need to do to gain access.
## 5. Audit access
It's often a good idea to double check which researchers have access to your datasets.
In order to audit a particular member's access to your organization's datasets, select that member, and navigate to the **Access overview** tab. This will list all of your organization's datasets and the member's corresponding access to each.
In order to audit all members that have access to a particular dataset, select **Filter** to filter members by their access to and usage of your organization's datasets.
## Next steps
#### Expand your reach
If you are part of a larger institution, [contact us](https://redivis.com/contact) about getting an institution-wide Redivis page to help users discover your organizations and datasets.
---
# 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.redivis.com/guides/administer-an-organization/grant-access-to-data.md?ask=&goal=
```
`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.