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

[GH-ISSUE #496] Feature: Teams for Organizations #16926

New Issue
Closed
opened 2026-04-15 14:53:22 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-15 14:53:22 -05:00
Owner
Copy Link

Originally created by @gixnluca on GitHub (Nov 11, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/496

Is your feature request related to a problem? Please describe.
Organization with tens or hundreds of members will need to become more structured. It's very unlikely that all members need to be able to see everything.

Describe the solution you'd like

  • An admin would be able to create Teams and specify some basic attributes like a logo/icon/emoji/color, description and wether a team is invite-only or open (free for any org member to join).
  • A member would join the Organization and then a Team based on either Invitation (specify which Team within the org when sending invite) or freely (pick any Team within the org).

When it comes to roles, we could partially inherit from Organization level:

  • Organization admins will have the option to create and join any team with admin permissions.
  • Organization members can only join if invited or if the team is open.

And have some Team-specific roles:

  • Organization members can be promoted to Team admins/leads while still being members at org-level.

Describe alternatives you've considered
Nothing really, there needs to be a parent-children relationship and cannot be achieved with multiple orgs.

Additional context
Linear (https://linear.app) handles it very nicely in my opinion. Organization can have many teams, Members are related first to the Oganization and then to as many Teams as needed.

Originally created by @gixnluca on GitHub (Nov 11, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/496 **Is your feature request related to a problem? Please describe.** Organization with tens or hundreds of members will need to become more structured. It's very unlikely that all members need to be able to see everything. **Describe the solution you'd like** - An admin would be able to create Teams and specify some basic attributes like a logo/icon/emoji/color, description and wether a team is invite-only or open (free for any org member to join). - A member would join the Organization and then a Team based on either Invitation (specify which Team within the org when sending invite) or freely (pick any Team within the org). When it comes to roles, we could partially inherit from Organization level: - Organization admins will have the option to create and join any team with admin permissions. - Organization members can only join if invited or if the team is open. And have some Team-specific roles: - Organization members can be promoted to Team admins/leads while still being members at org-level. **Describe alternatives you've considered** Nothing really, there needs to be a parent-children relationship and cannot be achieved with multiple orgs. **Additional context** Linear (https://linear.app) handles it very nicely in my opinion. Organization can have many teams, Members are related first to the Oganization and then to as many Teams as needed.
GiteaMirror added the locked label 2026-04-15 14:53:22 -05:00
GiteaMirror commented 2026-04-15 14:53:23 -05:00
Author
Owner
Copy Link

@gixnluca commented on GitHub (Feb 18, 2025):

@Bekacru you're the best!

<!-- gh-comment-id:2666951139 --> @gixnluca commented on GitHub (Feb 18, 2025): @Bekacru you're the best!
GiteaMirror commented 2026-04-15 14:53:23 -05:00
Author
Owner
Copy Link

@AndiCrisan commented on GitHub (Feb 28, 2025):

Excited for this one to get through!

<!-- gh-comment-id:2691156696 --> @AndiCrisan commented on GitHub (Feb 28, 2025): Excited for this one to get through!
GiteaMirror commented 2026-04-15 14:53:24 -05:00
Author
Owner
Copy Link

@khabubuphathu commented on GitHub (Apr 30, 2025):

I wish there was a way to make an organization member to be part of many teams.

<!-- gh-comment-id:2842480199 --> @khabubuphathu commented on GitHub (Apr 30, 2025): I wish there was a way to make an organization member to be part of many teams.
GiteaMirror commented 2026-04-15 14:53:24 -05:00
Author
Owner
Copy Link

@rozazhaidenova1980-create commented on GitHub (Oct 26, 2025):

darкаura

<!-- gh-comment-id:3448302602 --> @rozazhaidenova1980-create commented on GitHub (Oct 26, 2025): darкаura
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 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#16926
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?