Restrict book to some users #1329

New Issue

OVERLORD · 2026-02-05T00:37:22+03:00

OVERLORD commented

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

Originally created by @mmteyrek on GitHub (Aug 30, 2019).

Describe the feature you'd like
it will be great to have the possibility to restrict the access of a book to some users.

Describe the benefits this feature would bring to BookStack users
when a user create a book, he can chose between 2 possibilities: public / private when public => all users can see the book when private => he has the possibility to choose the users who could see the book (by default he has access :p).

Originally created by @mmteyrek on GitHub (Aug 30, 2019). **Describe the feature you'd like** it will be great to have the possibility to restrict the access of a book to some users. **Describe the benefits this feature would bring to BookStack users** when a user create a book, he can chose between 2 possibilities: public / private when public => all users can see the book when private => he has the possibility to choose the users who could see the book (by default he has access :p).

OVERLORD added the ❓ Question label 2026-02-05 00:37:22 +03:00

OVERLORD closed this issue

2026-02-05 00:37:24 +03:00

OVERLORD commented

2026-02-05 00:37:27 +03:00

@ssddanbrown commented on GitHub (Sep 1, 2019):

Hi @mmteyrek,
You can use the "Permissions" button when viewing a book to set controls about what roles can view/edit/delete the book. Permission on a book will cascade down to chapters and page.

You can create a role (Settings -> Roles) for the specific users you want to target.

@ssddanbrown commented on GitHub (Sep 1, 2019): Hi @mmteyrek, You can use the "Permissions" button when viewing a book to set controls about what roles can view/edit/delete the book. Permission on a book will cascade down to chapters and page. You can create a role (Settings -> Roles) for the specific users you want to target.

OVERLORD commented

2026-02-05 00:37:32 +03:00

@mmteyrek commented on GitHub (Sep 1, 2019):

Hello,
Thank you but unfortunately this is not what I mean.

Actually I'm building a wiki style about a specific subject.

The current user is not an admin so he don't have Access to settings / roles.

Let's imagine this 2 scenarios :
1- I'm writing an article (page) about something and I want to get it validated by someone else before publishing. I give this person on private to see it and then after I put it as public for everyone.

2- I'm writing an article (page) about something really specific and I want to keep between users of my company/ team/ friends.

Actually what i'm suggesting is to put this privacy at page level and not on book..

@mmteyrek commented on GitHub (Sep 1, 2019): Hello, Thank you but unfortunately this is not what I mean. Actually I'm building a wiki style about a specific subject. The current user is not an admin so he don't have Access to settings / roles. Let's imagine this 2 scenarios : 1- I'm writing an article (page) about something and I want to get it validated by someone else before publishing. I give this person on private to see it and then after I put it as public for everyone. 2- I'm writing an article (page) about something really specific and I want to keep between users of my company/ team/ friends. Actually what i'm suggesting is to put this privacy at page level and not on book..

OVERLORD commented

2026-02-05 00:37:37 +03:00

@ssddanbrown commented on GitHub (Dec 12, 2020):

Thanks for explaining @mmteyrek.

The request in #1747 should cover the cases described above so I'm going to close this issue off in favour of that one.

@ssddanbrown commented on GitHub (Dec 12, 2020): Thanks for explaining @mmteyrek. The request in #1747 should cover the cases described above so I'm going to close this issue off in favour of that one.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#1329