Features · Team roles
A printed QR code is one mis-click from pointing somewhere wrong, which makes 'who can change what' a safety feature, not an org chart. Teams here get real roles: the owner, admins who run the workspace, editors who work the library, and viewers who can see every chart and touch nothing.
The part that matters is where the roles are enforced: on the server, at every action, not by hiding buttons. A viewer's login physically cannot repoint a code — not because the form is hidden, but because the request would be refused.
Owner (everything, including billing and deletion), admin (runs the workspace, can't spend money), editor (the full library — create, repoint, design — nothing else), viewer (read-only: the role that exists because 'IT needs to see it but must never change it' is a real request).
An invite is emailed to an address, bound to that address, and expires after 14 days. A forwarded invitation link can't pull a stranger in — accepting requires signing in as the person it was sent to.
Removing someone removes their access and nothing else. Codes belong to the workspace, not to whoever created them — offboarding a designer never takes a printed campaign down with them.
PlansTeam invitations are on Scale, Business and Enterprise. A workspace that changes plan keeps every member it already has — the gate is on inviting, not on colleagues you rely on. Compare plans →
Questions
Yes — every repoint is recorded with when and by whom, per code. When a printed campaign misbehaves, 'what changed and who changed it' has an answer before the meeting does.
Everything — dashboards, charts, per-code detail. They can look at anything and change nothing, which is exactly what an auditor, a client, or a cautious IT department wants.
Related
Unlimited static codes on every plan. Dynamic codes you can repoint after printing, on your own domain.
