Goal

Eliminate the requirement that email addresses must be unique across different organizations within the system.

Importance

Currently, users often have a single email address but may belong to multiple organizations. The existing restriction prevents users from using the same email address for notifications across all their organizations. This limitation forces users to create and manage multiple email addresses, leading to unnecessary complexity and increased administrative burden. By allowing non-unique email addresses, we can streamline the user experience and enhance notification management.

Scenarios

1. Creating Organizations: A user can create a new organization using an email address that is already associated with another organization.
2. Updating Organizations: An existing organization can be updated to use an email address that is already registered to a different organization.
3. Notification Management: Users receive notifications from multiple organizations sent to the same email address without any conflicts or issues, ensuring they stay informed about all relevant activities.

Acceptance Criteria

• Users can successfully create multiple organizations with the same email address.
• Users can update an organization's email address to one that is already in use by another organization without encountering errors.
• Documentation is updated to reflect this change in policy regarding email address uniqueness.

This feature aims to improve user experience by simplifying the management of notifications across multiple organizations, ultimately fostering better engagement and communication within the platform.