Permission System

Hey,

Is there an easy way of assigning multiple projects to the group?
e.g.
I have P1, P2, …, P10 (Projects), and G1, G2 (Groups of Devs).
I want to set up permissions so G1 has access to P1, P2, P3, and G2 has access to P4-P8.

I know that I can right-click each repo, select permissions and add a group there (then configure permissions - the same permissions in each repo)

Also, in order to have a manager in my org, I need to give him at least chgperm and mkrepository so he can create a new repo and add new people to it. It doesn’t make sense for me, because after testing it seems that he can modify his own permissions e,g, granting rmrepository, rmchangeset and I don’t want this to happen.

If this is the only option, please consider adding an option to copy permissions from other groups.

Hi,

You can define permissions at the server level and also at the repo level. You could neither allow nor deny the view and read permissions at the server level and then explicitly allow the permissions at the repository level for the desired users/groups. You can also do it in the opposite way, But I’m afraid there is no a way to copy permissions.

Not sure if you are aware of the security guide: Plastic SCM version control · Security guide
We include some use cases with Plastic SCM permissions.

1 Like

Yes, I was aware of the guide.
Thanks for the confirmation.

It would be great if you could add something like copying permissions to speed up the process.

1 Like