> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/agency-permissions/updating-a-homepage-photo-banner.md).

# Updating a Homepage Photo Banner

{% hint style="info" %}
Before following the instructions below you'll need to have your image resized and ready to upload.
{% endhint %}

1. On the Employee Admin page, click on Home & Master and select Rotate/Banner.
2. Click the yellow pencil icon to open the Edit page.
3. Click **Drop files here to upload**.
4. Select the image you'd like to use for the homepage banner and click **Open**.
5. Optional: If you have rotating images in your banner, repeat steps 2 - 5 to update each images you'd like to update.


---

# 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://help.doctorlogic.com/docs/agency-permissions/updating-a-homepage-photo-banner.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.