Description of the Idea:
When creating a new user within a specific site, administrators should be able to assign a phone number associated with that site. Currently, only company-level (main account) numbers are available in the number selection list, even if the site has its own pool of numbers.

Problem Statement:

• This behavior limits proper resource segregation by site.
• It results in manual workarounds (e.g., creating the user first, then reassigning the number manually later).
• It contradicts the site-based organizational model and reduces the benefits of multi-site configuration.

Suggested Improvement:

• When creating or assigning a user within a given site, the system should make available all numbers currently associated with that site in the number selection list.
• This ensures proper site-to-number alignment at the time of user provisioning.

Use Case Example:

• Site “Berlin Office” has 10 phone numbers assigned.
• An admin wants to create a new user under the Berlin site.
• Expected behavior: the admin can select one of the Berlin-assigned numbers.
• Current behavior: only main company numbers are available during user creation, despite Berlin's own number pool.

Implementation Suggestion:

• In the user creation form/API, filter or extend the number list to include site-assigned numbers based on the selected site.
• Ensure this behavior is consistent in both Admin Portal UI and developer APIs.

Benefits:

• Promotes clean and logical separation of resources per site
• Saves time and reduces post-creation adjustments
• Supports scalable, decentralized administration
• Aligns with the multi-site architecture intent of RingCentral deployments

Priority:
Medium, but critical for organizations with multi-site operations — should be addressed ASAP to support clean provisioning flows.

Conclusion:
Allowing access to site-assigned numbers during user creation will significantly improve administrative workflows, enhance consistency, and make full use of RingCentral’s multi-site capabilities.

Let me know if you’d like supporting examples, UI suggestions, or expected API behavior for this use case.