github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 22:32:01 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #9184] tracking: organization invitations (validation, race conditions, channels) #19933

New Issue
Open
opened 2026-04-15 19:18:20 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 19:18:20 -05:00
Owner
Copy Link

Originally created by @gustavovalverde on GitHub (Apr 14, 2026).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/9184

Summary

Invitation handling in the organization plugin breaks in validation, acceptance, and delivery flows. Invite creation allows inconsistent role state. acceptInvitation does not protect against concurrent acceptance. The plugin also lacks a first-class channel model for non-email delivery. Onboarding and bulk invite flows remain incomplete.

Root cause

The invite endpoints pre-date the current role and enrollment surfaces. Validation does not fully enforce role state constraints, and acceptance does not perform one atomic race check. The transport model also treats the recipient as an email address instead of separating channel from identifier. Unauthenticated invite acceptance does not have one defined onboarding path. Bulk and filtered operations exist lower in the stack but are not exposed consistently through the API.

Scope

In: invite validation, acceptInvitation atomicity, channel abstraction (email + phone + custom), unauthenticated recipient onboarding, listInvitations filtering, bulk invite.

Out: dynamic-role typing surface (tracking: admin/org dynamic-role lifecycle). Super-admin cross-org scope (tracking: admin plugin scope + impersonation).

Resolution criteria

  • Invite validation rejects inconsistent role states on create.
  • acceptInvitation is atomic under concurrent accepts.
  • Invites dispatch via email, phone, or a custom channel through one config.
  • Unauthenticated recipients can accept an invite and complete onboarding in the same flow.
  • listInvitations supports filtering.
  • Bulk invite API exists.

Related

  • Dynamic-role invite typing bug #9135 was moved to the dynamic-role lifecycle tracker because the root cause is in the role system, not the invite path.
  • Prior closed context: #6710, #6598, #8691, #7824, #7820, #6576, #7291, #8385.
Originally created by @gustavovalverde on GitHub (Apr 14, 2026). Original GitHub issue: https://github.com/better-auth/better-auth/issues/9184 ## Summary Invitation handling in the organization plugin breaks in validation, acceptance, and delivery flows. Invite creation allows inconsistent role state. `acceptInvitation` does not protect against concurrent acceptance. The plugin also lacks a first-class channel model for non-email delivery. Onboarding and bulk invite flows remain incomplete. ## Root cause The invite endpoints pre-date the current role and enrollment surfaces. Validation does not fully enforce role state constraints, and acceptance does not perform one atomic race check. The transport model also treats the recipient as an email address instead of separating channel from identifier. Unauthenticated invite acceptance does not have one defined onboarding path. Bulk and filtered operations exist lower in the stack but are not exposed consistently through the API. ## Scope **In:** invite validation, `acceptInvitation` atomicity, channel abstraction (email + phone + custom), unauthenticated recipient onboarding, listInvitations filtering, bulk invite. **Out:** dynamic-role typing surface (`tracking: admin/org dynamic-role lifecycle`). Super-admin cross-org scope (`tracking: admin plugin scope + impersonation`). ## Resolution criteria - Invite validation rejects inconsistent role states on create. - `acceptInvitation` is atomic under concurrent accepts. - Invites dispatch via email, phone, or a custom channel through one config. - Unauthenticated recipients can accept an invite and complete onboarding in the same flow. - `listInvitations` supports filtering. - Bulk invite API exists. ## Related - Dynamic-role invite typing bug #9135 was moved to the dynamic-role lifecycle tracker because the root cause is in the role system, not the invite path. - Prior closed context: #6710, #6598, #8691, #7824, #7820, #6576, #7291, #8385.
GiteaMirror added the trackingenhancementorganization labels 2026-04-15 19:18:20 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label enhancement organization tracking
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#19933
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?