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

# How do I customize the header information and logo in my reports?

## Logos and Banners

You can set a logo or banner within your work space and it will appear in your published reports. (See how to do it in the [offline app](/manual/report-and-run/branding/set-a-company-logo-1.md) or the [cloud app](/manual/readme/branding/set-a-company-logo.md).) 

If you want reports to have unique logos, you can [set multiple logos on the folder level](/manual/readme/branding/set-multiple-logos.md) in Report and Run: Cloud. In Report and Run: Offline, you can create different work spaces and [set a unique logo](/manual/report-and-run/branding/set-a-company-logo-1.md) in each space. 

## Hide/Show Header Information

You can use the report properties to adjust [what information appears in published report headers](/manual/faq/c150/c155/q486.md). For example, you can choose to hide the company name or contact email. 

## Related 

* [Article: Add a banner in Report and Run: Cloud](/manual/readme/branding/add-a-banner-to-a-report.md)
* [Article: Add a banner in Report and Run: Integrate](/manual/report-and-run-integrate/branding/add-a-banner-to-a-report.md)
* [Article: Add a banner in Report and Run: Offline](/manual/report-and-run/branding/set-a-banner.md)
* [Article: Show/hide header fields in Report and Run: Cloud](/manual/readme/customization/show-hide-header-fields.md)
* [Article: Show/hide header fields in Report and Run: Offline](/manual/report-and-run/customization/show-hide-fields.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/q487.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.