Sinch Account Model

Michelle_Peruskie — Mon, 06 Jul 2026 10:52:16 GMT

To help you effectively manage your resources, billing, and team access, Sinch uses a structured hierarchy:

Accounts
Projects
Subprojects.

Understanding this model is key to organizing your Sinch products securely, whether you are a direct customer separating internal environments or a reseller managing multiple end-customers.

The Hierarchy at a Glance

The Sinch Account Model follows a strict top-down structure:

Sinch Accounr Model Daigram.jpg

This has a maximum depth of three tiers:

Account (Top level)
Project (Child of Account)
Subproject (Child of Project
Note: Subprojects cannot have their own child subprojects.)

Resources (such as phone numbers, apps, or API configurations) can sit directly on either the Project level or the Subproject level.

Account Level

The Account is the highest level of your Sinch organization. It represents your overarching business entity and help you manage:

Billing & Cost: Your Account is the centralized entity for billing. One Account is tied to one invoice and operates in one single currency.
Top-Level Access: Organization-wide settings and top-level user access are managed here.

Project Level

A Project is a general container for your Sinch resources. Every Sinch Account comes with at least one default project. Projects have the following features:

Resource & Environment Separation: Projects are ideal for general separation of resources and access as desired (for example, creating separate Projects for "Development" and "Production" environments).
Technical Equivalence: Technically, Projects and Subprojects function the same way when it comes to hosting resources. The main difference is that a Project's parent is the Account.

Subproject Level

A Subproject is an additional organizational layer that sits inside a parent Project. Technically, a Subproject acts exactly like a project, but it has a Project as its parent instead of an Account. Subprojects have the following features:

The Reseller Use Case: Subprojects are highly recommended to represent resellers' end-customers. Because subprojects support certain API automation capabilities, they allow resellers to programmatically isolate costs and resources for individual customers securely. Note: This does not apply for new signups.
Strict Hierarchy: There can only be one level of subprojects. A subproject cannot act as a parent to another subproject.
Inherited Management: Unlike parent Projects, Subprojects do not have their own separate user management in the Build Dashboard. They inherit the UI configurations of their parent project.

Access Control and Inheritance

Security and user access in Sinch, flow downwards, but they are handled differently depending on whether you are managing access to the Build Dashboard (UI) or access via APIs.

Build Dashboard (UI) Access: User access is configured on the Account or Project level, inherited downwards within that specific tree, and strictly isolated otherwise.
- Example 1: A user granted access to the whole Account automatically has access to all current and future projects and subprojects within it.
- Example 2: A user granted access only to Project A will have access to Project A and all of its subprojects. However, they are completely isolated from Project B unless explicitly granted access to it.

Learn how to manage user access.

API Access: Access controls for integrations are configured at the Project or Subproject level. Each subproject can have its own unique Access Key, isolated from sibling subprojects and other accounts; because permissions inherit downward within a project's tree, a parent project's Access Key can also be used to access its subprojects' resources.

Accessing your API Keys.

Frequently Asked Questions

Can I create multiple Projects and Subprojects?

Currently, the ability to manually create and manage additional projects and subprojects is enabled primarily for large-scale implementations operating alongside a dedicated Sinch Account Manager. For most users, a single default project is provisioned upon signup, which is sufficient for standard use cases.

Note: We are aiming to enable the option for all accounts to create a limited number of projects and subprojects via self-service in the future.

Can a Subproject belong to more than one Project?

No. A Subproject is strictly tied to a single parent Project. It cannot inherit from or be shared across multiple parent projects.

Can I delete a Project or Subproject?

Currently, there is no self-service deletion of Projects or Subprojects from within the Build Dashboard. For parent projects, deletion can only be performed by our team in exceptional cases via a support request.

Note: For Subprojects, certain API automation capabilities are available that do allow for programmatic deletion. We also plan to introduce self-service deletion capabilities directly within the Build Dashboard in the future.

article Sinch Account Model in Billing & Pricing