Adding and removing people
Creating an account directly, resetting a password, and what leaving actually leaves behind.
Invitation first, direct creation second
The main route is an invitation, because on that path the person sets their own password and you never know anybody's.
Direct account creation also exists, for when an invitation is impractical. An account created this way is born active, holds a seat in this workspace and nowhere else, and gets no platform access.
If that address already has an account elsewhere, the answer is a neutral conflict: it does not say which workspace holds it. Display names, by contrast, never conflict — two people may share one.
Credential authority follows sole membership
A workspace admin can reset or disable an account only if that account lives in this workspace and nowhere else.
If the same person is a member elsewhere too, that authority is not yours — otherwise one workspace could cut off another's access.
When somebody leaves the team
Removing the membership frees the seat and ends their access. But their contact record stays in the directory and only loses the colleague tag.
The reason is that their feed, their seats and their work are the firm's history. The tag is derived from membership rather than stored, so it can never drift out of step with the truth.
The roster never offers to change your own role, and the last-owner guard applies here too.
Read this next
- Workspace & teamColleagues in the contacts directoryWhy your own team are contacts too, and why they never appear twice.
- Workspace & teamRoles and permissionsThree roles inside a workspace, and one entirely separate axis for the vendor.
- Account & plansYour account and passwordWhat you change yourself, and what changing a password does to your other devices.
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.