> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/b2b-lock-password-protect/content-to-lock/pages.md).
# Pages
Lock specific storefront pages behind access rules while the rest of your store stays public.
The **Pages** content type locks one or more specific storefront pages — for example an FAQ page reserved for logged-in customers, a wholesale application page, or a members-only resources page.
## Create the lock
1. Open **Locks** in the app's navigation.
2. Click **Create lock**.
3. Give the lock a descriptive name, for example "Wholesale application page."
## Choose Pages as the content to lock
4. On the **Lock setup** tab, in the content picker, select **Page**.
Select Page in the content picker to lock one or more specific storefront pages.
5. Use the page picker to search and select the pages you want to lock. You can select more than one page for the same lock.
Search and select the specific storefront pages you want to lock.
{% hint style="warning" %}
Locking pages may require a paid plan depending on your current plan.
{% endhint %}
6. Click the **Unlock rules** tab to continue.
## Add an access rule
7. Add at least one rule — for example, **Logged-in customers** so only signed-in shoppers can view the page.
8. Configure the rule's settings. See [Access rules overview](/b2b-lock-password-protect/access-rules/overview.md) for the full catalogue of available rules.
9. Add every required condition to the access key. All conditions must be satisfied. See [Combining rules](/b2b-lock-password-protect/access-rules/combining-rules.md).
## Choose a lock behavior
On the same **Unlock rules** tab, the right-hand sidebar has a **Blocked visitor behavior** panel — configure it alongside your rule:
10. A locked page typically shows a full lock screen instead of its normal content until the visitor passes. You can also redirect visitors elsewhere after they gain access, or hide the page's link from your storefront menus so it isn't discoverable by visitors who don't qualify. Review [Lock behavior overview](/b2b-lock-password-protect/lock-behavior/overview.md) for the full set of options.
## Save
11. Click **Save**. The lock takes effect on your storefront as soon as the app embed is enabled.
## Related docs
* [Access rules overview](/b2b-lock-password-protect/access-rules/overview.md)
* [Lock behavior overview](/b2b-lock-password-protect/lock-behavior/overview.md)
* [Manage locks](/b2b-lock-password-protect/locks/manage-locks.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 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://docs.samita.io/b2b-lock-password-protect/content-to-lock/pages.md?ask=&goal=
```
`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.
