> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/es/videos/offline-videos/b0dsiseleqi.md).

# Cómo mostrar y ocultar campos

Este vídeo explica cómo ocultar los campos predeterminados que no quieres que aparezcan en tus informes, como la fecha en que se creó una imagen. También explica cómo volver a mostrar los campos ocultos.

{% embed url="<https://www.youtube.com/embed/B0DsISELeqI>" %}

## Relacionado

* [Artículo: Cómo mostrar y ocultar campos en Report and Run: sin conexión](https://docs.reportandrun.com/manual/es/report-and-run/customization/show-hide-fields.md)
* [Preguntas frecuentes: ¿Cómo elimino u oculto las marcas de fecha y hora que aparecen en los informes?](https://docs.reportandrun.com/manual/es/faq/c150/c155/q484.md)
* [Video: Cómo configurar los datos de contacto](https://docs.reportandrun.com/manual/es/videos/offline-videos/4d-4xp9qwgc.md)
* [Artículo: Cómo cambiar las etiquetas del informe](https://docs.reportandrun.com/manual/es/report-and-run/customization/change-report-labels.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.reportandrun.com/manual/es/videos/offline-videos/b0dsiseleqi.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.
