Book module enhancements: better permissions

As someone who used book module for the first time last project think additional permissions would be useful. So this is still relevant.

This extension is being deprecated, see 🌱 [Meta] Tasks to deprecate Book module Active . It will be removed from core and moved to a contrib project, 📌 [11.x] [Meta] Tasks to remove Book Active .

This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

This issue may be re-opened if it can be considered critical → , If unsure, re-open the issue and ask in a comment.

Still seems like a relevant feature request.

Actually going back on my previous statement. This was quiet for 12 years. Still a desired feature?

We've done a lot of work with 2.0.x that may cover some of this.

If still a new permission is needed that's outside what we have done lets open up follow ups for those.

I still think this feature is necessary because a book(any content) can be a creative final work that no one wants it to be expanded upon by others. There are situations where no one wants to interfere with other people's work.
Therefore, members should be limited to choosing their own content.
No one should be able to add their own content to someone else's book or parent content. Or, permissions can be extended or limited based on the type of node.
Another benefit is that the outline list will be shorter when selecting/searching for a book/parent from a bunch of books.