By HXn on

I have a couple users that need access to a specific Book. I don't want them to have access to ALL Books, just one. Which is where the default roles fail, as far as I know. (Why isn't there a whitelist type funtionality where I can just put in a list of users to have access to the node and all sub-nodes?)
I installed taxonomy_access because I read you can get better access functionality, but I'm still not sure how to implement it.

I need to give certain users access to this Book:

Policies & Procedures [Book page]
- Personnel [Book child page]
- Operations [Book child page]
- Other [Book child child page]
- Health & Safety [Book child page]

How do I do it simply and cleanly?

⋅ Categories: Drupal 5.x

Comments

HXn’s picture

HXn commented

The users will have different roles. For example, the Training Coordinator and Residence Coordinator will both need access to create/edit the Book.

cog.rusty’s picture

cog.rusty commented

I think the problem is that books and node relationships in general have little support at the moment, which makes a book a strange thing, hard to identify with any of Drupal's entities for which there are access control modules.

*All pages* of a book would need to have some common property which would apply only to this particular book (content type, category or something -- whatever the access control modules need to work) and that can hardly be enforced. That somehow makes a book a non-entity, and users would have to tag its pages one by one.

I don't know what a future solution would look like. Perhaps an automatic tag to all pages of a book (or of an "outline" -- book's future name).

If you create all the pages beforehead and tag them with categories then you can control access to them, but not to their future child pages.