> For the complete documentation index, see [llms.txt](https://fpphelp.fesnow.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fpphelp.fesnow.org/portal-interface/getting-to-know-your-dashboard/page-header.md).

# Page Header

The Page Header is consistent across all parts of the FES Partner Portal. As the name implies, it's the section across the top of the page. It's used to provide consistent navigation options, school branding options, and easy access to the help documentation.

![Page Header](/files/-MfoxxZlF9QUOWBvaPqv)

Let's break down the Page Header to better understand its parts. Starting with the left side of the Page Header, you see the three blue lines, also known as the "hamburger menu" which is the main menu for the Portal.

![Page Header - Left Side](/files/-Mfoy096pXgudiy4X685)

To the right of the menu icon is a place for school branding. During your schools' setup, our administrators will link your school logo and school name to your account.  In this example you see the FutureEd Solutions logo and &#x20;

![Page Header - Right Side](/files/-Mfoy3jRpkCUjWOXPgoZ)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fpphelp.fesnow.org/portal-interface/getting-to-know-your-dashboard/page-header.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
