For security or operational reasons, it is common for a single enterprise to operate multiple Box tenants. However, when an organization's internal user scope ("company") is defined by its Enterprise ID (EID), users from these separate-but-related tenants are treated as external collaborators.

This creates significant problems and reduces usability:

Shared Link Restrictions: Users from a related tenant cannot access links shared with the "People in your company" permission level.

Group Collaboration Issues: It is not possible to invite groups from a related tenant to collaborate on content.

Reduced Security and Convenience: Collaborators from related tenants are flagged as "external," which can trigger stricter security policies (e.g., via Box Shield) and create unnecessary friction for users who are, in reality, internal employees.

These limitations force administrators to use less secure sharing methods or manage a complex web of individual invitations, undermining the benefits of having separate tenants in the first place.

Proposed Solution
Develop a feature that allows administrators to designate other specific Enterprise IDs as part of their internal organization.

This "Tenant Federation" or "Trusted EID List" would enable all users across the federated tenants to be treated as a single "company." By implementing this, the following would be possible:

Users from trusted tenants could seamlessly access "People in your company" shared links.

Collaboration invitations could be extended to user groups across all federated tenants.

Security and governance policies (like those in Box Shield) could be applied consistently to all users within the true organizational boundary, removing the "external collaborator" status for trusted colleagues.

This would provide a secure and efficient way to manage collaboration across the complex structures of modern enterprises.