Because all email addresses have to be unique, a new user add should fail if their email address matches that of an existing user. As the current design only allows RBAs to be assigned to regions by adding users, it's not possible for an RBA to administer two different regions as this would require adding the same email twice.
Internally, the database supports multiple RBAs for a region as the linking relation is by means of internal user_id, not email.
What's needed is a mechanism to authorize existing RBAs into a second region -- both in the case that the second region already has an RBA and in the case it doesn't.
Because all email addresses have to be unique, a new user add should fail if their email address matches that of an existing user. As the current design only allows RBAs to be assigned to regions by adding users, it's not possible for an RBA to administer two different regions as this would require adding the same email twice.
Internally, the database supports multiple RBAs for a region as the linking relation is by means of internal user_id, not email.
What's needed is a mechanism to authorize existing RBAs into a second region -- both in the case that the second region already has an RBA and in the case it doesn't.