I need the Field collection to have a separate set of permissions than the parent Node.
This would be useful in my case where I need users to be able to create more Field collection records to a node, but not have ability to edit them. (Because of the nature of this module, in that content is not editable directly on the parent but on another page, I feel this is necessary. Otherwise a user would be locked out of adding records as soon as they move to the next step required to "add" records, if they have 'create', but no 'edit' permissions set on the parent node.)
Also -- and this is more obvious -- when the parent node is read only to the user, but the Field collection for that node isn’t, I'd still like the ability for users to have the "add" link available on it, depending on rather permissions allow it.
- A separate permission set for Field collections than the parent node, with additional "create", "edit", "view", ("inherit") permissions.
- An override/bypass of parent permissions, when child Field collection is still create/edit-able.
- A further suggestion would be to assign Field collection roles by grouping them into sets, rather than by setting them all individually, to not clutter the Permission interface with m fields.