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

[GH-ISSUE #7820] Organization invites: support SMS invites or allow skipping invite email #28240

New Issue
Closed
opened 2026-04-17 19:41:39 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-17 19:41:39 -05:00
Owner
Copy Link

Originally created by @maxvaljan on GitHub (Feb 6, 2026).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/7820

Feature request

When inviting members to an organization, invites currently rely on email only.

Please add one of these options:

  1. Support inviting members via SMS (phone number)
  2. At minimum, make sending the invite email optional (e.g., sendEmail: false) so apps can deliver invites through custom channels (SMS, WhatsApp, in-app, etc.)

Why this is needed

Some products use phone-based onboarding and don't have a reliable email for every user. Requiring email delivery for org invites blocks these flows.

Suggested API direction

  • Accept phone as an invite target (or a generic identifier)
  • Add a flag to disable built-in email dispatch
  • Return invite metadata/token so developers can send the invite through their own provider

Expected result

Developers can keep Better Auth invitation logic, while controlling delivery channel and UX.

Originally created by @maxvaljan on GitHub (Feb 6, 2026). Original GitHub issue: https://github.com/better-auth/better-auth/issues/7820 ### Feature request When inviting members to an organization, invites currently rely on email only. Please add one of these options: 1. Support inviting members via SMS (phone number) 2. At minimum, make sending the invite email optional (e.g., `sendEmail: false`) so apps can deliver invites through custom channels (SMS, WhatsApp, in-app, etc.) ### Why this is needed Some products use phone-based onboarding and don't have a reliable email for every user. Requiring email delivery for org invites blocks these flows. ### Suggested API direction - Accept phone as an invite target (or a generic identifier) - Add a flag to disable built-in email dispatch - Return invite metadata/token so developers can send the invite through their own provider ### Expected result Developers can keep Better Auth invitation logic, while controlling delivery channel and UX.
GiteaMirror added the lockedenhancement labels 2026-04-17 19:41:39 -05:00
GiteaMirror commented 2026-04-17 19:41:40 -05:00
Author
Owner
Copy Link

@better-auth-agent[bot] commented on GitHub (Feb 6, 2026):

Thank you for your feature request regarding organization invites! Currently, Better Auth supports inviting members only via email. There is an open issue discussing the addition of SMS invitations or the option to skip sending an invite email, which highlights the need for improved onboarding experiences for applications that primarily utilize phone-based methods [1], [2].

To move this forward, I recommend participating in the discussion on the GitHub issue, where you can express your support for this feature and track any updates. In the meantime, would utilizing alternate communication methods for inviting users, such as sending and managing invitations through your own system, work for you? Let me know if you have more questions or ideas!

If you need more help, tag @better-auth-agent in a comment so I can respond.

Diagram • Discord • GitHub

Diagram Join Star

<!-- gh-comment-id:3858663848 --> @better-auth-agent[bot] commented on GitHub (Feb 6, 2026): Thank you for your feature request regarding organization invites! Currently, Better Auth supports inviting members only via email. There is an open issue discussing the addition of SMS invitations or the option to skip sending an invite email, which highlights the need for improved onboarding experiences for applications that primarily utilize phone-based methods [[1]](https://www.better-auth.com/docs/plugins/organization), [[2]](https://github.com/better-auth/better-auth/issues/6610). To move this forward, I recommend participating in the discussion on the GitHub issue, where you can express your support for this feature and track any updates. In the meantime, would utilizing alternate communication methods for inviting users, such as sending and managing invitations through your own system, work for you? Let me know if you have more questions or ideas! _If you need more help, tag @better-auth-agent in a comment so I can respond._ <!-- bot:webhook reply v1 --> [Diagram](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) • [Discord](https://discord.gg/better-auth) • [GitHub](https://github.com/better-auth/better-auth) [![Diagram](https://img.shields.io/badge/Diagram-2b3137?style=flat-square)](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) [![Join](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&style=flat-square)](https://discord.gg/better-auth) [![Star](https://img.shields.io/badge/star-181717?logo=github&logoColor=white&style=flat-square)](https://github.com/better-auth/better-auth)
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 locked
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#28240
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?