Video detailing what this does
Video detailing how this works
This module adds a system similar to publish / unpublished status of nodes. The reason that this is needed is so that you can tell certain roles they can't view nodes while others can. The issue with publishing status is that there is no grey. Menu systems automatically hide unpublished nodes while also checking for the node_access.
This blocks situations where admins and sub-admins need to work on content in the context that it will be presented left in a position where they are unable to do so. This will help create the same level of security that publish status does but without the limitations on admin-esk users to actively work with content the way it will eventually render (menu wise).
Use this module if you want to be able to limit what some users see in books and menus but still want others to have full visibility of those posts.
This should work with other node access methods as the priority of the grants in this module are very high. This is intentional so that it takes priority over all other access control projects, much in the same way that unpublishing a node takes priority over all access control methods.
Outline Designer 2.x integration!
Hidden nodes is the reason for the overhaul of the Outline Designer module and as such, it is the first module to implement the API. If you use Outline Designer 2.x branch and the new outline_designer_book module, you'll be able to hide nodes in bulk and see your changes instantly! This integration makes this module extremely useful
6.x and 7.x have views integration!
There is simple views integration in both branches. These allow you to display, filter, and sort based on the hidden node's value as it relates hidden_nodes table over to node via the nid (simple, yet powerful stuff). Large thanks to komlenic for that functionality.