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 #691] Q: hasPermission - role #17014

New Issue
Closed
opened 2026-04-15 14:57:33 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-15 14:57:33 -05:00
Owner
Copy Link

Originally created by @impactvelocity on GitHub (Nov 29, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/691

Great project!

Quick question for the organizaiton.hasPermission

https://www.better-auth.com/docs/plugins/organization#access-control-usage

const canCreateProject = await client.organization.hasPermission({
role: "admin",
permission: {
project: ["create"]
}
})

It seems to work with or without passing the role. I wonder why you need to pass the role? Wouldn't the role be inherited from the active user? Which it seems to be doing.

So I am just passing the permissions, and that is working.

Just wanted to ask and make sure I am understanding it.

Originally created by @impactvelocity on GitHub (Nov 29, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/691 Great project! Quick question for the organizaiton.hasPermission https://www.better-auth.com/docs/plugins/organization#access-control-usage const canCreateProject = await client.organization.hasPermission({ role: "admin", permission: { project: ["create"] } }) It seems to work with or without passing the role. I wonder why you need to pass the role? Wouldn't the role be inherited from the active user? Which it seems to be doing. So I am just passing the permissions, and that is working. Just wanted to ask and make sure I am understanding it.
GiteaMirror added the locked label 2026-04-15 14:57:33 -05:00
GiteaMirror commented 2026-04-15 14:57:34 -05:00
Author
Owner
Copy Link

@salvinoto commented on GitHub (Dec 1, 2024):

As far as I'm aware I believe the example is showing you can do either or. Meaning you can pass in the role you want it to be OR the specific permission.

<!-- gh-comment-id:2510309270 --> @salvinoto commented on GitHub (Dec 1, 2024): As far as I'm aware I believe the example is showing you can do either or. Meaning you can pass in the role you want it to be OR the specific permission.
GiteaMirror commented 2026-04-15 14:57:35 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Dec 2, 2024):

The docs were wrong. it doesn't require roles.

<!-- gh-comment-id:2511581352 --> @Bekacru commented on GitHub (Dec 2, 2024): The docs were wrong. it doesn't require roles.
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#17014
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?