Add more tables using neon.tech
Migrating users from supabase to better-auth, without downtime
Add activeOrganizationSlug in session data
How to access email in `verify-email` route when verifying email OTP?
requireEmailVerification: true
and trigger an emailOTP
to be sent upon user creation. This sends a user to a /verify-email
route where they can insert their OTP. However, my server here doesn't know the email address of the user so cannot verify the OTP because it doesn't know what user/email to associate it with.
How can I best solve this? I thought of passing the email as a query param, but that's unsafe. Any tips? Maybe the one-time token? Problem is that user needs to have verified their email before they can log in....Change email using OTP
[Admin Plugin] Default User logic
Best way to create an organization
[ Stripe ] Is there a way to cancel a user subscription when the user deletes their account?
Change Email Expiry

generateId
Where to pass `forceAllowId` ?
User
table by passing an existing user ID instead of letting the system auto-generate one. I found the documentation at https://www.better-auth.com/docs/guides/create-a-db-adapter for creating a custom adapter, but the section about user ID generation is unclear:
additionally, it's possible to pass forceAllowId as a parameter to the create method, which allows id to be provided in the data object. We handle forceAllowId internally, so you don't need to worry about it.
additionally, it's possible to pass forceAllowId as a parameter to the create method, which allows id to be provided in the data object. We handle forceAllowId internally, so you don't need to worry about it.
Different server for auth and frontend

Is it possible to define custom methods for storing and finding users?
Go backend
Auth endpoints returning 404 behind Cloudflare Tunnel
Not found: /api/auth/get-session
Not found: /api/auth/sign-in/social
Not found: /api/auth/get-session
Not found: /api/auth/sign-in/social
organizationClient incompatible type on Vue
Help: banUser expects string userId but my DB uses number — what's the best way to handle this?
`emailVerified` as datetime
error thrown in better auth plugin is not captured by better-auth configured logger