> 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/datasets.md).

# Datasets

Datasets are a core component of Redivis. They can contain various metadata and documentation, as well as data stored as tables or files.

All datasets have their own persistent URL and are [uploaded](/guides/create-and-manage-datasets/create-and-populate-a-dataset.md) by either a user or an organization. Datasets can be added to [workflows](/reference/workflows.md) to analyze their contents and combined with other datasets across Redivis. Some components of a dataset may not be available to you until you are [granted access](/reference/data-access/access-levels.md). In order to see the existence of a dataset, you must at least have [overview access](/reference/data-access/access-levels.md#overview-access).

You can [create your own datasets](/guides/create-and-manage-datasets/create-and-populate-a-dataset.md) to use in workflows and share with colleagues. They can also be created within any organization that you administer.

<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%2FFO3iEYNF8JEavJelvvoU%2Fredivis.com_workflows_x7kh-5pvd4mbf1_dataSources_f3st-1yxmt4nsf%20(1).png?alt=media&amp;token=e33d9768-d956-49af-ba3d-6b5d46d894b3" alt=""></div>

{% hint style="info" %}
New to Redivis? Learn more in our [Create & manage datasets](/guides/create-and-manage-datasets.md) guide.
{% endhint %}


---

# 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/datasets.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.