Can a subproject be tied to more than one parent Sinch project?

No. A Subproject is strictly tied to a single parent Project. 

Within the Sinch Account Model, the relationship between a parent project and its subprojects is a "one-to-many" hierarchy:

This means that while one parent project can contain multiple subprojects, each individual subproject can only roll up to one specific parent. 

Note on Projects and Accounts 

This strict hierarchy applies at all levels of the Sinch Account Model. Just as a subproject cannot belong to more than one parent project, a parent Project can only belong to one single Account. 

Why this strict structure matters: 

• Access Inheritance: Subprojects inherit their UI access permissions directly from their parent project, and projects inherit from the account. Having multiple parents would create conflicting permissions. 

• Billing and Reporting: Costs are rolled up from the subproject to its specific parent project, and ultimately to the single account invoice. A single entity cannot report its activity or costs to two different parents simultaneously. 

• Resource Isolation: This strict structure ensures that resources belonging to an end-customer (in a reseller model) or a specific internal team are clearly mapped to a single management point. 

Moving a Subproject 

Please note that a subproject cannot be moved or transferred from one parent project to another. If you need to restructure your resources, you would typically need to provision new resources within a new subproject under the desired parent project.