A client wants to have collaborators be able to collaborate on assets without exposing their comments to users who aren't collaborators or lifecycle managers. Currently collaboration activities (e.g. comments) are visible to anyone who has read access to the asset. It might solve their needs if there were a system or community option to prevent collaboration details being read by non-collaborators. The devil is in the details though...what if the sets of collaborators differ per state--e.g. should those who are collaborators only in state A be able to read comments once the asset leaves state A, merely by virtue of their having participated before?

Thoughts?

(Note that for this client, the "do not apply community permissions to assets in this state" option is insufficient, because they want the collaboration activity to be invisible to non-collaborators forever.)