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

# Organizations and teams

> Organizations, apps, and how they fit together

AgentMark uses an **Organization → App → Environment** hierarchy.

```mermaid theme={null}
graph TD
    Org[Organization]
    App1[App: customer-support-agent]
    App2[App: search-pipeline]
    Env1[Env: dev]
    Env2[Env: staging]
    Env3[Env: prod]
    Env4[Env: dev]
    Org --> App1
    Org --> App2
    App1 --> Env1
    App1 --> Env2
    App1 --> Env3
    App2 --> Env4
    style Org fill:#fff3c4,stroke:#333,stroke-width:2px
    style App1 fill:#e2f0d9,stroke:#333,stroke-width:2px
    style App2 fill:#e2f0d9,stroke:#333,stroke-width:2px
    style Env1 fill:#dbe9f6,stroke:#333,stroke-width:2px
    style Env2 fill:#dbe9f6,stroke:#333,stroke-width:2px
    style Env3 fill:#dbe9f6,stroke:#333,stroke-width:2px
    style Env4 fill:#dbe9f6,stroke:#333,stroke-width:2px
```

## Organizations

Each organization represents a company or team. Organizations own billing, members, and all apps within them.

* One billing configuration per organization
* Multiple members with [role-based access](/deploy/users-and-access-control)
* Multiple apps for different services or teams, each with its own [environments](/deploy/environments-and-promotions)

## Apps

Apps are the primary unit of isolation. Each app has its own prompts, traces, datasets, experiments, API keys, metrics, and [environments](/deploy/environments-and-promotions). You can sync an app to a Git repository (GitHub or GitLab).

Common patterns:

* **Per-service**: `customer-support-agent`, `search-pipeline`, `onboarding-flow`
* **Per-team**: `team-alpha`, `team-platform`

For staging/production separation, don't create separate apps. Create [environments](/deploy/environments-and-promotions) inside one app instead: every app starts with a live `dev` environment, and you create `staging` and `prod` alongside it, each with its own runtime, API keys, and environment variables.

## Setting up

1. **Create an organization** once AgentMark provisions your account. [Request access](https://forms.gle/r2z6HuvEoYfHKDxp6) to receive an invite.
2. **Create an app** from your org's **Apps** page by clicking **Create App**. The modal pre-fills a suggested name you can edit before creating; you can connect a Git repo afterwards from the app card's settings menu → **Link Repository**.
3. **Invite members** from **Settings → Members** and assign roles (Owner, Admin, Write, Read).
4. **Connect a Git repo** to your app for prompt version control and to mirror its `.outerlayer/` context directory into the Dashboard on every push.

## Related

<CardGroup cols={2}>
  <Card title="Users and access control" icon="shield" href="/deploy/users-and-access-control">
    Roles, permissions, custom roles, and SSO
  </Card>

  <Card title="Billing and usage" icon="credit-card" href="/deploy/billing-and-usage">
    Tiers, limits, and feature availability
  </Card>
</CardGroup>

<div className="mt-8 rounded-lg bg-blue-50 p-6 dark:bg-blue-900/30">
  <h3 className="font-semibold mb-3">Have questions?</h3>
  <p className="mb-4">Reach out any time:</p>

  <ul>
    <li>
      Email the team at <a href="mailto:hello@agentmark.co" className="text-blue-600 hover:text-blue-800 dark:text-blue-400 dark:hover:text-blue-200">[hello@agentmark.co](mailto:hello@agentmark.co)</a> for support
    </li>

    <li>
      Schedule an <a href="https://cal.com/ryan-randall/enterprise" className="text-blue-600 hover:text-blue-800 dark:text-blue-400 dark:hover:text-blue-200">Enterprise Demo</a> to learn about AgentMark's business solutions
    </li>
  </ul>
</div>