> 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/hide-price-1/require-customers-to-enter-passcode-to-see-product-price.md).
# Require customers to enter passcode to see product price
**Steps to manage**
1. Open the app > click **Locks** > click **Create Lock** button or open an existing **Lock**
2. In **Lock resources** > **Content to lock** section, select **Specific products or Specific collections** option > Add products/collections you want to apply the Lock
3. Then the product **Product settings** option will show up below, tick on **Hide product prices** checkbox
4. In **Lock conditions** section > **Select who can (or cannot) access the content** > select **Visitors with passcode**
5. Enter the passcode and description
6. Click **Save**
Now, view your 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/hide-price-1/require-customers-to-enter-passcode-to-see-product-price.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.