The lock covers the entire Experience, not one block. It is checked before anything else on the page, before the blocks, before the Inclusion Bar, before the cookie banner.
Draft, published, and back again
Draft
Who can see it
Only you, signed in
Address
/preview/{hash}
Every change is saved as you make it. Nothing here is reachable by a visitor, and a Marker pointed at a draft has nothing to open.
Published
Who can see it
Anyone with the link
Address
/view/{hash}
The public page. Edits you make afterwards go live the next time someone opens it. There is no second publish step for changes.
Unpublished again
Who can see it
Nobody
Address
None
The content stays exactly as you left it. Visitors get a short 'not available' page, and any Marker pointing here lands on the same.
Setting one
- 1
Open the Settings tab in the builder
Scroll to Require PIN to view and switch it on.
- 2
Type a PIN
Between 4 and 8 characters. The visitor's field opens a number pad on a phone, so a numeric code is the kindest choice.
- 3
Write a challenge message
Optional but strongly recommended: it appears above the input. “Enter the code from your ticket” tells somebody where to look; a bare PIN box tells them nothing.
- 4
Test it in a private window
Your own preview bypasses the lock, so you will never see it in the builder.
What the visitor sees
A single centred card on a plain page: the heading This Experience is locked, your challenge message if you wrote one, one wide-tracked input, and an Unlock button. Nothing else: no blocks, no navigation and no clue to what is behind it beyond your own words.
A wrong code turns the field's border red, shows Incorrect PIN. Try again., and clears the field. There is no lockout and no attempt counter, so a visitor who fumbles it can simply try again.
How long an unlock lasts
For the session, and no longer. Reloading the page asks again, and so does coming back tomorrow. This is deliberate: the code is on a ticket or a door, and the visitor has it to hand.
What a PIN is good for
- Ticketed content. A code on a ticket, opening a trail or an audio tour.
- Staff pages. A back-of-house Experience with opening procedures, on the same Marker system as everything else.
- Guest-only material. A room directory you would rather the street did not read.
- Timed reveals. An escape-room clue, a treasure hunt stage, a launch page you change the code on each morning.
What a PIN is not good for
If what you need is to know who the visitor is rather than to keep strangers out, that is a different tool: phone verification, on the Growth plan, confirms a real number once and recognises the person afterwards.
Changing or removing the code
Edit the PIN in the Settings tab and it takes effect on the next visit. Anyone mid-session keeps their unlock until they reload. Switching Require PIN to view off makes the Experience openly public again at the same address, immediately.
Example
Cedar Hollow Zoo & Aquarium
Cedar Hollow's after-hours lantern tour has its own Experience (a map, a running order and three animal stories) locked behind a four-digit code printed on the tour ticket. The challenge message reads “Enter the four digits from your lantern tour ticket.” The code changes each season, which takes one edit and no reprinting of anything on the trail, because the Markers point at the Experience and not at the code.
Can I use different PINs for different people?
No: one Experience, one code. For several codes, build several Experiences, which also lets you tell from the stats which group came in.
Does the lock stop the Experience appearing in my stats?
No. Views, taps and scans are still counted, and an unlock is recorded as its own event, so you can see how many people who arrived actually had the code.
Why does the PIN screen not show my colours?
It is deliberately plain, so that nothing about it can be mistaken for the content behind it. Your challenge message is the place to sound like you.
Can a locked page still be read aloud?
Yes. The lock screen itself is readable by read-aloud and by screen readers, so somebody who cannot see the challenge message still hears it.