Skip to main content
Sub-Organizations require a Business or Enterprise plan. View plans
Sub-organizations let you run separate organizations under one parent organization. Each sub-org has its own members, its own assistants, its own branding, and optionally its own domain and billing. You keep oversight from the parent. This is the setup agencies use for each client, and the setup larger companies use for each business unit or brand.
To let a client connect their own WhatsApp or Instagram without an account, send them a connection link from their sub-organization.
Sub-Organizations list with Name, Billing, Custom Domain, Members columns

Creating a Sub-Organization

  1. Go to Settings → Sub-organizations.
  2. Click + Create Sub-organization in the top right.
  3. Enter a Name. The Parent organization is already set to the organization you are in.
  4. Click Create.
You can also start from the organization switcher in the top-left of the sidebar:
  • Hover a parent organization you admin and click its + button (Create Sub-organization).
  • Or click Create Organization and pick a Parent organization from the dropdown. Leave it on None to create a standalone organization.
A sub-organization created from the app starts with consolidated billing on, so it draws from the parent’s balance.
Create organization dialog with the name, the parent organization and the organization domain
Everything else (branding, domain, modules, spending cap) is configured after creation from the sub-org’s management dashboard.

The Sub-Organizations List

The list shows every sub-org you belong to or manage from the parent. On the right of each row, the Add from button (it shows the parent’s name) and the Go to organization button sit next to a ⋮ quick-actions menu.

Quick Actions Menu

View Usage Across Sub-Organizations

Click View Usage at the top of the Sub-Organizations page to see aggregated spend and credits across every sub-org, with a date-range filter and a per-org breakdown.

The Management Dashboard

Click any row in the Sub-Organizations list to open that sub-org’s management dashboard. You can also open it from Open settings in the row’s ⋮ menu. The dashboard has five tabs: Overview, Members, Roles, Customization, Billing.
Sub-organization management dashboard header and tabs
The header shows the sub-org’s name and, on wide screens, its plan badge, its current balance, and its domain when it is not useinvent.com. A back arrow in the top-left returns you to the list. The arrow button in the top-right, Go to organization, switches you into the sub-org as a member so you can use it like any other organization.

Overview

A usage dashboard scoped to this sub-org: Total Spend, Total Credits, a daily usage graph, and a Usage by Event Type breakdown. Filter by Last 7 days, Last 30 days, and other preset ranges.

Members

Invite and manage the sub-org’s team members. Each member has a Name, Email, Role, and Status. Two buttons sit at the top of the tab:
  • The Add from button (it shows your parent organization’s name) lists the parent’s members. Click someone to add them right away, with the same role they have in the parent. There is no invite to accept.
  • Invite Member sends an email invite to anyone, inside or outside the parent.
Admins of the parent see the same Add from button on the sub-org’s own Settings → Members page. Members take the same roles as in the parent organization: Admin, Developer, Manager, and Agent. A user can belong to multiple sub-orgs at once with a different role in each. They switch between them using the organization switcher in the top-left of the sidebar. Invitation emails for this sub-org use this sub-org’s Domain. On any domain but useinvent.com, they go out under the parent’s name, with the sub-org’s logo when it has one. See Whitelabel for sub-organizations for the branding flow.

Roles

Each sub-organization has its own Roles tab for custom roles scoped to that sub-org, mirroring the parent’s Members → Roles. Roles created here apply only within this sub-org.

Customization

The sub-org’s own branding: logo and organization name. These values are used on the sub-org’s branded emails, portals, and sign-in screen.
Sub-organization Customization tab with branding fields
The sub-org keeps its own logo and name; its contact email, address, terms and privacy come from the parent. On any domain but useinvent.com, its invitations and notifications carry the parent’s brand. For field-by-field details and the end-to-end branding flow, see Whitelabel for sub-organizations.

Domain

The Domain card sits at the top of each sub-organization’s Customization tab. A sub-org can share the parent’s connected domain with no setup, and new sub-orgs start on it. A domain of the sub-org’s own takes over once it is connected. Adding the sub-org’s own domain works like the parent’s domain setup (add hostname, add CNAME, wait for the connection). For the full flow, DNS specifics, and the wildcard shortcut for agencies with many sub-orgs, see Whitelabel → Domain and Wildcard for agencies.

Modules

Modules control which sections of the product are visible in this sub-organization’s sidebar. Disabled modules are hidden from the sidebar and return a not-available placeholder if visited directly.
A module the sub-organization does not have (for example Workflows when it is not enabled on the parent) has no row here. The only greyed row is Show credits balance, which needs a spending cap on the sub-org first.
Every organization has its own module switches, in the Modules card of Settings → Customization. The sub-org’s Customization tab is the parent’s remote for the same card, see Modules on the Whitelabel page.

Show credits balance

Below the Modules card, the Sidebar card has a Show credits balance toggle. This changes the usage indicator shown in the sub-org’s sidebar.
  • Off (default): the sidebar shows a Balance in dollars, like $18.10.
  • On: the sidebar shows a Usage percentage, like Usage 6%, based on the sub-org’s monthly spending limit. No dollar amounts are exposed to members.
The credits-based indicator only makes sense when a Monthly spending limit is set on the sub-org, since the percentage needs a cap to measure against. Invent prompts you to set a limit first if you enable this toggle without one.
This is the recommended setting when clients sign in to a sub-org you manage on their behalf and you don’t want them to see raw dollar amounts.

