Access Codes and Content Expiration
Gate a fanflet behind an access code, set expiration presets, and configure event-date displays.
A fanflet has two reach controls. An access code decides who sees the resources. Content expiration decides how long the public page stays live. They work together, and neither one touches your dashboard, your analytics, or the underlying content.
Two ways to control reach
- Access codes gate the public URL behind a short alphanumeric code. Visitors who type the URL into a browser see a teaser and a code prompt. Visitors who scan the QR code skip the prompt because the QR carries an access token.
- Content expiration locks the public URL after a chosen date. The audience sees an expired notice. You keep the content, the analytics, and the option to reuse the fanflet later.
Setting an access code
Access codes live in the editor on the Access tab.
Open the fanflet in the editor
From the dashboard, click the fanflet you want to gate. The editor opens on the Content tab.
Switch to the Access tab
The Access tab holds the access code field, the expiration picker, and the post-survey email.
Type a 4 to 8 character code
Use letters and numbers. Short codes work best for live audiences because the goal is fast entry on a phone keyboard. Codes are case-insensitive on the public page.
Save and republish
The code takes effect on the next publish. Audiences hitting the public URL after that point see the prompt.
Pick a code with intent
What unverified visitors see
A visitor who lands on the public URL without a valid token gets the locked teaser view. The page renders your speaker hero with photo, name, and bio at the top. The fanflet title and event date sit below the hero. A small white card holds a lock icon, the heading Access Code Required, the line Enter the code shared at the event to view these resources, and a code input with an Unlock Resources button.
The teaser is enough context for someone to recognize the talk and enter the code. It does not expose any of your blocks, links, or sponsor placements.
Access tokens: how QR scans skip the prompt
Every fanflet carries an access token. The QR code points at a short token URL of the form /a/{token}. When a visitor scans the code, the token URL sets a short-lived access cookie and redirects to the public page already unlocked.
Two paths reach the same fanflet, with different friction.
- QR scan. Token URL, cookie set, redirect to the content. No prompt.
- Typed URL. Human-readable public URL, no cookie, the locked teaser asks for the code.
Why this matters
Putting the code on your slide deck
Most speakers pin the code to the same slide as the QR. Anyone who missed the scan window has the code in front of them. Anyone who types the URL later has the code in their notes. A short code on a closing slide works better than a long code in the chat.
Expiration presets
The expiration picker sits next to the access code field on the Access tab. The button group shows six options.
- Doesn't expire. The fanflet stays live until you archive it.
- 14 days from publish.
- 30 days from publish.
- 60 days from publish.
- 90 days from publish.
- Custom date. Pick any future date.
Day counts run from the publish date, evaluated end-of-day UTC. A fanflet published on the 1st with a 30-day window expires after the end of the 31st.
What expiration locks
Expiration is a public-page lock. The audience sees an expired fanflet page with your name and photo and a note that the content is no longer available. Search engines get a noindex hint on the metadata.
Nothing on your side disappears. You still own the blocks, the resource library files, the analytics history, the survey responses, and the sponsor attributions. Republishing a fresh fanflet later reuses the same library content.
The expiration notice
The Access tab also has a Show expiration notice toggle. When on, the public page surfaces a small banner with the expiration date so visitors know to save what they need before the window closes. Turn it off when you do not want the date visible.
Multi-day events
A fanflet stores both an event start date and an event end date. For a single-session talk, set the start date and leave the end date blank. For a workshop, summit, or conference that runs more than one day, set both. The hero header on the public page renders the full range.
Event dates are independent of expiration. The event date tells the audience when the talk happened. The expiration date tells them how long the resources stay live.
Plan tiers
- Free. Expiration is fixed at 30 days from publish. The picker is hidden.
- Pro. 30, 60, or 90 days from publish.
- Studio.30, 60, 90 days, or doesn't expire.
- Custom date. Available on Pro and Studio when paired with the right add-on, surfaced in the Settings tab.
- Access codes. Available on every paid tier.
Server-enforced
Related guides
- QR codes and public URLs covers the token URL and how to print the code for live talks.
- The block editor covers the Access tab in context with the rest of the editor.
- Creating your first fanflet walks the full publish flow end to end.