Inline Role-based access control #4254

New Issue

OVERLORD · 2026-02-05T08:21:56+03:00

OVERLORD commented

2026-02-05 08:21:56 +03:00

Originally created by @GHAFRI on GitHub (Oct 2, 2023).

Describe the feature you'd like

I'm looking for a feature that allows for role-based content visibility within a single page. Specifically, I want to have sections of content on the same page that are conditionally displayed based on the logged-in user's role. For instance, a "support" role user should be able to see both "guest" and "support" sections, while a "mod" role user should see "guest", "support", and "mod" sections, all on the same page. This is not about restricting access to entire pages based on roles, but rather displaying or hiding specific sections of content within a page. Does your platform offer such functionality natively, or is there a way to achieve this using custom code?

Describe the benefits this would bring to existing BookStack users

Ability to make one page content without being redundant on multiple pages. For example if there is a documentation that has different level of access, only supports will be able what they can access, while mods can see theirs and supports only.

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

I dont think so

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?

Not using yet, just scoping

Additional context

No response

Originally created by @GHAFRI on GitHub (Oct 2, 2023). ### Describe the feature you'd like I'm looking for a feature that allows for role-based content visibility within a single page. Specifically, I want to have sections of content on the same page that are conditionally displayed based on the logged-in user's role. For instance, a "support" role user should be able to see both "guest" and "support" sections, while a "mod" role user should see "guest", "support", and "mod" sections, all on the same page. This is not about restricting access to entire pages based on roles, but rather displaying or hiding specific sections of content within a page. Does your platform offer such functionality natively, or is there a way to achieve this using custom code? ### Describe the benefits this would bring to existing BookStack users Ability to make one page content without being redundant on multiple pages. For example if there is a documentation that has different level of access, only supports will be able what they can access, while mods can see theirs and supports only. ### Can the goal of this request already be achieved via other means? I dont think so ### Have you searched for an existing open/closed issue? - [X] I have searched for existing issues and none cover my fundamental request ### How long have you been using BookStack? Not using yet, just scoping ### Additional context _No response_

OVERLORD added the 🌔 Out of scope 🔨 Feature Request labels 2026-02-05 08:21:56 +03:00

OVERLORD closed this issue

2026-02-05 08:22:03 +03:00

OVERLORD commented

2026-02-05 08:22:05 +03:00

@ssddanbrown commented on GitHub (Oct 2, 2023):

Hi @GHAFRI,
It would be worth reading through #978 since that is a very similar request, where I also share a potential system using existing in-platform features.
Otherwise, I probably wouldn't look to bring specific permission control/functionality down to this level of detail due to the complexity it introduces, for relatively little demand.

@ssddanbrown commented on GitHub (Oct 2, 2023): Hi @GHAFRI, It would be worth reading through #978 since that is a very similar request, where I also share a potential system using existing in-platform features. Otherwise, I probably wouldn't look to bring specific permission control/functionality down to this level of detail due to the complexity it introduces, for relatively little demand.

OVERLORD commented

2026-02-05 08:22:10 +03:00

@ssddanbrown commented on GitHub (Feb 25, 2025):

Following my response above, I'm going to close this off as out of scope.

@ssddanbrown commented on GitHub (Feb 25, 2025): Following my response above, I'm going to close this off as out of scope.

OVERLORD referenced this issue

2026-02-05 10:29:29 +03:00

[PR #4254] [MERGED] Updated code view block line highlighting to only show on focus #6331

Sign in to join this conversation.