> ## Documentation Index
> Fetch the complete documentation index at: https://docs.macropay.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Create Multiple Organizations

> Run separate brands, clients, or agents under one login — each with its own products, payouts, and tax handling.

An **organization** is the top-level boundary for everything you sell on Macropay: products, customers, checkout, payouts, and webhooks all live inside one. Because Macropay is the **Merchant of Record**, each organization is also the unit we use to remit sales tax and VAT on your behalf — so the customer's bank statement shows the right seller, and the right entity's books stay clean.

Most builders eventually need more than one. You can spin up as many as you like from a single login and switch between them in two clicks.

## When to use more than one

<CardGroup cols={2}>
  <Card title="Separate brands">
    Ship a SaaS product and a paid newsletter without mixing their catalogs, customers, or payout schedules.
  </Card>

  <Card title="Client work">
    Run a billing org per client. Each gets isolated revenue, refunds, and a clean MoR tax trail.
  </Card>

  <Card title="Per-agent billing">
    Give each AI agent its own org to track agentic margin — billed revenue vs. AI cost — without cross-contamination.
  </Card>

  <Card title="Sandbox vs. live">
    Keep experiments walled off from a production org while you validate pricing or metered events.
  </Card>
</CardGroup>

## Create and switch between organizations

<Steps>
  <Step title="Start with your first organization">
    If you haven't yet, sign up on [Macropay](https://macropay.ai). The org you create during onboarding becomes your default workspace.
  </Step>

  <Step title="Open the organization menu">
    From the dashboard, click the menu in the **bottom-left corner** and choose `New Organization`.

    <img height="200" src="https://mintcdn.com/macrodeepinc/rPF293t5zy_Onjx_/assets/guides/create-multiple-organizations/first.png?fit=max&auto=format&n=rPF293t5zy_Onjx_&q=85&s=a4e2fa882b6d3d867f1aa977dca28fc1" data-path="assets/guides/create-multiple-organizations/first.png" />
  </Step>

  <Step title="Name and describe the new organization">
    Fill in the details for the new org — its name and slug determine the public-facing identity your customers will see at checkout.

    <img height="200" src="https://mintcdn.com/macrodeepinc/rPF293t5zy_Onjx_/assets/guides/create-multiple-organizations/second.png?fit=max&auto=format&n=rPF293t5zy_Onjx_&q=85&s=5a7062e68337b8cd120f88d3e0376fdf" data-path="assets/guides/create-multiple-organizations/second.png" />
  </Step>

  <Step title="Add your first product">
    Every org starts empty. Create a product to make it sellable — one-time or subscription, both use the same API and data model.

    <img height="200" src="https://mintcdn.com/macrodeepinc/rPF293t5zy_Onjx_/assets/guides/create-multiple-organizations/third.png?fit=max&auto=format&n=rPF293t5zy_Onjx_&q=85&s=6a4859c0b6c7bc082561112b3fcf5892" data-path="assets/guides/create-multiple-organizations/third.png" />
  </Step>

  <Step title="Done — the organization is live">
    Your new organization is ready to take payments, with tax and PCI handled for you.

    <img height="200" src="https://mintcdn.com/macrodeepinc/rPF293t5zy_Onjx_/assets/guides/create-multiple-organizations/fourth.png?fit=max&auto=format&n=rPF293t5zy_Onjx_&q=85&s=dd80792b1c44aea398204a91bf4a0fb1" data-path="assets/guides/create-multiple-organizations/fourth.png" />
  </Step>

  <Step title="Switch between organizations">
    Reopen the bottom-left menu and select any organization to switch context. Products, customers, and payouts swap instantly.

    <img height="200" src="https://mintcdn.com/macrodeepinc/rPF293t5zy_Onjx_/assets/guides/create-multiple-organizations/fifth.png?fit=max&auto=format&n=rPF293t5zy_Onjx_&q=85&s=d1ca0dc0098572519a52c8dcc3295141" data-path="assets/guides/create-multiple-organizations/fifth.png" />
  </Step>
</Steps>

<Note>
  Organizations are fully isolated. Products, customers, payouts, webhooks, and access tokens belong to exactly one org and never leak across the boundary.
</Note>

## Programmatic access per organization

Each organization issues its own **organization access tokens (OAT)**. Scope a token to one org and every API call lands in that workspace — handy when you automate per-brand or per-agent billing.

<Tip>
  Pair one OAT per agent with the [Signals API](/features/usage-based-billing/introduction) to attribute activity and outcome events to the right organization, then read agentic margin per agent without any manual reconciliation.
</Tip>