QR codes for teams roles, three seats
SmartQRCode editorial · Updated October 2026
QR codes for teams roles are three values: owner, admin, and member. All three can edit hosted codes. Only the owner confers admin, pays, and attaches domains. A Canva static file still wins when one person has a frozen destination and will not count scans.
What qr codes for teams roles actually allow
An admin cannot mint or remove another admin. The owner-only billing latch is the cancel risk. A member cannot invite. The activity log readable by members is the deterrent.
Owner is the account others point at. Admin can create, edit, invite, and remove members, but cannot mint or remove another admin, and cannot touch billing or custom domains. Member can create and edit codes and cannot invite. That grid is the whole product. Do not re-derive it in a runbook that says "admins can do everything except refunds."
The owner-only billing latch is the uncomfortable part. If an admin could cancel, they would strand every other seat, including the owner, while the owner was asleep. Domains are the same class of blast radius: a hostname in the modules is a physical object. Moving it is not a convenience click.
Unrecognised strings read as member. A row that claims owner is still a member unless it is the actual owner account. Invites cannot confer owner. The invite role is constrained to admin or member, and the accept function downgrades anything else.
Paid options are $1.99, $29, $97, and $197. We do not sell an unpaid tier. How seats are counted sits in QR codes for teams. Who should hold the owner seat in a large org sits in enterprise QR code governance. Client-by-client splits sit in agency QR code client work.
Tracked QR codes and the website URL generator are what members usually edit. Dynamic QR codes are the same hosted class. Product launch placements are the usual shared calendar: several people, one printed set.
Why an admin cannot mint another admin
Unbounded delegation is how a contractor becomes a shadow owner. The first admin invites a second "just for the weekend." The weekend does not end. The real owner is now one vote among three.
The removal half matters equally. If admins could remove admins, two of them could evict each other while the owner is not in the thread. Conferring admin stays a single-person act. That is slower. It is also how printed campaigns keep a known adult.
Member cannot invite. A floor staffer who can pause a bad URL should not be able to grow the team. Pause is an edit. Invite is a seat.
Does a member see the activity log
Activity log readable by members is the rule where that surface exists. Destination changes, pauses, and webhook edits are otherwise folklore. A member who can already see the codes can see who changed them. They still cannot rotate a webhook secret or attach a host.
Webhooks themselves are owner or admin to change, member to read. That matches the idea that a merchandiser watches, and a lead wires the CRM.
None of this identifies scanners. Country and device on hosted types are not a name. Roles govern the account, not the person in the aisle.
Hosted codes still depend on the provider. A perfect role grid does not resolve a paused owner account. F91 sits above F83.
A seat without a named human is how orphaned admins appear. Write the owner mailbox, the admin deputies, and the member shift on the same page as the SKU list. When a contractor finishes, remove the member the same day you collect the badge. Leaving the seat "for the next project" is how last quarter's freelancer still pauses codes.
If an agency needs isolation, they need a different owner account, not a decorative role called partner. Member cannot invite, and that is the point. Owner-only billing latch stays closed even when the room is full of helpful people.
Skip roles when one person owns the ink
A Canva one-off or another free static generator is enough when the payload will never move and you will not count scans. You do not need qr codes for teams roles to export a PNG of a form URL.
Two people arguing over a hosted menu that already shipped: you need roles. Write owner, admin, and member next to the print log. Do not invent a fourth role called "agency" in a slide. If the agency needs isolation, that is a different owner account, not a costume on member.
Questions this raises
One delegation would otherwise become unbounded. Two admins could also remove each other in a race the owner never sees. Conferring admin stays with the owner.
Where the activity log exists, every member can read it. A log only the owner sees deters nothing. Members still cannot change webhooks or billing.
When one person owns a frozen payload and will not count scans. A Canva one-off needs no owner admin member split. QR codes for teams roles exist for shared hosted codes.
No. Domains are owner-only and not delegable. An admin who could move DNS would move every printed host.
Keep going
The tools and playbooks this post refers to, one click away.
Make the code this post is about
$1.99 for 7 days, then a paid plan. Pick a type, brand it, and edit the destination whenever you like, even after it is printed.