Skip to main content

​
Subaccounts console: list, manage, invoice, and recover

The Settings → Subaccounts console is the day-to-day operations surface for parent organizations that resell or delegate Orbit to child organizations. From one page you can list every subaccount, change its status, open its detail page, recover an unfinished setup, view a live credit balance, and run a billing period across the whole tree. This guide covers the console itself. For the guided first-time setup, see the new subaccount wizard. For the API-first provisioning and branding flow, see white-label subaccounts.

​
What the Subaccounts console shows

Open Settings → Subaccounts (/settings/subaccounts) in the parent organization. The list shows every child organization with:
  • Name and slug — the slug appears in URLs, API calls, and invoice filenames.
  • Status — active, suspended, pending, or deleted.
  • Plan and limits — the plan name, max team members, and rate limit per second.
  • Created date — pinned to your workspace timezone.
The page is gated to the parent organization’s owner and admin roles. Developers and other members do not see the console, and direct navigation to the page is rejected by the same role check.
If your own account is a subaccount, the page shows an explainer instead of the create button: the platform supports a single level of hierarchy, so a child organization cannot create its own subaccounts. Ask the parent account’s owner or admin to manage children on your behalf.
The Channel connection mode tile also appears on this page. It lets the parent choose, per channel, whether every subaccount sends on the platform’s shared connection or on a connection the parent brings. See per-channel connection mode for how BYO vs platform default works.

​
Row actions: suspend, reactivate, delete

Each row has an action menu with Open, Suspend, Reactivate, or Delete, depending on the current status.

​
Suspend a subaccount

Choose Suspend when you need to stop a child’s traffic immediately without deleting its data. The confirmation dialog shows this warning:
All scheduled and in-flight sends will be paused. API keys belonging to this subaccount will return 403 until you reactivate.
After you confirm:
  • Scheduled and in-flight outbound sends pause.
  • All API keys for the child organization return 403.
  • Webhook delivery and inbound traffic handling pause.
  • Configuration, contacts, numbers, and credit balance remain in place.
Suspension does not transfer credits back to the parent and does not cancel standing charges. To resume, choose Reactivate from the same action menu.

​
Delete a subaccount

Choose Delete only when the customer no longer needs the tenant data. The dialog requires you to type the subaccount’s full name before it will proceed. Deletion is destructive and separate from suspension.

​
Recover a pending-setup subaccount

A subaccount created through the wizard but abandoned before launch sits in pending status. From the console you have two ways to finish it:
  • Resume setup — reopens the new subaccount wizard and continues from the saved draft.
  • Complete setup — calls POST /api/v1/subaccounts/{id}/finalize inline and flips the status to active.
Both options are available from the list-row action menu and from the detail page header.

​
Subaccount detail page

Click a subaccount name or choose Open to reach /settings/subaccounts/{id}. The detail page header shows:
  • Name, slug, and tenant ID
  • Status badge
  • Live credit balance — the current wallet figure in the organization’s currency, pulled from GET /api/v1/subaccounts/{id}.
The page is organized into tabs: The same Suspend, Reactivate, and Delete actions appear in the detail-page header.

​
Consolidated usage rollup

Below the subaccount list, the Consolidated usage & cost card rolls up total spend across every subaccount for a selected billing month and breaks it down per child. It reads from GET /api/v1/subaccounts/usage-rollup?period=YYYY-MM and reconciles with each subaccount’s own statement. You can also export the breakdown as a CSV. For multi-environment and API details of the rollup, see multi-environment subaccounts.

​
Reseller invoice run

The Reseller invoice run card runs a billing period across every subaccount and lets you download a branded HTML invoice per child.
  1. Choose a month with the period selector.
  2. The card lists every subaccount with its totals for that period.
  3. Click Download invoice next to a subaccount. The browser saves a file named:
For example, invoice-acme-retail-2026-10.html. The invoice is generated from GET /api/v1/subaccounts/{id}/invoice.html?period=YYYY-MM and uses the reseller’s own branding. Use the previous/next arrows to step through prior months and revisit invoice history. The next-month control is disabled once you reach the current calendar month, because an invoice run cannot cover a future period.

​
Who can see what