> 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/faq/c150/c155/q491.md).

# ¿Puedo añadir campos personalizados al encabezado y pie de página de un informe?

Aunque no admitimos agregar campos personalizados al encabezado y al pie de página, puedes ocultar los campos predeterminados y cambiar las etiquetas de texto para que coincidan con la estructura y el estilo de tu negocio (por ejemplo, puedes cambiar la etiqueta de "Contact" a "Representante de ventas").

## Relacionado&#x20;

* [Artículo: Mostrar/ocultar campos de encabezado en Report and Run: Nube](https://docs.reportandrun.com/manual/es/readme/customization/show-hide-header-fields.md)
* [Artículo: Mostrar/ocultar campos de encabezado en Report and Run: Sin conexión](https://docs.reportandrun.com/manual/es/report-and-run/customization/show-hide-fields.md)
* [Artículo: Cambiar las etiquetas de informe en Report and Run: Offline](https://docs.reportandrun.com/manual/es/report-and-run/customization/change-report-labels.md)
* [Artículo: Personalizar las etiquetas de informe en Report and Run: Cloud](https://docs.reportandrun.com/manual/es/readme/customization/customize-labels.md)
* [Preguntas frecuentes: ¿Cómo creo una nueva plantilla de informe con campos personalizados?](https://docs.reportandrun.com/manual/es/faq/c150/c155/q489.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/faq/c150/c155/q491.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.
