Organizations and embedding
Structure your business as multiple Wingspan Accounts, run Wingspan inside your own product, and control who can act on each Account.
This section covers businesses that need more than one Wingspan Account: companies with several legal entities, platforms operating in many markets, and software platforms that run contractor payments for their own customers. It explains how Accounts, Organizations, and the parent-child hierarchy fit together, how one backend credential operates many Accounts, and how to give people and systems the right access.
Read the pages in this order:
- Organizations: what an Organization is, how it differs from an Account, and when to split your business into several Accounts.
- Parent and child Accounts: create child Accounts, navigate the hierarchy, and act on a child with
X-Wingspan-Account. - Embed Wingspan in your app: model your customers as Accounts, set up a ServiceAccount credential, mint Account sessions, and onboard contractors.
- Branding and customization: what you can brand through the V3 API today and what V1 customization maps to.
- Team access and roles: invite teammates with roles, create custom roles, grant Authorizations, and manage ServiceAccounts and API keys.
For a full end-to-end example, see the embedded multi-tenant partner recipe.
Updated 10 days ago
Did this page help you?