Owners can remove any teammate from the team page. This article covers what that actually changes — which is both more immediate and less destructive than people expect.
What changes immediately
Their access to the workspace ends, and their seat is freed — if you were at your seat limit, you can invite someone else straight away.
Their login itself is untouched. One account can belong to several workspaces, so removing someone from yours doesn't affect any other workspace they're part of.
What stays
Everything they created stays. Prompts, tags, competitors, aliases — all of it belongs to the workspace, not to the person who added it. Removing the teammate who built your prompt list doesn't touch the prompt list, and no history is lost.
One offboarding habit worth having
Teammates can create their own API keys, and owners can see and revoke every member's keys. When someone leaves, make the API keys page part of the same checklist as the removal itself, and revoke anything that shouldn't stay active — an API key is a credential, and offboarding is exactly the moment to tidy them.
The two removals that aren't allowed
You can't remove yourself. Leaving a workspace you own means transferring it, not deleting your own access.
You can't remove the last owner. A workspace always needs one person who can manage billing and the team.
Removing a pending invite
Same action, same place. Removing an invite that hasn't been accepted invalidates the link that was emailed and frees the seat it was holding — worth remembering, since invites count against your seats from the moment they're sent, not from acceptance.
