feature request: unlink phone number #2852

Closed
opened 2026-03-13 10:23:33 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @reslear on GitHub (Feb 10, 2026).

Is this suited for github?

  • Yes, this is suited for github

unlink phone number and use other providers for login
for example situation when phone number is dead

Describe the solution you'd like

add route for unlink phone number, maybe with check pass or email otp
check if user has another providers for login

Describe alternatives you've considered

Additional context

No response

Originally created by @reslear on GitHub (Feb 10, 2026). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. unlink phone number and use other providers for login for example situation when phone number is dead ### Describe the solution you'd like add route for unlink phone number, maybe with check pass or email otp check if user has another providers for login ### Describe alternatives you've considered - ### Additional context _No response_
GiteaMirror added the enhancement label 2026-03-13 10:23:33 -05:00
Author
Owner

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

To address your feature request regarding unlinking a phone number, it's been identified that modifying the unlink logic is crucial to check for available authentication methods. Specifically, a user should be able to unlink their phone number, as long as they have verified email or alternative login methods available [1].

Here are the suggested next steps for your feature request:

  1. Develop a Route: Implement a new route for unlinking the phone number with proper authentication checks, such as confirming the user's password or using an email OTP.

  2. Check for Other Providers: Ensure that the unlinking process verifies if the user has alternative authentication methods in place before allowing the unlinking to proceed.

  3. Implement Proper Error Handling: Prepare for cases where no alternative login methods exist by notifying users that unlinking isn't possible without retaining another login method.

Feel free to reach out for further assistance or tag @better-auth-agent if you have additional questions about this feature! How else can I assist you with your Better Auth experience?

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

DiagramDiscordGitHub

Diagram Join Star

@better-auth-agent[bot] commented on GitHub (Feb 10, 2026): To address your feature request regarding unlinking a phone number, it's been identified that modifying the unlink logic is crucial to check for available authentication methods. Specifically, a user should be able to unlink their phone number, as long as they have verified email or alternative login methods available [[1]](https://github.com/better-auth/better-auth/issues/4742). Here are the suggested next steps for your feature request: 1. **Develop a Route**: Implement a new route for unlinking the phone number with proper authentication checks, such as confirming the user's password or using an email OTP. 2. **Check for Other Providers**: Ensure that the unlinking process verifies if the user has alternative authentication methods in place before allowing the unlinking to proceed. 3. **Implement Proper Error Handling**: Prepare for cases where no alternative login methods exist by notifying users that unlinking isn't possible without retaining another login method. Feel free to reach out for further assistance or tag @better-auth-agent if you have additional questions about this feature! How else can I assist you with your Better Auth experience? _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)
Author
Owner

@ping-maxwell commented on GitHub (Feb 11, 2026):

Hello, we're moving all feature requests or enhancement issues over to Github Discussions.

I've went ahead and created the discussion here:
https://github.com/better-auth/better-auth/discussions/7911

@ping-maxwell commented on GitHub (Feb 11, 2026): Hello, we're moving all feature requests or enhancement issues over to Github Discussions. I've went ahead and created the discussion here: https://github.com/better-auth/better-auth/discussions/7911
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#2852