> 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-masthead-photo-on-a-non-procedure-page.md).

# Updating a Masthead Photo on a Non-Procedure Page

{% hint style="warning" %}
Have the masthead image ready. Images can be in .png or .jpg format. We recommend an image file 2000 pixels wide and 1500 pixels tall.
{% endhint %}

The instructions below apply if you're using DoctorLogic Design version 3.0.

1. On the Employee Admin home page, click **Media** and select **Media Library**.
2. Click **Drop files here to upload**.
3. Select the image you'd like to use and click **Open**.
4. Locate the image you just uploaded to the media library (it should be the first one you see on the right side of the screen. 
5. Enter **MH-\[page name]** in the label field (e.g. enter **MH-Contact Us**, if this is a contact page).
6. Click **Components** from the navigation bar at the top of the screen and select **Masthead**.
7. Locate the page you'd like to edit and click the yellow pencil icon.
8. Click the dropdown arrow at the **MediaId** field and locate the image you just uploaded.
   1.  For example, using the example from the previous steps, the **MediaId** name is **MH-Contact Us**.
9. Click **Media**.
10. Click **Drop files here to upload** and select the same masthead image you previously uploaded.


---

# 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-masthead-photo-on-a-non-procedure-page.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.