Currently, RingCentral requires each user to have a unique email address in order to enable Single Sign-On (SSO). This limitation prevents SSO from being enabled for users who are associated with multiple RingCentral accounts using the same email address.

This is a common scenario in organizations where:

A single user may manage or participate in multiple departments or subsidiaries.
Shared service accounts are used across different teams or regions.
Impact:

Prevents seamless authentication for users with legitimate multi-account access.
Increases friction and administrative overhead.
Limits the flexibility of enterprise SSO deployments.
Proposed Solution:
Allow SSO to be enabled for users with the same email address across multiple RingCentral accounts by:

Supporting account-level SSO mapping.
Introducing user aliases or unique identifiers beyond email.
Providing admin-level controls to manage such exceptions securely.

Benefit:
Enhances user experience and security.
Aligns with enterprise identity management best practices.
Reduces support tickets and manual workarounds.