System-Wide/Granular enable/disable for "Reusing Page Content" feature (plus audit?/tracking?) #3029

New Issue

OVERLORD · 2026-02-05T05:58:31+03:00

OVERLORD commented

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

Originally created by @BloodyIron on GitHub (Aug 26, 2022).

Describe the feature you'd like

This is regarding : https://www.bookstackapp.com/docs/user/reusing-page-content/

While this feature is mad lad cool, and I could see being mad useful in a lot of scenarios, it also presents IT Security problems. In that, I am not seeing a way to see when content is referred in this way, and where. Plus also not seeing a way to limit/disable this feature, at various scopes (including system-wide?)

IMO I think it would be beneficial to extend this feature such that:

You can audit all "Reusing Page Content" instances across the whole system, both in which content is sourced and where it is referenced. So that it is easier to see where it may be used poorly/abused.
Enable the ability to disable this feature at all scopes, site-wide/per-shelf/per-book/per-chapter/per-page/etc

I suspect there will be many users that legitimately would like this feature where I am implementing it, but I want to have my cake and eat it too. In that, I think there's sections of our content where this usage is not only reasonable, is valuable. And in other areas it represents a real IT Security threat, as we plan to also have extremely sensitive content in sections, that we cannot have referenced in ways that circumvent security configurations (RBAC, etc). And in its current form it sure does look like access controls can be circumvented with this feature, plus even tracking active links of this nature looks logistically infeasible currently (NIGHTMARE).

Describe the benefits this would bring to existing BookStack users

Increase IT Security features so that access controls can be adhered to, but also make it so it can be used in areas where it is reasonable as a function.

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

Not that I am aware of.

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?

Not using yet, just scoping

Additional context

No response

Originally created by @BloodyIron on GitHub (Aug 26, 2022). ### Describe the feature you'd like This is regarding : https://www.bookstackapp.com/docs/user/reusing-page-content/ While this feature is mad lad cool, and I could see being mad useful in a lot of scenarios, it also presents IT Security problems. In that, I am not seeing a way to see when content is referred in this way, and where. Plus also not seeing a way to limit/disable this feature, at various scopes (including system-wide?) IMO I think it would be beneficial to extend this feature such that: 1. You can audit all "Reusing Page Content" instances across the whole system, both in which content is sourced and where it is referenced. So that it is easier to see where it may be used poorly/abused. 2. Enable the ability to disable this feature at all scopes, site-wide/per-shelf/per-book/per-chapter/per-page/etc I suspect there will be many users that legitimately would like this feature where I am implementing it, but I want to have my cake and eat it too. In that, I think there's sections of our content where this usage is not only reasonable, is valuable. And in other areas it represents a real IT Security threat, as we plan to also have extremely sensitive content in sections, that we cannot have referenced in ways that circumvent security configurations (RBAC, etc). And in its current form it sure does look like access controls can be circumvented with this feature, plus even tracking active links of this nature looks logistically infeasible currently (NIGHTMARE). ### Describe the benefits this would bring to existing BookStack users Increase IT Security features so that access controls can be adhered to, but also make it so it can be used in areas where it is reasonable as a function. ### Can the goal of this request already be achieved via other means? Not that I am aware of. ### 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? Not using yet, just scoping ### Additional context _No response_

OVERLORD added the 🔨 Feature Request label 2026-02-05 05:58:31 +03:00

OVERLORD closed this issue

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

OVERLORD referenced this issue

2026-02-05 10:24:51 +03:00

[PR #3012] [MERGED] Laravel 6 to Laravel 8 Upgrade #6116

OVERLORD referenced this issue

2026-02-05 10:24:57 +03:00

[PR #3029] [MERGED] Laravel 8 shift squash #6120

Sign in to join this conversation.