Can access to Components be restricted stream by stream?
Accepted answer
You can use the "Restrict Change Set Delivery to Components in a Stream" Deliver(Server) precondition.
Comments
Thanks Geoffrey!
Can this keep users from even reading the contents of a Component in a specific stream?
Foe example if you have a Component that has unique content (but only in a specific stream) that you don't want others to even be able to read. Can this pre-condition restrict read access of this Component for this specific stream?
Thanks!
Permissions and preconditions are for controlling write access, not for controlling read access. You can only control read access for a component globally ... not on a per stream basis. Just for interests sake, what would be the purpose of making a component invisible to a given person in one stream, but making it visible to that person in another stream?
Thanks again!
The purpose I was told would be that the Component will have unique content in a specific stream. The same Component in other streams would not have this unique content. Not everyone needs should be able to see this unique content.
The content of a component is actually stored in change sets ... a 'stream' is just a way of seeing the combination of a particular set of change sets. So hiding a component in a stream wouldn't really prevent someone from getting access to the content ... you would have to hide the change set (because RTC allows you to access change sets directly).
Thanks again Geoffrey!