Corporate Repository & Team Member Access Audit

[Deon Lausche]

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.