Unable to save Admin system permissions #670

New Issue

OVERLORD · 2026-02-04T21:46:13+03:00

OVERLORD commented

2026-02-04 21:46:13 +03:00

Originally created by @doc-jay on GitHub (May 11, 2018).

BookStack Version: .22-dev
PHP Version: 7.0.30
MySQL Version: 5.6

When I edit the admin role and deselect 'Manage permissions on own book, chapter & pages' and click 'Save', I would expect that setting to remain deselected.

When I edit the admin role and deselect 'Manage permissions on own book, chapter & pages' under system permissions' for the role and click 'save', it is not saved after I edit the role again to double check it.

GOAL:
What I am trying to accomplish is having private books for users that members of the admin group cannot see.

*Steps to reproduce

Edit the admin role
deselect 'Manage permissions on own book, chapter & pages'
click 'save'
edit the admin role
check if settings were saved.

Originally created by @doc-jay on GitHub (May 11, 2018). * BookStack Version: .22-dev * PHP Version: 7.0.30 * MySQL Version: 5.6 When I edit the admin role and deselect 'Manage permissions on own book, chapter & pages' and click 'Save', I would expect that setting to remain deselected. When I edit the admin role and deselect 'Manage permissions on own book, chapter & pages' under system permissions' for the role and click 'save', it is not saved after I edit the role again to double check it. GOAL: **What I am trying to accomplish is having private books for users that members of the admin group cannot see.** *Steps to reproduce 1. Edit the admin role 2. deselect 'Manage permissions on own book, chapter & pages' 3. click 'save' 4. edit the admin role 5. check if settings were saved.

OVERLORD added the ☕ Open to discussion label 2026-02-04 21:46:13 +03:00

OVERLORD closed this issue

2026-02-04 21:46:15 +03:00

OVERLORD commented

2026-02-04 21:46:23 +03:00

@ssddanbrown commented on GitHub (May 12, 2018):

Hi @doc-jay, Thanks for opening this issue.
What you're reporting here is very much a purpose-built feature of the system, Admin permissions cannot be limited. This is to allow an admin the ability to always view, edit and help with supporting users within the BookStack instance. In addition, It allows us during development to allocate new features to those admin users without worrying.

You could rename the admin role to something along the lines of super-user, Have that role majorly limited and create a new admin role with restricted permissions.

@ssddanbrown commented on GitHub (May 12, 2018): Hi @doc-jay, Thanks for opening this issue. What you're reporting here is very much a purpose-built feature of the system, Admin permissions cannot be limited. This is to allow an admin the ability to always view, edit and help with supporting users within the BookStack instance. In addition, It allows us during development to allocate new features to those admin users without worrying. You could rename the admin role to something along the lines of `super-user`, Have that role majorly limited and create a new `admin` role with restricted permissions.

OVERLORD commented

2026-02-04 21:46:31 +03:00

@doc-jay commented on GitHub (May 14, 2018):

okay, thanks for the update. I appreciate it.

@doc-jay commented on GitHub (May 14, 2018): okay, thanks for the update. I appreciate it.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#670