no permission for mkrepository

I had old collab projects migrate to SCM no problem at launch, but I tried to create a new SCM workspace today and I kept getting the error, “no permission for mkrepository.”

I explored every single organizational option available, and I couldn’t resolve this issue. I then went into Plastic SCM’s website and into their user/group management and gave some other random user in our organization admin mods. Once I hit SAVE, about 5min later I was able to create new workspaces on my user, and the other users.

I believe hitting “save” in the Org user/group SCM website’s permissions, resolved this issue for all users. As if the collab/SCM merge didn’t correctly apply permissions for making new workspaces and just hitting “save” in there resolved it.

Posting this here just incase someone else runs into the problem and this actually solves it for them as well.

3 Likes

It seems that you are also trying to create a new repository.

Good to know that you were able to fix the problem by adjusting the server permissions.

If I properly understand, you had some permissions defined previously in Collab but they were not properly migrated?

Give Daniel Stoke a medal, what a legend THANK YOU!

Can confirm that cleared the permission issue. Thank you, DanielStoke!