> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tesouro.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Organizations
> What an Organization is in Embedded Banking, where it sits in the platform hierarchy, and what you need before onboarding one.
An Organization is the business entity Tesouro maintains a banking relationship with — either directly, or indirectly through one of its banking partners. An Organization can be a bank, a platform partner contracted to a bank, a fintech partner contracted to that platform partner, or a business customer of the platform or fintech partner.
Every bank account, user, transfer, and webhook in Embedded Banking is scoped to one Organization.
Onboarding a business customer is KYB — the bank's Know Your Business pipeline. It collects information on the business and the people behind it, runs identity and risk checks, and either opens a deposit account or doesn't.
These pages cover the concept. For the API shape of the application that drives KYB, see [Bank account applications](/embedded-banking/guides/bank-account-applications/overview).
## Where Organizations sit
A Tesouro deployment is a hierarchy of Organizations. The bank sits at the top, and the business customer is the leaf. In between sit the platform partners and fintech partners integrating Embedded Banking.
```mermaid theme={null}
graph TD
classDef bank fill:#EFF4FF,stroke:#3538CD,color:#3538CD
classDef platform fill:#F4F3FF,stroke:#6938EF,color:#6938EF
classDef fintech fill:#EFF8FF,stroke:#175CD3,color:#175CD3
classDef business fill:#ECFDF3,stroke:#067647,color:#067647
bank["BANK"]
platform["PLATFORM PARTNER"]
fintechA["FINTECH PARTNER"]
fintechB["FINTECH PARTNER"]
biz1["BUSINESS CUSTOMER"]
biz2["BUSINESS CUSTOMER"]
biz3["BUSINESS CUSTOMER"]
bank --> platform
bank --> fintechB
platform --> fintechA
fintechA --> biz1
fintechA --> biz2
fintechB --> biz3
class bank bank
class platform platform
class fintechA,fintechB fintech
class biz1,biz2,biz3 business
```
A partner tier can be skipped — a fintech partner can sit under a platform partner or directly under the bank — but the business customer is always the leaf.
**Example**
Northfield Software, a platform partner integrating Embedded Banking, has its own Organization and creates a child Organization for each business customer that signs up through Northfield's product. Northfield's backend acts on those child Organizations using its own credentials and the `X-Organization-ID` header (see [Creating an application](/embedded-banking/guides/bank-account-applications/creating#acting-on-behalf-of-a-child-organization)).
## Cross-organization isolation
A user identity is bound to the OIDC application that introduced it, which is bound to a single Organization. User-scoped tokens cannot read or write data outside that Organization — even if the same identity exists in another.
## Prerequisites
| Prerequisite | Notes |
| :--------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Credentials | A `client_credentials` grant for your platform — see [Authentication](/embedded-banking/guides/authentication/overview). |
| Sandbox access | A sandbox tenant from Tesouro before you touch production. Test data, test outcomes, no real KYB. |
| Auth scope | `embedded:application:write` to create and submit applications. Reading needs `embedded:application:read`. |
| Surface decision | Pick how the applicant will fill in their details — your own UI, the [hosted app](/embedded-banking/guides/white-label), or the [onboarding component](/embedded-banking/guides/embedded-components/onboarding). |
You don't need anything from the business customer before creating the application. An empty `DRAFT` is valid; details get PATCHed in later, either by your backend or by the applicant in a browser.
## Where to next
The three entities — business, controller, beneficial owners — and what to pre-fill to reduce drop-off.
Instant approval, manual review, denied — what each one means and what your product should do.