You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have a user in my team who seems to have lost permissions all of a sudden...
We use fork as a GIT UI and fork had "forgotten" about the previous installation/execution, so it went through user setup again and we had to select the appropriate SSH Key again.
We try to setup permissions via groups so it is surprising because other users don't seem to experience that problem.
I temporarily solved the problem by getting him to create a new SSH Key which I added at the Project level with read-write permissions.
It works but is excessive because I do not want him to have read-write on all repositories.
2 Questions:
1) What is the difference between declaring an SSH Key at the user account level rather than the project (or repository...)? Where could I find explanations about this?
2) Is there some kind of method I could follow to try to unravel his permission problems?
Thanks