Have to set user permissions twice for them to take effect?
When I create a new user and assign them permissions for certain repositories, I've noticed that I have to go back in after they accept the user invitation and reapply their permissions to write to a repository.
Is this normal? If I can't set permissions before the user has accepted the invite, it would be nice if the check box was not available. Several times I have been completely baffled as to why new users couldn't access a repository, only to find the permissions are not set.
But I was so sure I had already set the permissions, I didn't understand the problem. Now, with a new user, I tested it, and can say with confidence that you have to assign permissions a second time, after they have accepted the invitation.
Is this normal? If I can't set permissions before the user has accepted the invite, it would be nice if the check box was not available. Several times I have been completely baffled as to why new users couldn't access a repository, only to find the permissions are not set.
But I was so sure I had already set the permissions, I didn't understand the problem. Now, with a new user, I tested it, and can say with confidence that you have to assign permissions a second time, after they have accepted the invitation.
2 people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Thanks for the report. We will take a look and try to reproduce it. Once we find it, we will fix it quickly.
Loading Profile...




EMPLOYEE