The three roles
Owner is the person whose card is on file and whose data it is. Billing, spend caps, inviting and removing people, and deleting the workspace are theirs alone, and no amount of seniority elsewhere substitutes for it.
Admin is the person who builds and maintains the agents. They can create agents, load knowledge, buy numbers, wire up actions and work every conversation. They cannot see or change billing.
Agent is the person who answers customers. They live in Conversations and the Inbox, take over a chat when the agent hands one up, and reply as themselves. They cannot change instructions, knowledge or channels — which is the point: the person handling a live customer should not be able to reconfigure the agent mid-conversation.
Send an invitation
Settings → Team, as an owner. Enter the address, choose the role, and they get a link. The link is the credential, so treat it like a password: anyone holding it can join the workspace at the role you chose.
If they have no account yet — the common case — the link takes them through sign-up first and then straight into the workspace, so they never see an empty account with nothing in it.
Settings → Team
Visible to owners. Admins and agents do not see it.
Address and role
Pick the least privilege that lets them do their job. You can raise it later in one click.
Send
They get a link. Accepting it lands them on a short orientation for their role, not on a blank dashboard.
What a new teammate sees
Someone joining an existing workspace does not get the build-an-agent wizard — the agent already exists, and somebody else built it. They get a short welcome that names their role, says what they can and cannot do, and points at the two or three pages they will actually live in.
It is worth reading over their shoulder the first time. The most common confusion for a new agent-role teammate is looking for settings they cannot see, and the welcome page answers that before they go hunting.
Changing and removing people
Roles change in the same place, and take effect immediately. Removing someone ends their access to the workspace, and their name stays on the replies they wrote — a conversation history should not rewrite itself when somebody leaves.
There is one owner per workspace by design. Handing a workspace over is a conversation with us rather than a toggle, because it moves the billing relationship as well as the access.