Add roles to owner concept #3873

New Issue

OVERLORD · 2026-02-05T07:44:42+03:00

OVERLORD commented

2026-02-05 07:44:42 +03:00

Originally created by @Coros on GitHub (Jun 21, 2023).

Describe the feature you'd like

Please add the ability set a role as the owner of an object (book/chapter/page). We have many users who add/share content under a single book but only the book owner can modify permissions at the top level. Each user who adds content is allowed to set the permissions on their own individually owned pages. I'd like to set their role, mapped from LDAP, as the owner so that all of the users in that role can manage the book properly. Once enough chapters and pages are created, it will be problematic if the permissions need to be modified by those users. They would have to track down each chapter's owner and get them to make the changes.

If possible, it may also be ideal to enforce ownership. If a role is set as an owner at the book level, all child objects, chapters and pages, should be owned by that role.

Describe the benefits this would bring to existing BookStack users

Allowing a group of users to own objects will allow shared administration of their content. We have large working groups that will rely on this shared ownership to easily manage permissions for their content.

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

unknown. I was unable to find any mention of "shared ownership" in the issues on github. I also didn't see a "hack" for this purpose

Have you searched for an existing open/closed issue?

I have searched for existing issues and none cover my fundemental request

How long have you been using BookStack?

0 to 6 months

Additional context

I don't want to grant the "manage all book, chapter, and pages permissions" right since these users should not be able to see some of the other books in the BookStack.

Originally created by @Coros on GitHub (Jun 21, 2023). ### Describe the feature you'd like Please add the ability set a role as the owner of an object (book/chapter/page). We have many users who add/share content under a single book but only the book owner can modify permissions at the top level. Each user who adds content is allowed to set the permissions on their own individually owned pages. I'd like to set their role, mapped from LDAP, as the owner so that all of the users in that role can manage the book properly. Once enough chapters and pages are created, it will be problematic if the permissions need to be modified by those users. They would have to track down each chapter's owner and get them to make the changes. If possible, it may also be ideal to enforce ownership. If a role is set as an owner at the book level, all child objects, chapters and pages, should be owned by that role. ### Describe the benefits this would bring to existing BookStack users Allowing a group of users to own objects will allow shared administration of their content. We have large working groups that will rely on this shared ownership to easily manage permissions for their content. ### Can the goal of this request already be achieved via other means? unknown. I was unable to find any mention of "shared ownership" in the issues on github. I also didn't see a "hack" for this purpose ### Have you searched for an existing open/closed issue? - [X] I have searched for existing issues and none cover my fundemental request ### How long have you been using BookStack? 0 to 6 months ### Additional context I don't want to grant the "manage all book, chapter, and pages permissions" right since these users should not be able to see some of the other books in the BookStack.

OVERLORD added the 🔨 Feature Request label 2026-02-05 07:44:42 +03:00

OVERLORD closed this issue

2026-02-05 07:44:45 +03:00

OVERLORD commented

2026-02-05 07:44:49 +03:00

@Coros commented on GitHub (Jun 21, 2023):

and just like that I did find another issue for this exact request. Their title was misleading. Closing this request and adding my impact to the existing request.

@Coros commented on GitHub (Jun 21, 2023): and just like that I did find another issue for this exact request. Their title was misleading. Closing this request and adding my impact to the existing request.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#3873