> For the complete documentation index, see [llms.txt](https://docs-shpf.bsscommerce.com/bss-b2b-lock-login-password-hide-price/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-shpf.bsscommerce.com/bss-b2b-lock-login-password-hide-price/lock-core-concepts/lock-page-settings.md).

# Lock Page Settings

In **Step 3 – Lock Page Settings settings**, you fine-tune **how your lock behaves** once the basic logic is in place.

You’ve already told B2B Lock:

* **What** to protect (Step 1 – Lock content), and
* **Who** can access it (Step 2 – Control access).

Advanced settings answer a different question:

> “What should blocked visitors see, and are there any exceptions or special rules?”

Not every option needs to be used on every rule. For simple setups you can skip Step 3 and just click **Save**. But for a polished B2B experience, Step 3 is where you add the details.

***

#### 1. Lock message & display options

When a visitor does **not** meet your conditions, B2B Lock replaces your content with a **lock message**. In Advanced settings, you can customize:

* **Headline**\
  Short, clear title such as:
  * “Wholesale access only”
  * “Login to view prices”
* **Body text**\
  Explain who this area is for and what the visitor should do next, for example:
  * “This content is reserved for approved wholesale customers. Please log in or request an account to continue.”
* **Button labels**\
  If the UI provides buttons (e.g., Login, Register, Contact), you can adjust the wording to match your tone and brand.

Think of the lock message as a **mini landing page**: it shouldn’t just block people; it should guide the right visitors to the right action.

***

#### 2. Login, register & other CTAs

For locks that are based on **logged-in users** or **tags**, it’s usually helpful to show **inline actions** instead of a dead-end message.

Depending on your configuration, Advanced settings can let you:

* **Show a login link or button**
  * Directs users to Shopify’s login page.
* **Show a create account / registration link**
  * Useful if you allow self-registration for B2B users.
* **Show a contact or “Request access” link**
  * Points to your contact page or B2B registration form.

Good practice:

* If your condition is “customer must be signed in”:\
  → Always show **Login** and **Create account**.x
* If your condition is “customer must be tagged wholesale”:\
  → Add a link or note about how to **request a wholesale account**.

***

#### 3. Passcode & secret link behaviour

If your rule uses **passcode** or **secret link** conditions, Advanced settings usually gives you extra control, such as:

* **Case sensitivity** for passcodes
  * Decide whether `Password` and `password` are treated the same.
* **Remembering access**
  * Choose whether the app should “remember” a successful passcode for a period (session/cookie), so users don’t have to re-enter it on every page.
* **Error message**
  * Customize the message shown when a passcode is wrong or missing.

For secret links, you can:

* Clarify what happens if the visitor arrives **without** the secret token (e.g., redirect to lock message, homepage, or another page).

***

#### 4. Exclusions & scope fine-tuning

Sometimes you lock a big area (like an entire collection or the whole site) but you want **exceptions**.

Advanced settings often lets you:

* **Exclude specific products or pages**
  * Example: lock the “Wholesale” collection but **exclude** one public product that must stay visible.
* **Exclude certain URLs** even when “entire website” is locked
  * Example: keep your “Contact” or “About us” pages public while everything else is gated.

Use exclusions when:

* Your rule target is broad (whole site / large collection).
* You have a few elements that **must remain public** (legal pages, contact page, marketing landing pages, etc.).

***

#### 5. Session & remember-me behaviour

For login- or passcode-based locks, you can usually control how long the unlock state should last:

* **Session-based**: access lasts as long as the browser session is active.
* **Time-based** (if available): access is remembered for a certain period.

This affects how often users need to re-authenticate:

* For strict content (sensitive B2B pricing, confidential documents), shorter sessions may be better.
* For typical wholesale browsing, a more generous “remember me” improves user experience.

***

#### 6. Schedule & time-based controls

Depending on your version/plan, you may see **start/end time** or **schedule** options in Advanced settings.

These let you:

* Make a lock **active only between specific dates** (e.g., before a launch or during a private sale).
* Automatically **start** or **end** a lock without manual intervention.

Example uses:

* Pre-launch pages that are only accessible to partners before a public release.
* Time-limited campaigns where VIP customers get early access to collections.

***

#### 7. SEO & search visibility

While the **target** and **price settings** control most of what appears publicly, Advanced settings is often where you refine the experience around visibility:

* Decide whether blocked users see a **friendly message** vs a hard “404/Not found” experience.
* Make sure your messaging clearly tells search engine visitors why they’re seeing a locked screen (e.g., wholesale-only, login required).

Paired with **“Hide price on Google”** (configured when targeting prices), this helps you keep B2B information controlled while still maintaining a good UX.

***

#### 8. When can you skip Advanced settings?

You **don’t** have to configure every option in Step 3 for every rule.

You can safely **skip Step 3** and just click **Save** when:

* You’re testing or prototyping a rule.
* You just need a simple internal control (e.g., hide a test page from guests).
* The default lock message is “good enough” for now.

You should spend more time in **Advanced settings** when:

* The rule impacts real customers (especially first-time visitors).
* You’re locking critical areas like pricing, wholesale collections, or key landing pages.
* You want a polished, branded experience with clear actions (login, register, contact, etc.).

***

#### Recap

In **Step 3 – Advanced settings**, you transform a basic lock into a **user-friendly, business-ready experience**:

* Customize the **message** blocked users see.
* Add **Login / Register / Request access** calls-to-action.
* Control **passcode** and **secret link** behaviour.
* Add **exclusions** so some pages/products remain public.
* Tweak **session, schedule, and visibility** for a smoother B2B flow.

Once you’re comfortable with Step 1 and Step 2, Step 3 is where you refine everything to match your brand, policies, and customer journey.