Billing

Controls how this sub-organization pays for usage and where its credits come from.
Sub-organization Billing tab with Consolidated Billing toggle

Consolidated Billing

Consolidated billing is the single most important control here. It decides who pays for this sub-org.
  • Enabled (default): usage charges are billed to the parent organization. The sub-org draws from the parent’s credit pool. No separate subscription, no separate payment method. This is the standard agency setup.
  • Disabled: the sub-org has its own billing: its own subscription, its own payment method, and its own plan. Usage is no longer deducted from the parent. Use this if you want a client to pay Invent directly, or if the sub-org is essentially an independent tenant.
If you ever “graduate” a client off your agency account, disable Consolidated Billing first so their organization keeps working with its own subscription after you detach it.

Monthly Spending Limit

Cap how much this sub-org can spend per calendar month. Once the cap is hit, billable operations pause until the limit is raised or the month resets on the 1st. Combine the cap with the Show credits balance toggle in the Customization tab to give members a clean percentage indicator instead of a dollar balance. Inside the sub-org this limit is read-only and reads Managed by the parent’s name: only the parent changes it, from this tab. The same goes for the All members and All assistants default rules on the sub-org’s Settings → Spending limits page: the sub-org reads them, and the parent sets them through the API (PATCH /orgs/orgs/{sub_org_id}/billing with spending_cap.defaults). Limits on a single member or assistant stay editable inside the sub-org.

Other Billing Controls

The rest of the tab mirrors the parent’s billing page, scoped to this sub-org:
  • Subscription: the sub-org’s current plan (relevant when Consolidated Billing is disabled). A sub-org on Pay As You Go gets its parent’s plan: the parent’s limits and features apply to it.
  • Available balance: the credit balance assigned to this sub-org.
  • Payment method: card on file (only used when Consolidated Billing is disabled).
  • Auto-recharge: automatic top-ups when the balance drops below a threshold.
  • Payment history: past transactions for this sub-org only.
To add balance, change the plan, or edit payment methods, click Go to billing to switch into the sub-org and open its full Billing page.

Switching Between Organizations

Use the organization switcher in the top-left of the sidebar to hop between your parent and any sub-org you belong to. The switcher shows:
  • The parent organization with its plan badge
  • All sub-orgs nested underneath (marked with a ↳ icon)
From the sub-organizations list, Change My Role → Admin / Developer / Manager / Agent lets you switch your own role inside a given sub-org. Change My Role → Leave removes you from it.

Detaching a Sub-Organization

Detaching makes a sub-organization fully independent. It disappears from the parent’s list and no longer shares any resources.
  1. Click ⋮ on the sub-org row.
  2. Select Detach Organization.
  3. Confirm.
Before detaching, make sure the sub-org has everything it needs to stand alone: its own Consolidated billing disabled (so it has its own subscription and payment method), its own Customization, and its own Domain. Otherwise it loses access to the parent’s credits the moment it’s detached.

Managing Sub-Organizations via the API

Everything above can also be done programmatically. This is the setup for platforms and agencies that provision an organization per client from their own backend and wrap Invent behind their own panel. All requests authenticate with a parent organization API key (create one here) in the Authorization: Bearer YOUR_API_KEY header. A parent key can call every org-scoped endpoint for any of its sub-organizations. Two rules to remember:
  • A path without an org id always means the parent org. To act inside a sub-organization, put the sub-org’s id after /orgs/.
  • Nesting is one level deep: a sub-organization cannot have sub-organizations of its own.

Endpoints

All routes require the orgs:write permission, except the billing route which requires billing:write. API keys carry full admin access, so both work out of the box.

Create a sub-organization

billing takes the same fields as the billing route below. Send "use_parent_balance": true to turn on consolidated billing from the start: without it, the new sub-org pays for its own usage. The response includes the new sub-organization’s id. From that moment, the sub-org is a full organization: put its id after /orgs/ on any org-scoped endpoint (contacts, broadcasts, connections, webhooks) with the same parent key.

Configure modules and spending

Toggle which product sections the sub-org sees, and cap what it can spend:
Feature flags (the features object) are managed by the Invent team, not through the API. If a sub-org needs a gated capability, such as a dedicated SMS carrier connection, contact support after creating it.
The full request and response schemas live in the API Reference.

FAQ

No. Your parent organization pays once. Sub-orgs have Consolidated billing enabled by default and draw from the parent’s credits. If you see a second active subscription inside a sub-org, someone accidentally subscribed it separately. Open the sub-org’s Billing tab, disable the redundant subscription, and leave Consolidated Billing on.
Two reasons. First, to set per-sub-org Monthly spending limits, track usage separately, and turn Consolidated billing off if you ever want that sub-org to pay its own way. Second, every organization in Invent is architecturally independent, so the billing tab is always present and a sub-org can “graduate” to its own plan later without any migration.
Free credits are provided to one organization per account. If you have multiple organizations, only one gets the free monthly allowance.
Yes. They use a single login and switch between the sub-orgs they’re invited to using the organization switcher. Their role can differ in each one.

Next Steps

Whitelabel

Brand the parent and every sub-org with logos, domains, and a wildcard for agencies

Members

Invite members into a sub-organization once its branding and domain are in place

Plans & Pricing

Understand how credits flow between the parent and its sub-organizations

Single Sign-On

Route team sign-ins for each sub-org through your identity provider