mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-05-04 18:08:46 +03:00
Read Confirmation for Pages/Books #2930
Closed
opened 2026-02-05 05:46:12 +03:00 by OVERLORD
·
6 comments
No Branch/Tag Specified
development
l10n_development
release
v26-03
ci_fixing
codeberg-actions
lexical_may_2026
MilnerMart/development
sort_rule_text
GamerClassN7/impersonations-for-admin
Zhey-on/feature/csp-image-css-controls-6033
tortillas5/development
clauvaldez/mfaReset
llm_only
vectors
McTom234/oidc-key-algorithms
docker_env
drawio_rendering
user_permissions
ldap_host_failover
svg_image
prosemirror
captcha_example
fix/video-export
v26.03.4
v26.03.3
v26.03.2
v26.03.1
v26.03
v25.12.9
v25.12.8
v25.12.7
v25.12.6
v25.12.5
v25.12.4
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
pull-request
Mirrored from GitHub Pull Request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#2930
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @smartmaracl on GitHub (Jul 29, 2022).
Describe the feature you'd like
If this feature was already requested by someone else please close this request. But I couldn't find anything like this.
The ability for a person to tick a box or press a button at the bottom of page confirming they have read the page to the author or anyone with the ability of viewing the page. example in image below.
Describe the benefits this would bring to existing BookStack users
Multiple companys using bookstack in germany could benefit of this feature. It is a necessary documentation for multiple ISO-certificates and for some national certifications.
Can the goal of this request already be achieved via other means?
No. As far as I can tell there is no way to display that you have read a page other than adding yourself in a list in the article itself, which requires the permissions to edit.
Have you searched for an existing open/closed issue?
How long have you been using BookStack?
Not using yet, just scoping
Additional context
@ssddanbrown commented on GitHub (Jul 29, 2022):
Thank you for the request. Issue #2835 has a similar request, My thoughts really remain the same, in that this is quite a specific requirement that is really meant to serve business process rather and being useful in the context of BookStack itself.
This is something that could be achieved to some degree using page comments, or by tracking via many other options (Internal form/spreadsheet/etc...).
@smartmaracl commented on GitHub (Aug 1, 2022):
Thank you for your very fast response! In general I can understand that this is a business case and not on your current Roadmap.
However in relation to issue 2834 I find that comments are not a really good alternative for such a feature. As far as I could analyze the behaviour with the BookStack Demo you can delete comments and there is no Log or anything (like the Pagerevision) where you can see who commented and what , or did I miss something there ?
@ssddanbrown commented on GitHub (Aug 1, 2022):
No, there is no specific log for comments, although their action of commenting on something will be written to the audit log and that would remain after the comment is deleted.
If it's really important, and you have a little PHP hacking skill, you could use our logical theme system to hook into comment events and log them to a file.
Alternatively, you could use webhooks on comment events to integrate that data into an external system.
@BloodyIron commented on GitHub (Aug 26, 2022):
@ssddanbrown would it be possible to have webhooks serve this function? In that, it says "this user" read "this page" (after they read the whole thing or something?), as in... not on comment events, but read page events?
This may be already achievable... ish...
@Mailstorm-ctrl commented on GitHub (Aug 29, 2022):
Yes...but not in bookstack. Bookstack is not meant to be a compliance tool (what this request is requesting). If you wanted to track if someone read a page you could do the following:
@ssddanbrown commented on GitHub (Aug 29, 2022):
The scope of where I want to track audit/webhook events is fixed to change actions, I don't want to introduce passive actions (read events) to these systems.
Since this is a feature really intended to serve business process, rather than the benefit of BookStack itself, I'm going to close this off as out of scope.