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

Organizations: Ability to add custom additional fields #1137

New Issue
Closed
opened 2026-03-13 08:24:28 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-13 08:24:28 -05:00
Owner
Copy Link

Originally created by @Sillyvan on GitHub (Apr 30, 2025).

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

Currently, the organization plugin provides a basic structure for organizations but feels quite minimal. It doesn't offer a built-in way to extend the organization entity with custom fields (e.g., address, phone number, industry type, VAT ID).

In my case the user that signs up will own his own org and that all from 1 sign up form.

Currently this would require:

  • Manually changing the org table schema
  • Create a custom api endpoint that takes in both, user and org data required.
  • Create User and Org with better-auths functionality
  • Insert the additional org data manually with your ORM

The database after hooks dont do the job here because it only allows me to access the user/session data and i dont want to store org infos in both just to pass it down to the hook and then manually insert stuff in my org table

Describe the solution you'd like

Add an additionalField field in the plugin just like with user or session that is also typed in the create function

Describe alternatives you've considered

Maybe a single function that allows coupling both these processes. Main issue is that 1 request should contain the data for both steps, user and org.

Additional context

No response

Originally created by @Sillyvan on GitHub (Apr 30, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. Currently, the organization plugin provides a basic structure for organizations but feels quite minimal. It doesn't offer a built-in way to extend the organization entity with custom fields (e.g., address, phone number, industry type, VAT ID). In my case the user that signs up will own his own org and that all from 1 sign up form. Currently this would require: - Manually changing the org table schema - Create a custom api endpoint that takes in both, user and org data required. - Create User and Org with better-auths functionality - Insert the additional org data manually with your ORM The database after hooks dont do the job here because it only allows me to access the user/session data and i dont want to store org infos in both just to pass it down to the hook and then manually insert stuff in my org table ### Describe the solution you'd like Add an additionalField field in the plugin just like with user or session that is also typed in the create function ### Describe alternatives you've considered Maybe a single function that allows coupling both these processes. Main issue is that 1 request should contain the data for both steps, user and org. ### Additional context _No response_
GiteaMirror commented 2026-03-13 08:24:29 -05:00
Author
Owner
Copy Link

@kdcokenny commented on GitHub (May 1, 2025):

https://github.com/better-auth/better-auth/issues/2036

@kdcokenny commented on GitHub (May 1, 2025): https://github.com/better-auth/better-auth/issues/2036
GiteaMirror commented 2026-03-13 08:24:30 -05:00
Author
Owner
Copy Link

@axelrtgs commented on GitHub (May 28, 2025):

I semi worked around this by using a database hook to deserialize the metadata into a new column. It works great on creation of org but the org plugin only supports hooks on create/delete and not update so I'm not able to keep it updated when changes are made to the metadata.

Since this might be a complicated task to support the additional fields natively perhaps in the interim we can add the ability to use hooks on update so we can implement this manually for now.

@axelrtgs commented on GitHub (May 28, 2025): I semi worked around this by using a database hook to deserialize the metadata into a new column. It works great on creation of org but the org plugin only supports hooks on create/delete and not update so I'm not able to keep it updated when changes are made to the metadata. Since this might be a complicated task to support the additional fields natively perhaps in the interim we can add the ability to use hooks on update so we can implement this manually for now.
GiteaMirror commented 2026-03-13 08:24:30 -05:00
Author
Owner
Copy Link

@felipemotarocha commented on GitHub (May 30, 2025):

This would be very helpful.

@felipemotarocha commented on GitHub (May 30, 2025): This would be very helpful.
GiteaMirror commented 2026-03-13 08:24:30 -05:00
Author
Owner
Copy Link

@Kinfe123 commented on GitHub (Aug 10, 2025):

This should be fixed by now. check this

@Kinfe123 commented on GitHub (Aug 10, 2025): This should be fixed by now. check [this](https://www.better-auth.com/docs/plugins/organization#customizing-the-schema)
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
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#1137
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?