> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/global-sections/header/account-menu.md).

# Account menu

Add the account icon to the Volume header and choose the menu that appears in the account dialog.

The account icon opens a dialog on the same page instead of sending the shopper to a separate account page, and **Account menu** decides which links that dialog contains.

{% hint style="info" %}
Theme editor → **Header** → **Account**. **Show account** adds the icon, and **Account menu** picks the menu inside the dialog.
{% endhint %}

### How to add

{% stepper %}
{% step %}

#### Turn customer accounts on

Customer accounts have to be turned on first, in the Shopify admin under **Settings → Customer accounts**. The editor says as much: *Customer accounts need to be enabled in your customer settings.*
{% endstep %}

{% step %}

#### Add the icon

* **Show account**\
  Off out of the box. You can tick it whether or not customer accounts are on, but the icon only renders on the storefront once they are — so a ticked checkbox and no icon almost always means the admin setting, not the theme.
* **Account**\
  How the icon looks: **Icon**, **Icon with text** or **Text**. The default is **Icon**.
* **Hide on mobile**\
  Removes it from the mobile header only.
  {% endstep %}

{% step %}

#### Pick the menu

**Account menu** selects the menu shown in the dialog. The editor says: *Select the menu shown in the account dialog. Legacy accounts not supported.* The default handle is `customer-account-main-menu`.

The **Account** block in the [Mobile dock](https://staylime.com/docs/volume-themes/global-sections/mobile-dock.md) section has the same **Account menu** setting, and it is set separately from the header.
{% endstep %}
{% endstepper %}

### Good to know

Shopify does not create a menu with the handle `customer-account-main-menu` for you. On most stores that menu does not exist, so the dialog opens with nothing in it. Create the menu in **Content → Menus**, then pick it in **Account menu**.

The dialog is Shopify's own customer accounts component, so the theme controls which menu goes in it and nothing else about it. Sign-in, the one-time code and the account page itself are Shopify's.

Legacy customer accounts are not supported. A store still on legacy accounts needs to move to new customer accounts before the dialog works.

On mobile the header always renders the plain icon, whatever **Account** is set to on desktop.

### Related

* [Header & Menu Styles](https://staylime.com/docs/volume-themes/global-sections/header/header-and-menu-styles.md)
* [Mobile dock](https://staylime.com/docs/volume-themes/global-sections/mobile-dock.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://staylime.com/docs/volume-themes/global-sections/header/account-menu.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.
