For the complete documentation index, see llms.txt. This page is also available as Markdown.

Lock behavior overview

What a blocked visitor actually experiences, and the six behaviors you can configure on a lock.

Every lock in Sami B2B Lock, Password Protect is built from three pieces: content to lock (what's protected), access rules (who must match to get through), and lock behavior — this piece. Lock behavior is what a blocked visitor actually experiences on your storefront, and what happens once someone passes your rules.

Not sure how these three pieces fit together? Start with Locks overview.

Where content-to-lock decides what is protected and access rules decide who gets in, lock behavior decides:

  • What a blocked shopper sees in place of the protected price, button, page, or menu link.

  • Whether the protected content is hidden from search engines, on-site search, and navigation menus.

  • Where a visitor goes after they pass (or after they fail a specific rule).

  • Whether passing a rule tags the customer's account.

  • How long a visitor stays unlocked before they have to verify again.

These settings live on the Unlock rules tab of each lock's editor — the same screen where you add access rules, not a separate step afterward. Hide price and Add to cart, Hide from search engines, and Hide from menus configure in the Blocked visitor behavior panel in that tab's right-hand sidebar, and the exact fields shown there depend on the lock's content type. Redirect after access, Add customer tags on verification, and Grant access duration instead configure per access key/rule in that same tab's main column, alongside the rule builder.

The six behaviors

Behavior
What it controls
Guide

Hide price and Add to cart

Hide a product or collection's price, Add to cart button, or both — or hide the item entirely

Hide from search engines

Remove protected content from on-site search, the sitemap, and search engine indexing

Hide from menus

Remove a protected item's links from storefront navigation menus

Redirect after access

Send a visitor to a URL after they pass, or after a specific rule denies them

Add customer tags after access

Tag a signed-in customer's account after they satisfy an access key

Grant access duration

How long a visitor stays unlocked before re-verifying

Last updated

Was this helpful?