Workspace members (the Members screen)

What it is

A workspace's people are its members. Each person holds exactly one role:

• Owner — everything, including making someone else an owner.
• Admin — invites people, removes them and changes roles, but can never touch an owner.
• Member — belongs to the workspace and can be given a role by an owner or admin; manages nobody.
• Guest — let into specific Team Chat channels rather than into the whole workspace.

Three things sit beside the roster. The seat count — the "N members" line under the heading — counts people who have actually joined and are not guests, so a pending invitation never bills a seat. Pending invitations are addresses that have been asked and have not accepted yet; they grant nothing until they are accepted. Guests are listed separately because their access is scoped to channels.

A person who has been removed and a workspace you have left never appear on the roster. An invitation nobody has accepted appears only under Pending invites, never as a member.

Where to find it

Open Settings → Team & Admin → Workspaces and scroll to the Members section under the Workspace heading; on a staff install the same navigation row is labelled User Management. Typing "Workspace Members" into Settings search jumps straight there.

The section opens on a People tab. An owner or admin of a company workspace also gets Pending invites, an Invite members button, a per-row menu, and — in the desktop app only — a Guests tab. Anyone else sees the roster read-only, plus a Leave button when they belong to the workspace.

The same people appear wherever the app shows teammates: Team Chat's member directory and channel member pickers, and the invite picker in the share-a-session dialog. The personal workspace has no team — its roster is you alone.

How it behaves

The roster

One row per person: their picture, name, a role pill and the date they joined. A search box filters the list by name. While the list loads you see placeholder rows; if it cannot be loaded you see an error with Retry, never an empty workspace. Every open roster updates live — when someone accepts an invitation, is removed or is re-roled, they change (or disappear) without a restart.

Controls you may not use are absent, not greyed out. What you see in a row menu is a convenience, never the permission: the server decides every change from your live role in that workspace.

Inviting people

Invite members opens a dialog with one field that takes a single address or a whole pasted list, separated by commas, spaces, semicolons or new lines. Entries that do not look like an address are named and skipped before anything is sent.

Sending answers per address: how many were invited, any that were skipped as blank or duplicate, any that failed with the reason, and whether the invitation email could not be delivered — in which case ask the person to check their spam folder, or run Invite again later. If a batch was cut short by the daily limit, the dialog tells you how many addresses were not sent yet and you run Invite again to finish; re-running is always safe, because addresses already invited are skipped.

Invitations are only offered on a company workspace. A self-serve chat workspace joins people with an invite code from inside Team Chat, so it has no invite dialog here.

Pending invitations

The Pending invites tab lists each address with when it was invited and when it lapses. Resend asks the invitation to be sent again — a repeat for an address that was mailed within the last hour is skipped, so nobody is mailed twice in quick succession. Revoke invite confirms and then withdraws the invitation, so nobody can join with it.

Guests

The Guests tab lists the guests of the workspace and the channels each one was let into — channel names while Team Chat is open on the same workspace, otherwise how many channels. Remove confirms and takes away their access to those channels. Invite guest — offered while Team Chat is open on this same workspace — opens Team Chat's own guest invitation, which owns the channel choice.

Guests are managed in the desktop app only, and only by an owner or admin.

Changing a role, removing someone, handing over ownership

An owner or admin opens a person's row menu. Which items appear depends on both roles. Make admin or Make member appears whenever the other role differs. Make owner appears only for an owner, and only on someone who is not a guest. Remove appears on anyone they may act on, except a guest — guests are managed from the Guests tab instead. An admin sees no menu at all on an owner's row, and nobody can act on their own row beyond handing the workspace over. Every item asks first, in a sentence that names the person and what it costs them.

Transfer ownership lives on your own row, and only if you are the owner. It asks you to pick the new owner from the other members who are not guests, warns that you become an admin, and then does both halves as one change: the new owner is in place before you step down, so the workspace is never left without an owner.

A workspace always keeps at least one person who can administer it — an owner or an admin. A change that would take the last of them is refused with a sentence saying so, and nothing is removed.

Leaving

Leave sits in the Members header for anyone who belongs to the workspace. It confirms that you lose access to its channels and messages and would need a fresh invitation to return. If you are the only owner, leaving is refused, and the message tells you to make someone else an owner first. Leaving a workspace you are currently working in takes effect at once: the app moves you off it and re-reads who you are, rather than showing the old workspace until your sign-in happens to refresh.

Refusals

Every refused or failed action arrives as a plain sentence — the last owner, not allowed, owner-only, the invitation limit, or not supported for this workspace. A raw backend or network error is never shown. A roster that failed to load says so and offers Retry rather than pretending the workspace is empty.

Related

Team Chat covers the member directory, channels and direct messages that show these same people, including guests' channel access. Plans & billing covers what a seat costs and why the seat count matters. Team Chat API platform covers the programmatic side of workspace membership.