> For the complete documentation index, see [llms.txt](https://help.brickspacelab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brickspacelab.com/slab/getting-started/global-settings/header-settings.md).

# Header

Header settings in **Theme settings > Header** control how the header behaves while customers scroll and whether top sections can render under the header when overlap is enabled at the theme and section level.

## How to change theme header

{% stepper %}
{% step %}

#### Choose header position

* Open **Theme settings > Header**.
* Under **Position**, choose **Sticky**, **Standard**, or **Dynamic**.
* Preview desktop and mobile before changing overlap.
  {% endstep %}

{% step %}

#### Configure overlap

* Turn on **Enable header overlap** only when top sections are designed for content under the header.
* Set **Desktop overlap** and **Mobile overlap** when overlap is enabled.
  {% endstep %}

{% step %}

#### Enable overlap on sections

* Open each section that should sit under the header.
* Turn on that section’s **Enable header overlap** setting.
* If either the theme-level or section-level overlap setting is off, the section stays in normal flow.
  {% endstep %}
  {% endstepper %}

### Notes on header behavior

* **Sticky** keeps the header visible while scrolling; **Standard** scrolls with the page; **Dynamic** can hide the header while scrolling down and show it when scrolling up—preview your main templates.
* Overlap values use 5 px steps from 5 to 200 px; tune them to your logo and bar height.

## Header settings

| Setting                 | What it controls                                                                                                                                   |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Position                | **Sticky**, **Standard**, or **Dynamic**. Default **Standard**.                                                                                    |
| Enable color difference | When enabled, header content can invert over overlapping page content for contrast. Default off. Best with light-on-dark or high-contrast artwork. |
| Enable header overlap   | Allows supported sections to render under the header when their overlap is on. Default off.                                                        |
| Desktop overlap         | Overlap offset on desktop when overlap is enabled (5–200 px, step 5, default 90 px).                                                               |
| Mobile overlap          | Overlap offset on mobile when overlap is enabled (5–200 px, step 5, default 80 px).                                                                |


---

# 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.brickspacelab.com/slab/getting-started/global-settings/header-settings.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.