My understanding is that the Web UI, as it does not use a repository workspace, requires permissions under "Save Stream (server)" to operate correctly.

Our testing of these permissions has shown that any sub-permission removed will render delivery impossible! So to utilise the Web UI for Source Control, the users have to have such permissions as :-

• Modify the stream flows
• Remove components from the stream
• Delete the stream
• Destroy the locks of others

Now, I'm going to go out on a limb and say that education should stop any erratic behaviour, but it is by no means prevented and leaves an uncomfortable position where you may not be able to undo some of these changes!

We are currently operating v3.0.1. Can someone tell me if this has been revised for RTCv4?