This is something that we looked into a while ago (for documents), and the problem I found was that the 'author' property is a read-only field (seems to be the case for all content types), so once the content is created, it forever lives under that user.
I'm not sure if this is of any help (or still an option), but we were pointed to Delegate Access (Ghost Blog) FAQ - Archived because of publishing issues as an option.
Would love to hear what others have done to combat this.
Bryce – Thanks for this info – and how appropriate a coupe weeks out from Halloween. ☺
I had never heard about ghost blog/delegate access. While interesting, it unfortunately won’t apply in this case as it seems it is limited to blogs, discussions or docs. I’ve never run across the use case for these content types, just for ideas.
But the first part of your reply on the author prop being read only is helpful. While I can’t do anything about it since it is read only, at least I have some add’l insight.
Thanks for the suggestion, tho. Am still hoping others may have some possible ideas (pun intended) they have used.