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

[PR #5718] feat: team roles #14422

New Issue
Open
opened 2026-04-13 09:28:00 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 09:28:00 -05:00
Owner
Copy Link

Original Pull Request: https://github.com/better-auth/better-auth/pull/5718

State: open
Merged: No

Summary

Extends the organization plugin to support team-level roles, enabling fine-grained access control within teams. Team members can now be assigned specific roles (e.g., admin, member, viewer) with customizable permissions.

💡 Usage Example

const auth = betterAuth({
  plugins: [
    organization({
      teamRoles: {
        roles: {
          admin: { permissions: ["teamMember:*"] },
          member: { permissions: ["teamMember:read"] },
          viewer: { permissions: [] }
        },
        defaultRole: "member",
        creatorRole: "admin"
      }
    })
  ]
})

Running Tests

pnpm i
cd packages/better-auth
pnpm test src/plugins/organization/team-roles.test.ts

Summary by cubic

Adds team-level roles to the organization plugin so teams can assign and enforce roles per member. Introduces APIs to update and read team member roles, with defaults and creator-as-admin behavior.

  • New Features
    • Configurable team roles via options.teams.teamRoles (roles, defaultRole=member, creatorRole=admin).
    • Team creators are automatically added as team admins.
    • addTeamMember accepts an optional role and falls back to default when omitted.
    • New endpoints: POST /organization/update-team-member-role and GET /organization/get-team-member.
    • hasPermission accepts an optional teamId to check team-scoped permissions, falling back to org role when not a team member.
    • Access control includes teamMember permissions (create, update, delete, read) and new error codes for role updates and visibility.
    • Team member schema now includes a role field (default "member").

Written for commit 0ef88710bf. Summary will update automatically on new commits.

**Original Pull Request:** https://github.com/better-auth/better-auth/pull/5718 **State:** open **Merged:** No --- ## Summary Extends the organization plugin to support team-level roles, enabling fine-grained access control within teams. Team members can now be assigned specific roles (e.g., admin, member, viewer) with customizable permissions. ## 💡 Usage Example ```typescript const auth = betterAuth({ plugins: [ organization({ teamRoles: { roles: { admin: { permissions: ["teamMember:*"] }, member: { permissions: ["teamMember:read"] }, viewer: { permissions: [] } }, defaultRole: "member", creatorRole: "admin" } }) ] }) ``` ## Running Tests ``` pnpm i cd packages/better-auth pnpm test src/plugins/organization/team-roles.test.ts ``` <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Adds team-level roles to the organization plugin so teams can assign and enforce roles per member. Introduces APIs to update and read team member roles, with defaults and creator-as-admin behavior. - **New Features** - Configurable team roles via options.teams.teamRoles (roles, defaultRole=member, creatorRole=admin). - Team creators are automatically added as team admins. - addTeamMember accepts an optional role and falls back to default when omitted. - New endpoints: POST /organization/update-team-member-role and GET /organization/get-team-member. - hasPermission accepts an optional teamId to check team-scoped permissions, falling back to org role when not a team member. - Access control includes teamMember permissions (create, update, delete, read) and new error codes for role updates and visibility. - Team member schema now includes a role field (default "member"). <sup>Written for commit 0ef88710bf5ac06690bbc5a1f8bf16f06a52cb7f. Summary will update automatically on new commits.</sup> <!-- End of auto-generated description by cubic. -->
GiteaMirror added the pull-request label 2026-04-13 09:28:00 -05:00
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 pull-request
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#14422
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?