> ## Documentation Index
> Fetch the complete documentation index at: https://launchday.apps.madvalley.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Multiple Locks on the Same Content

> What happens when more than one lock covers the same product, page, or collection — and how to see it before it happens.

You can have more than one lock covering the same product or page — for example a Product lock on a single item *and* a Collection lock on the collection it belongs to, or two Product locks you created for different groups of customers. This page explains exactly how that works.

> [!TIP]
>
> If you just want to give different groups their own passcodes for the same content, you don't need separate locks — add several passcodes to **one** lock instead. See [Creating Your First Lock](https://launchday.apps.madvalley.com/docs/getting-started/creating-your-first-lock.md).

## The short version

* **Every active lock applies.** The product or page stays locked as long as at least one active lock covers it.
* **Any one lock's passcode gets a customer in.** If two locks cover the same product, a customer can enter either lock's passcode.
* **Removing or unlocking one lock never opens something another lock still covers.** The content opens only when the last lock covering it is gone.

## What customers see

Customers see one lock screen — the message, image, and button settings of the **most recently created** lock covering that content. Entering the passcode from *any* covering lock unlocks it, even though only one lock's screen is shown.

> [!NOTE]
>
> If you add another lock to something that's already covered, customers who had previously unlocked it may be asked for a passcode once more.

## Seeing what's already covered

When you pick products, pages, or a collection in the lock builder, Launch Day - Store locks checks whether anything else already covers them and tells you before you save:

> *2 products in this collection are already covered by Spring Drop. Visitors can unlock them with the passcode from any covering lock, including this one.*

This is a heads-up, not an error — you can save the lock either way.

## Removing or unlocking one of several locks

| What you do | What happens |
| - | - |
| **Remove** a lock that others also cover | Only that lock's hold is released. Anything another active lock still covers stays locked, and shows that lock's screen. |
| **Remove** the only lock covering something | It opens. |
| A **scheduled unlock** fires for one of several locks | That lock is released at the scheduled time. Content another lock still covers stays locked. |

When a scheduled unlock fires and other locks still cover the same content, the confirmation email says so — for example, *"2 products are still locked by Wholesale, so they stay locked until that lock is released."* If nothing else covers the content, the email is unchanged.

## Collections and individual products

A Product lock and a Collection lock can both cover the same product. The product stays locked until **both** are released, and either lock's passcode opens it. See [Collection Lock](https://launchday.apps.madvalley.com/docs/locking-your-store/collection-lock.md) for how a Collection lock stays in sync with its collection.

## Site locks are the exception

Only **one Site lock can be active at a time**. A Site lock covers your whole store rather than specific items, so a second one would have no clear meaning. If you try to create or reactivate a second Site lock, Launch Day - Store locks asks you to remove the active one first. Product, Page, and Collection locks work on top of a Site lock as usual.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.