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

[GH-ISSUE #2323] metadata/additionalFields for Teams in Organization #9148

New Issue
Closed
opened 2026-04-13 04:30:30 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-13 04:30:30 -05:00
Owner
Copy Link

Originally created by @asterssk on GitHub (Apr 16, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/2323

Is this suited for github?

  • Yes, this is suited for github

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

No response

Describe the solution you'd like

a metadata column in Teams table.

Describe alternatives you've considered

None

Additional context

No response

Originally created by @asterssk on GitHub (Apr 16, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/2323 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. _No response_ ### Describe the solution you'd like a metadata column in Teams table. ### Describe alternatives you've considered None ### Additional context _No response_
GiteaMirror added the enhancementlocked labels 2026-04-13 04:30:30 -05:00
GiteaMirror commented 2026-04-13 04:30:32 -05:00
Author
Owner
Copy Link

@Kinfe123 commented on GitHub (Apr 21, 2025):

you can use the organization metadata field along with team details that you want to store

<!-- gh-comment-id:2818233703 --> @Kinfe123 commented on GitHub (Apr 21, 2025): you can use the organization metadata field along with team details that you want to store
GiteaMirror commented 2026-04-13 04:30:34 -05:00
Author
Owner
Copy Link

@xn1cklas commented on GitHub (Jul 14, 2025):

It would actually be great to have this. It could be implemented like the additionalFields prop on the user table in the auth config.

<!-- gh-comment-id:3070151771 --> @xn1cklas commented on GitHub (Jul 14, 2025): It would actually be great to have this. It could be implemented like the additionalFields prop on the user table in the auth config.
GiteaMirror commented 2026-04-13 04:30:36 -05:00
Author
Owner
Copy Link

@ping-maxwell commented on GitHub (Aug 11, 2025):

Hello, this is now a feature.

<!-- gh-comment-id:3176321821 --> @ping-maxwell commented on GitHub (Aug 11, 2025): Hello, this is now a feature.
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#9148
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?