> ## Documentation Index
> Fetch the complete documentation index at: https://help.plannotator.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Invite and Remove Organization Members in Workspaces
> Invite people, change organization roles, manage pending invitations, and remove members safely.
Hosted Workspaces admins manage people from a team's **Members** tab. Admins
can invite people, change roles, resend or revoke pending invitations, and
remove members. Every member can view the roster and leave the team.
Self-hosted Workspaces does not show these hosted team controls. Its identity
provider controls who can sign in to the instance.
## Understand the two roles
| Role | Team controls |
| ------ | -------------------------------------------------------------------------------------------- |
| Admin | Invite and remove people, change roles, manage pending invitations, and change team settings |
| Member | View the roster, use workspaces shared with the team, and leave the team |
Both roles get the same access to a workspace shared with the organization.
The admin role adds team-management controls. It does not grant extra access to
private workspaces.
Guests are not organization members. They use guest links, do not appear in
the member roster, and do not use seats.
## Invite people
Only an admin can send invitations.
From **Home**, open the team under **Your organizations**, then select
**Members**.
Under **Invite people**, enter up to 50 email addresses. Separate addresses
with commas or line breaks.
Select **Member** or **Admin**. Workspaces gives every person in this batch
the same role. Workspaces selects **Member** by default.
Select **Send invites**. Workspaces reports how many people it invited and
lists each address it could not invite.
Workspaces sends each recipient an email. The recipient follows that email to
accept. There is no invitation inbox in Workspaces.
A pending invitation does not use a seat. The recipient becomes an active
member and may use a seat after accepting. See [Plans, trials, and
seats](/workspaces/billing/plans-trials-and-seats).
If some addresses fail, Workspaces still sends the successful invitations.
Check **Members** and **Pending invitations** before trying a failed address
again. An address may fail because the person is already a member or already
has a pending invitation.
When Workspaces reports an organization as expired, it blocks new invitations.
An admin can subscribe from the organization's **Billing** card to restore
write access.
## Manage a pending invitation
Pending invitations appear below the invite form. Select **Resend** to send the
email again or **Revoke** to prevent the recipient from accepting it.
After a recipient accepts, the invitation leaves the pending list and the
person appears in **Members**.
## Change a member's role
An admin opens the menu on another person's row and selects **Make admin** or
**Make member**. Your own row has no role menu, so another admin must change
your role.
A team must keep at least one admin. Workspaces refuses to demote or remove the
only admin and shows:
> A team always needs at least one admin. Make someone else an admin first.
Workspaces may not apply a role change to the other person's open browser
session at once. That session must refresh first.
## Remove a member
Removing a member ends access granted by their membership after Workspaces
refreshes the membership data. Workspaces also gives every organization
workspace the person owns to the admin who removes them. This includes
organization workspaces the person kept private. Personal workspaces and
workspaces in other organizations do not move.
On **Members**, open the menu on the person's row.
Select **Remove from team**.
Confirm **Remove \[name] from the team? They can be re-invited later.**
Workspaces removes the active membership.
An existing browser session may keep organization access until it refreshes.
The person's API keys remain active, but they lose access granted by the
removed membership. Access through a key normally reflects removal within 60
seconds. If Workspaces cannot refresh organization memberships, cached access
may last up to 10 minutes.
Removal does not cancel other access. The person may still open a workspace
that is public, open to anyone with the link, or shared through a guest link
they hold. An admin cannot revoke another person's API keys.
The person also leaves the active-member roster used for future seat
calculations. Workspaces updates an active subscription's seat count after the
membership change.
## Leave a team
Any member can select **Leave team** below the roster. Workspaces returns the
person to **Home** after a successful request.
The only admin cannot leave. Make another member an admin first. When a person
leaves, Workspaces gives their organization workspaces to the remaining admin
who joined the organization first. This includes organization workspaces they
kept private. Their personal workspaces do not move.
## Current roster limit
The **Members** tab shows up to 100 active members and up to 100 invitation
records. A larger organization may not show every member or pending invitation
on this page. Workspaces uses the full active-member list and applies seat
exemptions when it calculates seats. The page limit does not affect that
calculation.
Workspaces loads up to 20 organization memberships into a hosted browser
session. If your account belongs to more organizations, some teams may not
appear or open in that session. The 20-organization browser-session cap does
not apply to API keys. They load up to the first 100 current organization
memberships.
Learn how member removal changes a person's API-key access.
*Reviewed July 22, 2026. Maintained by the Plannotator documentation team.*