mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-08 11:19:36 +03:00
Page Verification Workflow using Private Book and Tags #5312
Reference in New Issue
Block 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 @s-sandeep-tech on GitHub (Jun 6, 2025).
Describe the feature you'd like
Implements a simple page verification workflow using native BookStack features:
Pages pending review are tagged Needs Verification and placed in a private Book.
Only Verifier role can access this Book.
Once verified, pages are moved to public Books for visibility.
No core changes; uses permissions + tags + process discipline.
Describe the benefits this would bring to existing BookStack users
Enables pre-publication review of content without needing core changes or external plugins.
Provides a simple content approval workflow, improving content quality and governance.
Allows organizations to implement editor/reviewer roles while keeping draft content hidden from general users.
Leverages existing BookStack features (permissions, Books, tags) — easy to adopt and maintain.
Improves content trustworthiness by ensuring only verified pages are visible to all readers.
Can the goal of this request already be achieved via other means?
Partially, But it is not good method.
Have you searched for an existing open/closed issue?
How long have you been using BookStack?
Under 3 months
Additional context
No response
@ssddanbrown commented on GitHub (Aug 29, 2025):
Hi @s-sandeep-tech,
I feel the fundamental request for this is already covered by exiting issue #473.
While I appreciate you putting forward a potentially simpler implementation option, I think it would be too simplistic for most desires of some kind of approval/verification feature, at least without growing in scope to essentially be a more full approval workflow.