How to prevent a role creating components?
Hi all, I'm seeking to restrict creation of new components (RTC 4.0.7) to administrative users. It should still be possible for certain roles to be able to add existing components to streams.
I thought I could do this by removing the permission 'Save Component (server) / Modify / Component / Add a component to a project/team area' from all except the one admin role I have defined but this doesn't seem to have worked as a 'normal' user has managed to create a component in a stream, so I must have missed something.
Can someone advise the best way to do this please?
Accepted answer
Comments
Hi Geoffrey,
thanks for your response. It's not the answer I was hoping for (!) but the enhancement you mention should give the measure of control I'm looking for.
The reason I want this concerns management of a Production environment with multiple project areas and hundreds of users. I'm seeking to keep it as clean as reasonably possible and don't want untold numbers of components (that can't be deleted) created by users outside standard processes. Also components names are mandated as unique within the repository so uncontrolled creation can cause unwanted knock-on effects. Experience shows that when users with limited knowledge have unfettered access then a mess is created that someone - not them - has to deal with!
I personally agree that one should be able to control who is allowed to create components in a repository, for the reasons you mention (which you probably could guess since I submitted that enhancement request :-).
But note that components by default are created as "private" which means nobody else will see them ... so any mess created by someone playing around will not be visible to anyone else, unless the owner explicitly modifies the visibility of the component to be "public".