QR codes for teams that share a list

QR codes for teams put several people on one owner's codes. Owner, admin, and member share the list. Billing and custom domains stay with the owner. A Canva export is still enough when one person has a frozen file and will not count scans.

How qr codes for teams share one namespace

The three owner admin member roles share edits. billing and domains stay owner. A pending invite reserves a seat. An unrecognised role reads as member.

Members do not each hold a private pile of short codes that later have to be merged. They work in the owner's namespace. Quota, API usage, and scan history follow that owner. That is why a seat is not a courtesy login. It is a pointer that grants access to objects already in the field.

An account with no team owner id is the owner, whatever a stale role field says. That ordering avoids a half-failed removal that would lock someone out of their own rows. An unrecognised role reads as member, including a row that claims owner. There is no second owner.

Paid options are $1.99, $29, $97, and $197. We do not sell an unpaid tier. Role detail is QR codes for teams roles. Agency splits are agency QR code client work. Policy after ink is enterprise QR code governance.

Create with the website URL generator, count with tracked QR codes, or author a custom landing page. Retail marketing codes are the usual shared list: many facings, one merchandising owner.

How to invite without handing over billing

Billing and domains stay owner. An admin who could cancel would end everyone else's access, including the owner's. Keep that latch on one person.

1. Decide who is owner. That person already owns the printed URLs if codes exist.
2. Invite admin or member by exact email. Case-insensitive match is required on accept. Matching on email alone without the token is how a stranger used to claim an invite.
3. Treat a pending invite as a reserved seat. Do not invite ten people onto three seats and hope.
4. If the invite mail fails, expect the row to vanish so the token cannot occupy capacity.
5. On accept, the new user points at the owner. They can create and edit codes, including pause.
6. Export print files as SVG or 300 dpi PNG or PDF. Do not let a member screenshot /qr-preview for a national run.
7. Proof-scan at 2 cm or larger with a four-module quiet zone on the real stock.
8. Remove by releasing the seat first. A list row that still grants access after a "removal" is the old incident.

Resend rotates the token. If send fails, the previous token is restored so you do not hold an invite nobody can redeem.

What a seat counts as

A seat is a users row pointing at the owner, plus the owner. A pending invite reserves a seat. Count the pointer that getEffectiveOwnerData reads, not a side table that can drift.

A failed seat count is not the same as zero seats left. The honest failure is to refuse the invite with a server error, not to tell the owner they are full when the counter could not be read.

Unlimited is sent as null in JSON because Infinity is not valid JSON. Clients that subtract from null and get a negative allowance are wrong. Treat null as no cap.

Who can pause a shared code

Create and edit, including pause, sit on all three roles. That is how a merchandiser stops a bad destination at 6am without waking billing. Invite and remove sit on owner and admin. Conferring admin sits on owner only. An admin cannot mint another admin, and cannot remove one. Both halves stop a pair of admins from boxing the owner out.

Custom domains and billing remain owner-only and are not delegable. Members can read an activity log where that surface exists. They should not be able to attach qr.brand.com.

Pause stops resolution. Archive keeps scanning. Agree which verb the team uses before a night operator "archives" a live pack.

Team mistakes that lock the owner out

Handing admin to everyone, then discovering nobody can undo it except the owner, after the owner left the company. Keep a documented owner.

Counting seats from a membership table while access is granted by a different column. People remain in the namespace after they disappear from the page.

Leaving a refused invite attached during signup. The new account would hold a seat in someone else's namespace with no membership row to remove.

Expecting QR codes for teams to survive a provider pause. Hosted objects need the owner account to keep resolving. F91 is not a role setting.

How to run a shift change without losing the owner

Write the owner mailbox on the SKU map. When that person leaves, transfer the owner account in a planned window, not by inviting a new admin and hoping. Admin cannot become owner through an invite. There is one owner: the account others point at.

Night merchandisers should be members. They can pause a poisoned destination. They cannot attach a host or cancel billing. If they need to invite a freelancer at 11pm, that is an admin problem you should have staffed, not a reason to make everyone admin.

Train the words pause and archive in the same five-minute standup you use for fire exits. Archived codes keep scanning. A well-meaning close-down that archives a recall SKU leaves it live. Pause is the stop.

When a seat count cannot be read, stop inviting. A 503 is the honest answer. Pretending you are full when the counter failed, or pretending you have room when you are full, both mint the wrong number of humans in the namespace.

Keep print files in a shared drive that members can read even if they lose the seat tomorrow. The SVG is a physical object. The seat is not.

Onboarding a member should include a five-minute scan of a spare code, a pause, and a release, so they have felt the status page before they ever touch a live SKU. People who have only edited destinations in a spreadsheet will treat pause as a delete. It is not. Archive is the quiet trap in the other direction: the list looks tidy and the carton still hops.

When two brands share a holding company, still use two owner namespaces if the ink is different. A shared owner looks efficient in a board deck and then leaks a host, a key, or a pause across brands. QR codes for teams are a seat model inside one namespace, not a holding-company directory.

Export rights should be written down. Members who can download SVG can also leak next season's art. That is not a product setting. It is an employment and agency clause next to the seat list.

When a personal Canva export is enough

One designer, one poster, never edited, never counted: Canva or another free static generator. Seats add invites, mail, and a namespace you do not need.

Several people touching hosted destinations that are already printed: use qr codes for teams. Size the symbol for distance. Export real files. Keep owner, admin member roles written down next to the print log, rather than in a private notebook alone.