> 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-products.md).
# Creating Lock for Products
### **Create Lock for all Products**
**Steps to manage**
1. Open the app > click on the **Locks** section > **Create Lock**
2. In the **Lock setup** tab, set up **Lock name**:
3. Move to the **Content to lock** section:
* Choose a Lock content for Products: **All products**
* **Exclude** some specific products in the **Restricted products** setting (optional)
4. In the **Unlock rules** tab > Navigate to the **Access key** section and set up a lock condition.
*For example:*
*Hide the products in the storefront and only allow **customers who login to the store** can see the products again.*
*Customers will be redirected to the login page immediately once trying to access the locked products.*
*After login, customers are redirected back to the Collection page to start purchasing locked items in the store.*
* **Rule condition** > Select **Logged-in customers** from the list:
* **Rule logic**
There are two options for you to choose: **If** or **Unless**.
**If** - when you just want customers to immediately login to your store when they try to access the locked products.
**Unless** - when you want customers to be redirected to another page to do other things you require before they can login and see the locked products. Like register or do some extra works before login.
In each logic, the app supports redirecting customers to a specific page before or after login.
* Navigate the **Summary** section, in here, select a **lock behaviour**:
You also can configure to hide the product in Google by checking the settings in **Google settings**:
These settings help you:
* Hide products within collection pages/product lists
* Hide products on Google via search/search engine.
5. Click **Save** to complete the lock.
Check the result on the front store.
***
### **Create lock for specific Products**
**Steps to manage**
1. Open the app > click on the **Locks** section > **Create Lock**
2. In the **Lock setup** tab, set up **Lock name**
3. Move to the **Content to lock** section:
* Choose a Lock content for Products: **Manual products**
* Select the products you want for this lock in the **Restricted products** setting:
*\*You can select more than 1 product*
4. In the **Unlock rules** tab > Navigate to the **Access key** section and set up a lock condition.
*For example:*
*Hide 1 product in the storefront and only allow **customers who login to the store** can see the products again.*
* Navigate the **Summary** section, in here, select a **lock behaviour**:
You also can configure to hide the product in Google by checking the settings in **Google settings**:
5. Click **Save** to complete the lock.
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-products.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.