> 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/reference/data-access/configuring-access.md).

# Configuring access

Before [releasing a dataset](https://docs.redivis.com/guides/create-and-manage-datasets/create-and-populate-a-dataset.md#5-release-the-dataset), it is important to ensure that access to the dataset is appropriately configured. By default, new datasets are public at the [overview access level](https://docs.redivis.com/reference/data-access/access-levels.md), and must be explicitly shared with others in order for them to get metadata or data access.

In order to change a dataset's access configuration, select **Configure access** on the dataset editor page.

<div data-with-frame="true"><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2Fa7I5ZAZGHiOBoZ8RFuWJ%2Fredivis.com_projects_hgy3-2zw1x6tab%20(4).png?alt=media&amp;token=c9d51cc9-c98f-4aab-a846-4eb437c1326c" alt=""></div>

## Access concepts

For every [access level](https://docs.redivis.com/reference/data-access/access-levels.md#levels), you may use one of three paradigms to control access. Different levels can be controlled by different paradigms. Ror example, you may want anyone to be able to see overview access, specific people to have metadata access, and only the subset of those specific people who have completed certain requirements to have data access.

### 1. Public

If a dataset is public at a particular access level, anyone on the internet can access the dataset at that level (once it's released).

### 2. All members

For organization datasets, administrators may specify that only organization members may access the dataset at that level.

### 3. Direct access

Direct access allows the data owner to specify the individual users who can access the dataset at that level.

### 4. Requirements

Available only to datasets owned by an organization. Users must complete and be approved for all requirements for an access level in order to gain access.

*Learn more in the*[ *requirements reference*](https://docs.redivis.com/reference/organizations/requirements.md)

<div data-with-frame="true"><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2FyiP0rVwf6XSdpj3NUeS1%2Fredivis.com_Demo_admin_datasets_7br5-41440fjzk_v%3D1.1%26access.png?alt=media&amp;token=0ffca1c0-26e7-43cf-9ddf-731e8c27db40" alt=""></div>

## Permission groups

Organizations have the option to codify their access configurations in permission groups, which can then be applied across datasets.

*Learn more in the* [*permission groups reference*](https://docs.redivis.com/reference/organizations/permission-groups.md)

## Unpublished datasets

When you first create a dataset within an organization, it is unpublished. Unpublished datasets can only be viewed by organization administrators and assigned [dataset editors](https://docs.redivis.com/reference/data-access/access-levels.md#editors). Once a dataset is published, it can be "unpublished" at any time to restrict access to administrators only, locking down the dataset without having to modify its configuration.

## Usage rules

Organizations can also configure various usage rules on a dataset, such as to limit exports to specific compute environments.

*Learn more in the* [*usage rules reference*](https://docs.redivis.com/reference/data-access/usage-rules.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.redivis.com/reference/data-access/configuring-access.md?ask=<question>&goal=<user_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.
