Invite teammates

Settings → Governance → Users holds everyone in your workspace and every invitation you have sent. It needs the manage_org_roles permission.

The page has two tabs: Users, the people who have joined, and Pending Invitations, the ones who have not yet.

Invite someone

1. Click + Invite User.
2. Enter their email address.
3. Choose their Access. The list has two groups: the roles your workspace has defined, and three built-in levels (Administrator, Team Member, Viewer).
4. Read the permission list under the picker. It is the exact set the invitation grants, not a summary of it.
5. Click Create Invitation.

Choosing a workspace role does two things a built-in level does not: it grants that role’s permission set, and it seats the invitee in the role when they accept, so the org chart is right without a second step. A role somebody already holds still grants its permissions but does not reseat anyone.

What the invitee receives

The invitation is emailed. They click through, sign up, and land in your workspace.

The link also appears in the drawer after you submit, so if the mail is caught by a spam filter you can copy it and send it however you normally would.

The link is the invitation

Anyone holding the link can accept it, so treat it as a credential. It expires after seven days, and you can revoke it from the Pending Invitations tab before then.

After they accept

Their row moves from Pending Invitations to Users, and the permissions the invitation carried become theirs. From that point on their access changes through roles, not through the invitation.

Their arrival is recorded in the audit log as user.joined, with the invitation it came from.

Removing someone

Removing a member from the Users tab ends their access. Work they created stays: tasks keep their history, meetings keep their messages, and the audit log keeps every action under their name. A workspace whose record thinned out when somebody left would not be a record.

Next steps

• Roles and permissions: define the access before you send the invitation.
• The audit log: who joined, who changed what, and when.
• Permission tokens: access for a script rather than a person.