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

Multiple Teams Membership #909

New Issue
Closed
opened 2026-03-13 08:09:35 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-03-13 08:09:35 -05:00
Owner
Copy Link

Originally created by @OscarMayReal on GitHub (Mar 24, 2025).

Is this suited for github?

  • Yes, this is suited for github

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

teams allow better managment of orgs, but sometimes members need to be in more than one team

Describe the solution you'd like

an option to allow members to be in more than one team, and only be able to see the teams they are a member of

Describe alternatives you've considered

creating a seperate database that manages access permissions for each team

Additional context

No response

Originally created by @OscarMayReal on GitHub (Mar 24, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. teams allow better managment of orgs, but sometimes members need to be in more than one team ### Describe the solution you'd like an option to allow members to be in more than one team, and only be able to see the teams they are a member of ### Describe alternatives you've considered creating a seperate database that manages access permissions for each team ### Additional context _No response_
GiteaMirror added the enhancement label 2026-03-13 08:09:35 -05:00
GiteaMirror commented 2026-03-13 08:09:36 -05:00
Author
Owner
Copy Link

@i-am-rad commented on GitHub (Mar 26, 2025):

Yes I want this as well. Members currently have only one spot for a teamId. Maybe a flag for multi-team support and a team_member table.

@i-am-rad commented on GitHub (Mar 26, 2025): Yes I want this as well. Members currently have only one spot for a teamId. Maybe a flag for multi-team support and a team_member table.
GiteaMirror commented 2026-03-13 08:09:36 -05:00
Author
Owner
Copy Link

@XanderXVD commented on GitHub (Apr 14, 2025):

The teams function is great for bringing structure within an organization by grouping users logically. However, the current setup limits users to a single team through a direct teamId field on the user, which restricts flexibility.

Wouldn't this be better addressed by introducing a join table — e.g. teams_members — that maps users to teams in a many-to-many relationship? This way, users can be part of multiple teams, and permission checks can be scoped accordingly to the teams they belong to.

This approach would also make it easier to extend with role-based access per team in the future if needed.

@XanderXVD commented on GitHub (Apr 14, 2025): The teams function is great for bringing structure within an organization by grouping users logically. However, the current setup limits users to a single team through a direct `teamId` field on the user, which restricts flexibility. Wouldn't this be better addressed by introducing a join table — e.g. `teams_members` — that maps users to teams in a many-to-many relationship? This way, users can be part of multiple teams, and permission checks can be scoped accordingly to the teams they belong to. This approach would also make it easier to extend with role-based access per team in the future if needed.
GiteaMirror commented 2026-03-13 08:09:36 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Aug 3, 2025):

Hi, @OscarMayReal. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested support for members to belong to multiple teams within an organization with restricted visibility.
  • Community members like i-am-rad and XanderXVD support this and suggest implementing a many-to-many relationship via a join table (e.g., teams_members).
  • This approach would allow multi-team membership and scoped permission checks.
  • The idea is favored for its flexibility and potential for future role-based access control enhancements.
  • The issue remains unresolved with broad positive community interest.

Next Steps:

  • Please let me know if this feature is still relevant to your use case with the latest version of better-auth by commenting on this issue.
  • If I don’t hear back within 7 days, I will automatically close the issue to keep the backlog manageable.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 3, 2025): Hi, @OscarMayReal. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested support for members to belong to multiple teams within an organization with restricted visibility. - Community members like i-am-rad and XanderXVD support this and suggest implementing a many-to-many relationship via a join table (e.g., teams_members). - This approach would allow multi-team membership and scoped permission checks. - The idea is favored for its flexibility and potential for future role-based access control enhancements. - The issue remains unresolved with broad positive community interest. **Next Steps:** - Please let me know if this feature is still relevant to your use case with the latest version of better-auth by commenting on this issue. - If I don’t hear back within 7 days, I will automatically close the issue to keep the backlog manageable. Thanks for your understanding and contribution!
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
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#909
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?