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

Admin Plugin: Check multiple separate permission groups on one request. #1933

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

Originally created by @frixou89 on GitHub (Sep 15, 2025).

Is this suited for github?

  • Yes, this is suited for github

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

My problem at the moment is that I have a user portal that needs to use permissions to show/hide sidebar menu items.

Currently, for each menu item we make a separate request to check for that permission like so

authClient.admin.hasPermission({ permissions: {clients: ['read']} })
authClient.admin.hasPermission({ permissions: {projects: ['read']} })
...

These return a { success: boolean } response.

Describe the solution you'd like

Following the issue I described above, it would be more efficient if there was a way to check permissions 1-to-1.

For example something like this.

authClient.admin.hasPermission({
  permissions: [
    { projects: ['read'] },
    { users: ['read'], account: ['edit'] }
  ]
});

And retrieve a response like an array of the corresponding matches requested.

{
  "success": [true, false]
}

Describe alternatives you've considered

The only alternative right now is to make several API calls for each permission group which causes too many API calls.

Additional context

No response

Originally created by @frixou89 on GitHub (Sep 15, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. My problem at the moment is that I have a user portal that needs to use permissions to show/hide sidebar menu items. Currently, for each menu item we make a separate request to check for that permission like so ```ts authClient.admin.hasPermission({ permissions: {clients: ['read']} }) authClient.admin.hasPermission({ permissions: {projects: ['read']} }) ... ``` These return a `{ success: boolean }` response. ### Describe the solution you'd like Following the issue I described above, it would be more efficient if there was a way to check permissions 1-to-1. For example something like this. ```ts authClient.admin.hasPermission({ permissions: [ { projects: ['read'] }, { users: ['read'], account: ['edit'] } ] }); ``` And retrieve a response like an array of the corresponding matches requested. ```json { "success": [true, false] } ``` ### Describe alternatives you've considered The only alternative right now is to make several API calls for each permission group which causes too many API calls. ### Additional context _No response_
GiteaMirror added the enhancementplugin labels 2026-03-13 09:13:24 -05:00
GiteaMirror commented 2026-03-13 09:13:25 -05:00
Author
Owner
Copy Link

@hieudien14310 commented on GitHub (Sep 20, 2025):

In ur case, i think what you need is to fetch all the permissions from all the roles that a user has, and then use that to display the corresponding menu items based on roles.
If true, you can create a separate api (eg: /list-access-control) to retrieve information in the roles management section on the backend where you have configured it.

@hieudien14310 commented on GitHub (Sep 20, 2025): In ur case, i think what you need is to fetch all the permissions from all the roles that a user has, and then use that to display the corresponding menu items based on roles. If true, you can create a separate api (eg: `/list-access-control`) to retrieve information in the roles management section on the backend where you have configured it.
GiteaMirror commented 2026-03-13 09:13:25 -05:00
Author
Owner
Copy Link

@frixou89 commented on GitHub (Sep 20, 2025):

What I ended up with was to include the user role permissions in the customSession hook. That way I can check manually for permissions without any extra api calls. Something like that

customSession(async ({ user, session }) => {
  ...
  const userRole = (user.userRole || 'user').split(',')[0];
  const permissions =
    rolesMap[userRole as keyof typeof rolesMap]?.statements || {};

  return {
    ...userMeta,
    permissions,
  };
}

And in my sidebar component I simply check if the permission is there

items: [
  {
    ...
    hide: !permissions?.expert?.includes('list'),
  },
  {
    ...
    hide: !permissions?.client?.includes('list'),
  },
  {
    ...
    hide: !permissions?.appointment?.includes('list'),
  },
],
@frixou89 commented on GitHub (Sep 20, 2025): What I ended up with was to include the user role permissions in the `customSession` hook. That way I can check manually for permissions without any extra api calls. Something like that ```ts customSession(async ({ user, session }) => { ... const userRole = (user.userRole || 'user').split(',')[0]; const permissions = rolesMap[userRole as keyof typeof rolesMap]?.statements || {}; return { ...userMeta, permissions, }; } ``` And in my sidebar component I simply check if the permission is there ```ts items: [ { ... hide: !permissions?.expert?.includes('list'), }, { ... hide: !permissions?.client?.includes('list'), }, { ... hide: !permissions?.appointment?.includes('list'), }, ], ```
GiteaMirror commented 2026-03-13 09:13:25 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Dec 20, 2025):

Hi, @frixou89. 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 an enhancement to the Admin Plugin to check multiple permission groups in a single request for better efficiency.
  • A contributor suggested fetching all permissions from user roles and creating a dedicated API endpoint for role information.
  • You shared a workaround by including user role permissions in a customSession hook to avoid extra API calls.
  • This workaround allows manual permission checks on the frontend without multiple requests and was well received.
  • The issue was effectively resolved with this approach improving efficiency.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of better-auth by commenting here.
  • If I don’t hear from you within 7 days, this issue will be automatically closed.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Dec 20, 2025): Hi, @frixou89. 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 an enhancement to the Admin Plugin to check multiple permission groups in a single request for better efficiency. - A contributor suggested fetching all permissions from user roles and creating a dedicated API endpoint for role information. - You shared a workaround by including user role permissions in a customSession hook to avoid extra API calls. - This workaround allows manual permission checks on the frontend without multiple requests and was well received. - The issue was effectively resolved with this approach improving efficiency. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of better-auth by commenting here. - If I don’t hear from you within 7 days, this issue will be automatically closed. Thanks for your understanding and contribution!
GiteaMirror commented 2026-03-13 09:13:26 -05:00
Author
Owner
Copy Link

@Gbuomprisco commented on GitHub (Dec 31, 2025):

The suggested workaround wouldn't work with DAC. I believe the original suggestion in this post would be extremely useful to everyone - and honestly, not too complex to implement.

@Gbuomprisco commented on GitHub (Dec 31, 2025): The suggested workaround wouldn't work with DAC. I believe the original suggestion in this post would be extremely useful to everyone - and honestly, not too complex to implement.
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 plugin
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#1933
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?