Richar Cai,

Yes, you will have to add a precondition trigger on the 'Deliver Phase 2 (server)' action. Although it is not as automatic as you may prefer.

The first thing you should do is create a RTC Team Area or new RTC Project role within the RTC Project to identify the people who will end up with write access (either adding them to the new RTC team or giving them membership to the new role, whichever you end up choosing.)

Once that is done, open your Project (I'm using Eclipse), go to Process Configuration -> Team Configuration -> Operation Behavior -> Source Control -> Deliver Phase 2 (server). Check the 'Preconditions...' checkbox and add the trigger 'Restrict Changes to Items'.

At the bottom of the precondition make sure to select the stream that the trigger should resolve paths against (different streams can have the content located in different places if users decided to move code around, which is why I believe this is required.) After that you select the component and drill down to the files underneath the directory structure you want to lock down. Unfortunately it doesn't appear there is any easy way to recursively set a parent directory so you'll have to add all the files.

Remember that this is triggered on a deliver operation. Users can still checkin changes to these files but they won't be able to deliver them, so you may get some developer grief that it wasn't caught sooner. If this is an issue, you may want to look at putting in locks on the files to make it more obvious to them early-on. I believe this also doesn't lock out directories so users may be able to add new files underneath that directory.

If you need more control over directories as well, there is another precondition on the same phase called 'Restrict Changes by Item Name' where you can restrict specific change types to folders (as well as files.)

https://jazz.net/library/article/1075

https://jazz.net/library/article/215