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.
How do others approach the need to occasionally audit team member's access to corporate Bitbucket repositories? Most of our team members are named such that they are recognizable but some are unidentifiable. Example is a team member with repo access named 'ss'. Since there is no way from the team administration side to see even a simple basic attribute like the user's email address it makes auditing current access lists impossible.