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

# Can I hide information from the header of the PDF?

## Report and Run: Cloud and Integrate

In the cloud version of the app, you can [hide header fields](/manual/readme/customization/show-hide-header-fields.md) in the web portal and those settings will apply to the mobile app. 

* Go to the report properties and scroll down to the *Show and Hide* section. 
* You will see several header properties that you can show or hide (e.g. *Company*, *Contact Email*). 
* Items you want to appear in report headers should be marked as "true" and items you want to hide should be marked as "false."

## Report and Run: Offline

In the offline version, you can [hide header fields](/manual/report-and-run/customization/show-hide-fields.md) in the report settings before generating a report. 

* Go to the report settings and open the *Show/Hide Header* section.
* Tap an item and mark it as "true" to show it in the report header or "false" to hide it.

## Related 

* [Article: Show/hide header fields in Report and Run: Cloud](/manual/readme/customization/show-hide-header-fields.md)
* [Article: Show/hide functionality in Report and Run: Cloud](/manual/readme/customization/show-hide-functionality.md)
* [Article: Show/hide header fields in Report and Run: Offline](/manual/report-and-run/customization/show-hide-fields.md)
* [FAQ: Can I add custom fields to the header and footer of a report?](/manual/faq/c150/c155/q491.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/faq/c150/c155/q486.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.