Skip to content

Team

At /app/team, pick a role and create an invite — this generates a one-time link rather than sending an email, so you share it yourself (WhatsApp, email, however you’d normally reach them). The link works once and expires after 7 days; opening /join/{token} while signed in (or signing up first) shows the team and your proposed role. You join only after selecting Accept invitation. Opening, refreshing or previewing the link does not consume it; Not now leaves your account unchanged. Someone who already belongs to another organisation with a venue, or with other members, can’t accept a second invite.

An owner can invite a manager (edits the menu, settings and availability, and can invite staff) or staff (availability and Today when Book is enabled; cannot invite anyone); a manager can only invite staff, not another manager. Only the owner can manage billing or delete the venue — a manager is refused both. There’s one owner per organisation — the account that created it — so ownership itself is never handed off through an invite.

Team seats — every accepted member plus every invite still open, beyond the owner — start on the Pro plan. Free has no seats at all, so inviting anyone is refused until you upgrade; Pro includes 2 seats, Business 10. See Plans and pricing. Once a plan’s seats are all taken — by members plus invites still pending — creating another invite is refused until a seat opens up or you upgrade.

/app/team lists every accepted member with their name, email, role and join date, and separately lists invites still pending with their role and expiry date.

A pending invite (not yet accepted) can be revoked from the team page, which invalidates its link immediately. For an accepted member, select Remove access and confirm. Owners can remove managers or staff; managers can remove staff. Owners and your own account cannot be removed. This applies to all organization venues, ends account sessions and connected-agent tokens, and revokes pending invitations created by the removed member. Organization API keys and separate POS staff PINs are independent: review or rotate them separately if shared with that person. Reinvite the member if access is needed again.

Navigation and search show staff only their availability and enabled booking screens. Language and sign-out controls remain available.