Add a way to manage/validate the email address domain of members allowed to join a team (BB-10238)

Issue #9148 open
Marcus Bertrand
staff created an issue

In the case where you may run a large team with contractors and other external entities, you may be interested to know which of those members do not have a primary contact email inside your company's domain. You may also wish to prevent users with unverified or non-domain email addresses from joining a team in the first place.

A possible way to do this would be to provide a filter up front that would only allow members with email domain xyz123.com to be added. And, for existing team members, the system could show somewhere which team members do not have a matching domain.

Comments (22)

  1. Jeff Gover

    This is not going to fly in the corporate world. This lack of control is very unacceptable for anyone to give access to our confidential repositories without following any sort of ITIL model.
    In other words treat and lockdown Bitbucket from a Domain level; ie: our firstname.lastname@mycompany.com can only access our Bitbucket repositories, like you do with JIRA for example. You need to start to put security in mind first.

  2. Log in to comment