Password gate
A password screen appears before the code's destination loads.
Feature
Keep a code's page behind a password
Require a password before a dynamic code opens its destination. Share the code widely, but let only the right people through.
- Password gate
- Private content
- Change anytime
- Dynamic only
This code is protectedEnter the password to continueUnlock
How it works
Gate a code in three steps
Turn on protection
Set a password on any dynamic code from its settings.
Share the code
Print or send it as usual — the password is the key.
Only insiders get in
Scanners enter the password to reach the destination; everyone else is stopped.
What you get
Simple access control
Change on demand
Update or remove the password any time — the printed code never changes.
Control who sees what
Share the code openly while keeping the content limited to people you trust.
Put it to work
When a code shouldn't be wide open
Private documents
Gate menus, price lists or files meant for a specific group.
Internal links
Point staff to internal resources without exposing them publicly.
Members-only content
Reward subscribers with codes only they can open.
Product inserts
Put warranty or setup info behind a password on packaging.
Course materials
Share class resources with enrolled students only.
Sensitive info
Add a barrier in front of content that shouldn't be public.
Password protection FAQ
How does the password work?
When someone scans the code, a screen asks for the password before the destination opens.
Can I change the password later?
Yes — update or remove it any time. Because the code is dynamic, the printed artwork stays the same.
Is this the same as encrypting the content?
No — it's an access gate in front of the destination. For stronger protection, combine it with the security controls on your account.
Can everyone share one password?
Yes. You set one password per code and share it with whoever should have access.
Does it work on static codes?
No. The password screen lives on the redirect page, which only dynamic codes use.
Use it without creating a mess
- Set a password that can be shared safely.
- Explain to the intended audience where to obtain it.
- Rotate the password when access should change.
Questions before enabling password protection
- Which repeated task or control problem is this feature meant to solve?
- Who owns the configuration after the first campaign launches?
- Which plan limit or permission affects the rollout?
- What should happen when a destination, member, domain or subscription changes?
- How will the team test the complete scan path before printing?
Related features
Lock down a code in seconds
Create a free dynamic code and add a password before you share it.