Work on your codes as a team

Make a team workspace for each client or location and give every person a role. To work with someone outside the team, share one folder.

One place for the teamThe switcher moves between your personal workspace and your team workspaces.
A role for each personOwners, admins, members and viewers see and do only what their role allows.
Invite by emailAn invite names the role. It waits until the person signs in with that address.
Share one folderA folder can go to a client with read, write or edit access.

The names, links and numbers in this video are demo data.

What's in it

Workspaces: Your personal workspace stays private. Make a team workspace for each client or location, and switch between them from the header.
Roles: An owner can do everything. Admins manage members and settings, members make and change codes, and viewers see codes and scan stats without changing anything.
Invites: Invite people by email with a role. The invite waits until they sign in with that address and confirm it.
One folder: Share a single folder with someone outside the team. They can view it, edit its codes or manage it.
Keys and chats: API keys and connected apps act as the person who made them, with that person's role.

We don't send invite emails yet. Copy the sign-up link from the invite and send it yourself.
A workspace has one owner. The owner hands it to someone else before leaving.
Codes stay with the workspace when someone leaves it.