> 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/avante-themes/templates/other-templates/password.md).

# Password

The storefront password page — a newsletter signup shown while the store is locked.

When the storefront password is on, Shopify shows the **Password** template instead of the shop.

{% hint style="info" %}
**Theme editor → Password → Default password** · Enable the gate in **Shopify admin → Online Store → Preferences → Restrict access to visitors with a password**
{% endhint %}

***

### What the template contains

In 16.0.0 the main section of the password template is a **Newsletter** section with heading, text and signup-form blocks, so visitors can join the list while the catalogue stays locked. Style it like any newsletter section — the shared form options are described under [Call to action](https://staylime.com/docs/avante-themes/sections/call-to-action.md).

You can add further sections to the password template if the editor offers them for that template.

***

### Related

* [Call to action](https://staylime.com/docs/avante-themes/sections/call-to-action.md)
* [Other templates](https://staylime.com/docs/avante-themes/templates/other-templates.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/avante-themes/templates/other-templates/password.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.
