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.
Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster ! While we’re all excited about the new improvements to Bitbucket ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events