The motivation is to enforce that an email address is linked to a single ROCC User account. This is important because an email address can be used in the future to retrieve access to one account (email behave as an identifier). This is also to limit people from creating multiple accounts.
On the other hand, the email property for Organization is intended as a contact email address. In that case, there is not reason to restrain one email address to be used with more than one Org account.
The strategy above will be implemented at the API service level.
The motivation is to enforce that an email address is linked to a single ROCC User account. This is important because an email address can be used in the future to retrieve access to one account (email behave as an identifier). This is also to limit people from creating multiple accounts.
On the other hand, the email property for Organization is intended as a contact email address. In that case, there is not reason to restrain one email address to be used with more than one Org account.
The strategy above will be implemented at the API service level.