Skip to main content
A workspace holds the data of one team. Each person and each program gets access to a workspace in a different way.

Explain workspace access.

People are members

A person signs in to their own account. The account can be a member of more than one workspace. The workspace menu in the rail changes between them. Each membership has one role: owner, admin, or member. The role sets what the person can do in that workspace only. A person can be an owner in one workspace and a member in a different workspace. A person becomes a member when they create a workspace or when they accept an invitation. An invitation is for one email address, so that only that person can accept it.

Programs use API keys

An API key belongs to the workspace, not to the person who created it. If that person leaves the workspace, the key continues to work. A key does not get the permissions of a role. It gets only the scopes that you give it, and you can give only the scopes that your role has. This keeps each key to the smallest access that its program needs. Only a hash of the key is stored. Nobody can read the key after you copy it. To change the scopes of a key, create a new key, then revoke the old key.

Settings for each person and for the workspace

Some settings belong to the workspace, such as its name and its default language. Owners and admins change them. Other settings belong to the person, such as their name, their avatar, and their language. A personal language replaces the default language of the workspace for that person. See workspace access for the exact permissions.