[Feature Request] In-page permissions #1509

New Issue

OVERLORD · 2026-02-05T01:05:56+03:00

OVERLORD commented

2026-02-05 01:05:56 +03:00

Originally created by @clafee on GitHub (Jan 28, 2020).

Hello,

I'd love to see an in-page permissions system, where one can choose to hide certain elements (for example passwords, or other "sensitive" data) that not everyone should be able to see.

This would allow documentation made in BookStack to be much more complete.

I hope that other people will find it useful.

Thank you !

Originally created by @clafee on GitHub (Jan 28, 2020). Hello, I'd love to see an in-page permissions system, where one can choose to hide certain elements (for example passwords, or other "sensitive" data) that not everyone should be able to see. This would allow documentation made in BookStack to be much more complete. I hope that other people will find it useful. Thank you !

OVERLORD added the 🔨 Feature Request :cat2:🐈 Possible duplicate labels 2026-02-05 01:05:56 +03:00

OVERLORD closed this issue

2026-02-05 01:05:58 +03:00

OVERLORD commented

2026-02-05 01:06:03 +03:00

@ssddanbrown commented on GitHub (Feb 5, 2020):

Thanks for providing your idea @clafee.
The core functionality wished for in this request has already been requested in issue #978 therefore I'm going to close this to cut-down on duplicates.

Although I can understand your use-case, I probably wouldn't look to implement this due to the fact this would introduce additional very granular control, will make maintenance of editing and permissions system more complex, and will only used by a small portion of BookStack users.

I'll keep the other issue open though for further feedback and so others can voice support.

@ssddanbrown commented on GitHub (Feb 5, 2020): Thanks for providing your idea @clafee. The core functionality wished for in this request has already been requested in issue #978 therefore I'm going to close this to cut-down on duplicates. Although I can understand your use-case, I probably wouldn't look to implement this due to the fact this would introduce additional very granular control, will make maintenance of editing and permissions system more complex, and will only used by a small portion of BookStack users. I'll keep the other issue open though for further feedback and so others can voice support.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#1509