Team and Invitations
Manage organization members, roles, and invitation lifecycle in authenticated deployments.
Route Scope
Team management route:
/$orgSlug/team
This page is organization-scoped and intended for authenticated mode.
Role Model
Typical roles surfaced in the UI:
- Owner
- Admin
- Member
Use least privilege by default and reserve owner/admin for operational and governance responsibilities.
Invitation email setup
Self-hosted deployments need RESEND_API_KEY and an EMAIL_FROM address on a verified sender
domain to deliver invitation emails. Creating an invitation does not guarantee email delivery
when an email provider is unconfigured. See
Environment Variables.
Invitation Lifecycle
Core operations:
- send invite to email with selected role
- resend pending invite
- cancel/revoke invite
- invited user accepts through invite route
Invite acceptance route:
/invite/$invitationId
Backend public invite read endpoint:
GET /api/invitations/:id
Member Management
Available actions include:
- list active members
- remove member from org
- inspect pending invitation counts
Operational Guidance
- Keep at least two admins/owners for continuity.
- Periodically clean stale pending invites.
- Rotate roles when personnel changes happen.