Members & invitations
Open People → Members (/admin/members) or People → Invitations (/admin/invitations) to manage organization access. These pages are available to organization owners and admins on tenants with managed membership. When membership comes directly from another identity-provider configuration, manage it there instead.
Members
Section titled “Members”The Members table shows name, email, role, joined date, and whether a GitHub account is linked. Your row carries a You badge. A seat counter shows current usage where the plan has a limit.
Use a row’s three-dot menu for the actions available to your role:
- An owner can Promote to Admin, Demote to Member, or Transfer Ownership to a non-owner.
- An owner or admin can Remove Member for another non-owner. Confirming removes the person from all native teams and revokes organization membership.
Role changes
Section titled “Role changes”Transferring ownership prompts you to confirm the recipient and that your own role will become Admin. If the server reports multiple owners, its warning asks you to transfer ownership to establish a single owner.
You cannot remove yourself from this page, and the removal action is not offered for owners. Transfer ownership before arranging removal; the server also protects the last owner from deletion.
| Organization role | Member management | Invitations |
|---|---|---|
| Member | None | None |
| Admin | Remove other non-owner members | Invite members |
| Owner | Admin actions, plus promotion, demotion, and ownership transfer | Invite members or admins |
Ownership moves by transfer; an invitation cannot directly grant the owner role. Organization administration grants access to Members, Invitations, and Plan. Instance-wide configuration is separately restricted on shared deployments; see Administration.
Send an invitation
Section titled “Send an invitation”- Open People → Invitations.
- Enter an Email address.
- Choose Member, or Admin if you are the owner.
- Click Send Invitation.
The recipient receives an invitation to join the organization with the selected role. The Pending Invitations table shows the email, status, and expiry date. It lists invitations still pending; accepted and expired invitations are not a historical log here.
A pending row’s menu offers Resend to send the invitation again and Revoke to cancel it before acceptance.
Active members plus pending invitations consume seats. At the plan limit, Send Invitation is disabled and an Upgrade your plan link opens the Plan page. Revoke a pending invitation or remove a member to make capacity available without changing plans.
See Plans & seats for limits and trial details.
Identity merge
Section titled “Identity merge”On WorkOS tenants where this service is enabled, server admins can open Identity Merge (/admin/identity-merge) to review legacy GitHub identities whose stored email exactly and unambiguously matches one current account.
The table shows the legacy identity, GitHub login, WorkOS account, matched email, and session counts. Choose Merge, verify both accounts and their evidence, and confirm to give the current account the legacy identity’s history. If the evidence changed since loading, refresh and review again.
This does not link GitHub for future sign-ins. The user still links their own GitHub account through their account settings. Ambiguous matches are not offered for administrative merging.
Related
Section titled “Related”- Setup Server — first-time setup and invitations.
- Teams — groups used for session sharing.