mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-06 09:09:38 +03:00
Management Editable Drafts/Review #5221
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 @Saincrad95 on GitHub (Mar 14, 2025).
Describe the feature you'd like
I would like to be able to designate a manager and user permissions in which a user will submit a draft to their manager, instead of out-right publishing.
Describe the benefits this would bring to existing BookStack users
I feel this would bring better colaboration to users as we could assign certain edit permissions that aren't necessarily permenant and could be approved by appropriate parties before publishing them to everyone.
Can the goal of this request already be achieved via other means?
Not within bookstack itself. The current way my team has been able to do this is by emailing word documents then copying and pasting the content into our Bookstack after verifying the information.
Have you searched for an existing open/closed issue?
How long have you been using BookStack?
1 to 5 years
Additional context
Just to clear up any confusion on wording or the request.
I would like drafts to be reviewable before publishing by specific teams members and once they give their stamp of approval, then to actually publish the page.
By not having this, it makes it difficult to collaborate as a team with trying to ensure no rogue members pop up and hurt the collection we created for our information.
@SebastienMerv commented on GitHub (Mar 15, 2025):
Hey! I'm not a regular user of Bookstack, but I love contributing to open-source projects.
But I don't understand… Don't you really have a proper "publication" system on Bookstack? Can you only change the book's permissions?
Or do you mean that the book should just have a different default status like "draft," and after this step, you publish it? But if you make another update, you can "review" it one more time… I think that if you want all updates to be reviewable, it would require too big a change to the project’s architecture.
@Saincrad95 commented on GitHub (Mar 15, 2025):
So the way that it is built right now is a user can start a draft, but that draft is only viewable by them. The only way to allow another person to see or edit it, would be to publish it, then it becomes viewable by all parties
@ssddanbrown commented on GitHub (Mar 15, 2025):
Thanks for the request @Saincrad95, but I'd consider the fundamental request here to be already covered by existing issue #473 so I'll therefore close this off as a duplicate.