> For the complete documentation index, see [llms.txt](https://uxsmart.gitbook.io/velare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uxsmart.gitbook.io/velare/set-up-your-store/customer-account.md).

# Customer account

Customer account settings control how shoppers reach their account from your storefront. You choose which menu item acts as the account entry point, and whether tapping it opens a popup on the current page or sends the customer to the account page. Turning accounts on lets customers log in, see their order history and reorder, which is useful for stores with returning buyers. Legacy customer accounts are not supported, so your store needs to be on the new customer accounts.

### Where to find these settings <a href="#where-to-find-these-settings" id="where-to-find-these-settings"></a>

Go to **Online Store > Themes > Customize > Theme settings > Customer account**.

<figure><img src="/files/m2PATbOBjV7yW7uwOVlx" alt=""><figcaption></figcaption></figure>

### Settings <a href="#settings" id="settings"></a>

| Settings    | Description                                                                                                                                                      |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Menu**    | The menu item customers use to open their account. Pick the menu that already holds your account link.                                                           |
| **Open as** | How the account opens when a customer clicks that item. Choose **Popup** to open it over the current page, or **Link** to send the customer to the account page. |

The image below shows the two available settings of the Customer account section, Menu and Open as.

<figure><img src="/files/3yQvIvZhcJSl4UJyVAXS" alt=""><figcaption></figcaption></figure>

### What customers see <a href="#what-customers-see" id="what-customers-see"></a>

Customers reach their account through the menu item you selected, so the wording of that menu item is what they see on the storefront. With **Popup**, the login form opens over the page they are already on and they keep their place after logging in, which suits stores where customers log in mid browse. With **Link**, they leave the current page and land on the Shopify account page instead. Because legacy accounts are not supported, customers sign in using the new customer accounts flow.

### Related pages <a href="#related-pages" id="related-pages"></a>

* [Header](/velare/set-up-your-store/header-group/header.md): where the account entry point sits in the header
* [Layout](/velare/set-up-your-store/layout.md): global page width and corner radius applied to the account popup and forms
* [Colors](/velare/set-up-your-store/colors.md): color schemes used by the account popup and its buttons
* [Vélare Intro](/velare/readme.md): overview of the theme and where to start


---

# 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://uxsmart.gitbook.io/velare/set-up-your-store/customer-account.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.
