Two-factor sign-in
Add 2FA so a password alone can't unlock your account.
Feature
Codes and accounts you can trust
Protect your account with two-factor sign-in, lock sensitive codes behind a password, control who can do what, and review a history of actions.
- Two-factor login
- Per-code passwords
- Role-based access
- Activity history
Security controls
Two-factor sign-in
Per-code passwords
Role-based access
Activity history · every change logged
How it works
Layers that keep you covered
Secure your account
Turn on two-factor authentication for an extra layer at sign-in.
Set roles and access
Give teammates the right level of access with role-based permissions.
Review what happened
Check the security and activity history to see actions taken in your workspace.
What you get
Protection at every layer
Per-code passwords
Require a password before a code's content opens.
Role-based access
Control who can view, edit or manage in your workspace.
Put it to work
Where security matters most
Restrict sensitive content
Gate internal or private links behind a password.
Team permissions
Give each member the access their role needs.
Audit trail
See a history of actions for accountability.
Protect accounts
Reduce takeover risk with two-factor sign-in.
Client work
Keep each client's codes locked to the right people.
Limited-audience codes
Share content only with those who have the password.
QR code security FAQ
How do I secure my account?
Enable two-factor authentication so signing in needs both your password and a second code.
Can I password-protect a code?
Yes — set a password on a code so its content only opens for people who have it.
Can I control what teammates can do?
Yes. Role-based access lets you decide who can view, edit or manage in your workspace.
Is there a record of actions?
Yes — a security and activity history shows actions taken in your account.
Does password protection change the code?
No. The code stays the same; the password gate sits in front of the content.
Put the control in the workflow
- Require TOTP two-factor authentication for privileged users.
- Review active sessions and revoke unfamiliar ones.
- Use audit history, login alerts and abuse reporting as part of normal operations.
Questions before enabling security
- 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?