Security on Label - chgperm Deadlocked

[tom.peters]

I did not realize that when you remove 'chgperm' from ALL_USERS that it overrides individual users, too! I saw the override warning, but I thought that if an individual user had chgperm (like the OWNER), that would win out.

 

Now I am stuck with a label whose permissions are locked in my own local rep even though I am the owner.

 

Is there any way to get this back?

 

Thanks,

Tom

[manu]

Yes, review who is the "repository Server" owner, that user is the Plastic SCM root, if it's "ALL_USERS" change it to someone else, for example you.

 

Then, login with the root user and change the label permissions.

[tom.peters]

TA-DA! You saved the day!

 

Thanks you. :-)

[manu]

You are welcome cyber-tom!

[tom.peters]

DELETE, DELETE

 

So, here's what I ultimately want to do. Once a label is determined to be 'frozen', such as when we decide a release is GA and the label should not move to any other changeset, how do I ensure no one changes the label?

 

My thinking was (and may be wrong) to remove all permissions (except for view, read, and mkchildbranch) from the label for ALL_USERS but keep all permissions for Admins (group we have). Now, being that we are fully-distributed, will that cause issues for ALL_USERS when they replicate into their repository as it did for me? Should I tell everyone to make themselves the rep owner for their own local reps?