08 · Teams
Most generators assume one person and one code. QR Lift assumes a team managing hundreds — shared workspaces, locked brand presets, roles, and an audit trail on every destination change.
Shared workspace
Invite teammates by email. Everyone sees the same code library, folders, and scan data — no more codes trapped in one person's account.
Roles
Give designers edit rights and stakeholders read-only analytics. Only admins can repoint a live printed code.
Brand presets
Save colors, module shape, and logo as a workspace preset so every code a teammate generates is already on brand.
Workflow
Multi-person QR management fails on process, not features. This is the process our team workspaces are designed around.
Owner and admins can repoint live codes; members create and edit their own; viewers get analytics only. Decide this before you invite anyone.
Presets belong to the workspace, not to the person who made the first code. New teammates inherit the correct style automatically.
Channel, campaign, placement, date. Folders per team, region, or batch. Write it in the workspace description so nobody guesses.
One approver scans the proof and checks the destination before print. Cheap insurance against an expensive reprint.
Every destination change is logged with user and timestamp. Treat that log as the record of truth in any post-campaign review.
Archive finished campaigns, fix dead destinations, and reassign codes owned by people who have moved on.
Best practices
The small rules that stop a shared library from decaying.
Never let a printed code live in an individual's private account — that's how organisations lose control of assets already in the wild.
Only admins should be able to repoint anything already printed. Everyone else can still build and test freely.
When someone leaves, reassign their codes in the same pass as their email. An orphaned dynamic code is a live liability.
Static codes, third-party destinations, and permanently placed signage should be listed somewhere your future team will find.
The Team plan includes shared seats in a single workspace. Every member generates codes into the same library, with roles controlling who can edit destinations.
Yes, within their role. Admins and owners can repoint any dynamic code; members can create and edit their own; viewers only see analytics.
Yes. Destination edits are logged with the user and timestamp so you can trace any change to a printed campaign.
Yes — CSV upload creates codes directly in the shared workspace with your team's brand preset applied.