People, roles and teams
Available to organisation owners and admins on workspaces with managed membership. Where membership comes from an identity provider instead, manage it there; the console then shows no invitations or native teams
Members
Section titled “Members”People → Members lists everyone with name, email, role, join date and whether GitHub is linked; your row has a You badge; a seat counter shows usage against the plan. The row menu offers what your role allows:
- An owner can Promote to Admin, Demote to Member, or Transfer Ownership to a non-owner. Transferring makes you an admin; the server protects the last owner
- An owner or admin can Remove Member for a non-owner, which also drops them from every team. An owner can also remove another owner
You cannot remove yourself, and the server protects the last owner
| Role | Members | Invitations |
|---|---|---|
| Member | — | — |
| Admin | Remove non-owner members | Invite members |
| Owner | Promote, demote, transfer ownership, remove any other member | Invite members or admins |
Invitations
Section titled “Invitations”People → Invitations: email, role, Send Invitation. The pending table shows status and expiry (seven days); the row menu has Resend and Revoke. Accepted and expired invitations are not listed; it is not a log
Active members plus pending invitations consume seats. At the limit, Send Invitation is disabled with a link to the Plan page; revoke a pending invitation or remove a member to free one. Plan and seats
People → Teams creates native teams: named groups that session sharing, memory audiences and knowledge audiences can name. Create one from the New Team card; each team card has Manage members, Rename and Delete team (permanent, confirmed). Add members by name or email; only active organisation members can be added, and a person can be in several teams
Team grants resolve against live membership: adding someone to a team gives them every session shared with it, and removing them takes it away, with nothing to re-share. Removing someone from the organisation removes them from every team first
Identity merge
Section titled “Identity merge”On workspaces that moved from GitHub sign-in to single sign-on, Identity Merge lets a server admin give a current account the history of a legacy GitHub identity whose stored email matches it exactly and unambiguously. Review both accounts and their session counts before confirming; ambiguous matches are not offered. The user still links GitHub for future commits from their own account settings