Skip to content

API endpoint to get all custom-permissions of role #5613

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
Rob787 opened this issue May 16, 2025 · 0 comments
Open
1 task done

API endpoint to get all custom-permissions of role #5613

Rob787 opened this issue May 16, 2025 · 0 comments

Comments

@Rob787
Copy link

Rob787 commented May 16, 2025

Describe the feature you'd like

Due to the limitation that OIDC tokens cannot be used yet to authenticate to the API (will submit a separate feature request), we are trying to integrate content of our Bookstack environment in an web application via another way.

In this case we created a "service-user" with API token, that can fetch content via the API. However, we are having one challenge: determine the content a certain role has access to.

Currently the only endpoint provided is the: https://bookstack.bassopaolo.com/api/docs#content-permissions-read
For which we always need to provide a specific shelf/book or pageid.

However, I would like to request an endpoint, where I can, based on role_id, get a list of all content permissions. Such that when requesting a list of shelves, we can filter out the shelves a role is entitled to to see for instance.

Describe the benefits this would bring to existing BookStack users

Easier to determine if user is allowed to see specific list of content based on role.

Can the goal of this request already be achieved via other means?

Yes, by looping through requested list of content and request content-permission for each specific shelf/book/page.

Have you searched for an existing open/closed issue?

  • I have searched for existing issues and none cover my fundamental request

How long have you been using BookStack?

1 to 5 years

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant