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.
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
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