Prevent component creation owned by individual users?

Is there any way to prevent component creation by naive users who don't really want/need them? We find that new users end up creating a component because they don't flow with a stream when creating a repository workspace. So our server is ending up with a bunch of junk components that can never be deleted (or even archived since that isn't an option).

You can configure permissions for roles to prevent component creation. Check the permissions for the project/team. The options are under Source Control -> Save Component.

Is there any way to prevent component creation by naive users who don't really want/need them? We find that new users end up creating a component because they don't flow with a stream when creating a repository workspace. So our server is ending up with a bunch of junk components that can never be deleted (or even archived since that isn't an option).

You can configure permissions for roles to prevent component creation. Check the permissions for the project/team. The options are under Source Control -> Save Component.

Correct me if I am wrong - I believe repository workspace/component creation is independent of projects. The permissions you are pointing to don't control creation of the component, but adding or removing to the project and changing it's properties when it is owned by the project.

I am trying to prevent component creation where the owner is an individual rather than a project/team.

I'm not aware of a way to do this. I've submitted work item 95350
requesting this capability.

Cheers,
Geoff

xdcx11 wrote:

tmokwrote:

Is there any way to prevent component
creation by naive users who don't really want/need them? We find that
new users end up creating a component because they don't flow with a
stream when creating a repository workspace. So our server is ending
up with a bunch of junk components that can never be deleted (or even
archived since that isn't an option).Is there any way to prevent
component creation by naive users who don't really want/need them? We
find that new users end up creating a component because they don't
flow with a stream when creating a repository workspace. So our
server is ending up with a bunch of junk components that can never be
deleted (or even archived since that isn't an
option).

You can configure permissions for roles to
prevent component creation. Check the permissions for the
project/team. The options are under Source Control -> Save
Component.

Correct me if I am wrong - I believe repository workspace/component
creation is independent of projects. The permissions you are pointing
to don't control creation of the component, but adding or removing to
the project and changing it's properties when it is owned by the
project.

I am trying to prevent component creation where the owner is an
individual rather than a project/team.

Thanks for adding this Geoff.