Okay that’s what I thought. Thanks for the confirm and the information. I’ll check out that thread on Members.
To clarify, I expected Members to protect by role for each document, as it does for pages and posts. I’m asking if that is the intended interaction between the two plugins.
If you’re under the impression that Members only manages capabilities on roles, then this screenshot below might shed some light. In the middle of the image is a “Content Permissions” section that appears when editing pages, posts, and documents. There you can select individual roles that are required to view the content. However, it doesn’t seem to work for documents.
Thanks for the document_read_uses_read suggestion. That did allow me to set read_document on each role but I was hoping for the more fine-grained control of restricting each document to selected roles as mentioned above.
