Currently, when new RingCentral extensions/users are provisioned, they are automatically added to the primary account-wide default message team (e.g., "JTeam").

Admins—including Super Admins—currently have no way to:

Prevent users from automatically joining the default group based on their assigned site location (e.g., Maverick Medical).

Manually remove users from this default group once they are added.

Delete or convert the account-wide default group into a restricted/site-specific team.

For multi-site organizations, this creates unwanted group clutter, cross-site messaging noise, and potential data/communication privacy concerns across different locations.

Proposed Solution
Provide Admins with control over auto-joining default teams under Admin Portal Settings / Team Messaging Configuration:

Site-Based Auto-Join Rules: Allow admins to set auto-join rules for the default team based on Site Location (e.g., Only auto-add users assigned to Main Branch; exclude Maverick Medical).

Option to Disable Default Auto-Join: Allow Super Admins to disable the mandatory default account-wide team altogether, or convert it to an opt-in group.

Member Management for Default Teams: Grant Super Admins permission to manually remove active extensions/members from the default group if necessary.

Business Impact
Prevents employee confusion and unnecessary notifications across different branch locations.

Reduces administrative overhead spent managing unintended broad group memberships.

Improves message organization and security compliance for multi-site organizations.