> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-docs-es/product-guides/explorador-de-datos.md).

# Explorador de Datos

Gestiona la data de tus fuentes conectadas en el Explorador de Datos de Dapta: filtra, ordena, asigna permisos, edita registros y genera reportes.

El Explorador de Datos te permite gestionar la data de las fuentes de datos que has conectado.

Con el Explorador de Datos puedes crear tablas personalizadas con filtros, ordenamiento de columnas, permisos, reportes y más.

Algunas de las funcionalidades del Explorador de Datos:

* Consulta toda tu data con filtros
* Revisa quién cambió tu data en nuestro registro de actividad
* Asigna permisos de acceso a usuarios
* Crea nuevos registros
* Edita registros existentes
* Genera reportes
* Recibe notificaciones cuando se modifica la data


---

# 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.dapta.ai/dapta-docs-es/product-guides/explorador-de-datos.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.