DNG permissions not flowed down to team areas

We noted an issue with DNG (5.0.2) in that we created multiple team areas - one per system, and assigned users roles within each team area.

Used noted problems in that they could not save a review of a module within their team area.  After raising PMR with IBM on this issue, it turns out that there are a few operations that are defined/controlled at the project level requireing users to also be members at the project level.  IBM even stated that these project-level permisions are not even documented. Great the blind leading the blind, inconsitent behaviors between RTC, DNG, RQM, etc.. in controlling permisions.

Needless to say, this can be quite an admin headache considering we have 30 team areas, with the potential of each having different users. 

I've raised an RFE 69251 ( http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=69251 on this issue to have their permision model addressed to flow down permsions to team areas. Some of these are: 

 saveComment
saveReviewApproval
savePrivateQuery
clm.link.save
saveReview
saveAnyreview
createModuleBaseline
savePersonallDashboard
savePublicTag
saveProjectSnapshot     (not too sure on this one) 

Please add your vote to the RFE.