Teams & roles
Invite your team
One shared workspace, up to 25 people, with roles that decide who manages and who counts. What Team changes and how attribution works.
What Team changes
On the Team plan your account becomes a shared workspace: everyone sees the same scans, the same groups, and the same history. Team scanning is unlimited under our fair-use policy — we do not meter your work — and the workspace holds up to 25 members. During early access Team is free until 4 December 2026, no card; it is claimed with a single-use founding code — ask us for one — so you can try all of this with your actual crew.
Roles
Owner
The account itself: billing, and everything below.
Admin
The team and the machinery: invites, roles, API keys, webhook endpoints.
Member
Scans and works the inventory. Most of the team, and all a counter needs.
The sensitive surfaces are role-gated on the server, not just hidden in the interface: API keys and webhook endpoints can only be created by an owner or admin on a Team workspace.
Inviting
Invites are sent from the web dashboard under Team. Each invite is a link tied to an email address; the invitee signs in with any of the usual methods and lands in your workspace with the role you gave them.
Who added what
Every barcode records who first added it — that is the Added by column, and it
stays put. A colleague re-scanning the same item raises the count without reassigning
credit, so “who put this record here” always has one stable answer.
Two people, one shelf
The scan count increments happen in the database under a row lock, so two phones scanning the same barcode at the same moment both land — the count goes up by two, no lost update, no duplicate row. Splitting an aisle between two counters is the intended workflow, not an edge case. The Monday recount playbook leans on exactly this.