> 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/lock-1/creating-lock-for-specific-pages.md).
# Creating Lock for specific Pages
**Steps to manage**
1. Open the app > click **Locks** > click the **Create Lock** button
2. Choose the type of lock you want > **Specific Pages** > **Create lock:**
3. Set up **Name** for the lock.
4. In the **Restricted page** setting > Click **Browse** and select the page you want to add to this lock:
*You can choose more than one 1 page to lock.*
{% hint style="info" %}
The app takes page data from **Shopify Pages** to show you the page list like that in the lock.
{% endhint %}
5. Set up **Conditions settings**: Select who can (or cannot) access the content, and the direct page when customers access the Lock. Refer to this [document](https://docs.samita.io/b2b-lock-password-protect/lock-1/lock-condition):
6. Click **Save** to update the changes
Check the result on the front store.
{% hint style="success" %}
**Need support?**
If you do encounter any difficulty while proceeding these steps, don’t show any hesitation to contact us promptly via the email address [support@samita.io](https://samita.io/pages/contact)
{% endhint %}
---
# 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/lock-1/creating-lock-for-specific-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.