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

# Organizations

> How multi-tenancy and team access work in Bizzy

Organizations are the foundation of Bizzy's data model. Every piece of data —
contacts, messages, automations — belongs to an organization. This page explains
what organizations are, why they exist, and how they shape the way you use
Bizzy.

## What is an Organization?

An organization is a container that holds all your Bizzy data. Think of it as a
workspace that can represent:

* Your company
* A department or team
* A personal account
* A client you manage

Each organization is completely isolated from others. Data in one organization
cannot be accessed from another, even by the same user.

## Why Organizations?

Organizations exist to solve a fundamental problem: keeping different contexts
separate while letting the right people collaborate within each one.

| Benefit                 | Description                                                 |
| ----------------------- | ----------------------------------------------------------- |
| **Data isolation**      | Keep different businesses or clients completely separate    |
| **Team collaboration**  | Share access with colleagues while controlling permissions  |
| **Resource management** | Connect different email accounts to different organizations |
| **Billing separation**  | Each organization can have its own subscription             |

For example, a freelancer managing three clients can create a separate
organization for each — keeping contacts, messages, and automations completely
isolated. A single company would typically use one organization with multiple
members.

## Members and Roles

Organizations can have multiple members. Each member has a role that determines
what they can do:

| Role      | Description                                                                                                               |
| --------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Owner** | Full access to everything, including billing, API keys, and member management. Every organization has at least one owner. |
| **Admin** | Can manage data and invite members, but cannot access billing or API keys.                                                |
| **User**  | Read-only access to organization data. Can manage their own profile and files.                                            |

This hierarchy follows the principle of least privilege — most team members only
need the User or Admin role. See
[Roles & Permissions](/admin-guide/organization/permissions) for the full
permission matrix.

## Organization Scope

Everything in Bizzy is scoped to an organization:

* **Contacts and customers** belong to an organization
* **Messages** are received and sent through the organization's connected
  resources
* **Automations** run within the organization's context
* **API keys** and **MCP server access** grant access to a single organization's
  data

If you belong to multiple organizations, you can switch between them from the
header. Each switch changes your entire view to that organization's data.

## How Organizations Relate to Accounts

Your Bizzy **account** is your personal identity — your login credentials.
**Organizations** are workspaces you belong to. The relationship works like
this:

* One account can belong to multiple organizations
* One organization can have multiple accounts (members)
* Billing is managed at the account level, covering all organizations under it
* Your subscription tier determines how many organizations you can create

## Related Topics

<CardGroup cols={2}>
  <Card title="Set up your organization" icon="gear" href="/admin-guide/organization/setup">
    Create and configure an organization
  </Card>

  <Card title="Manage team members" icon="users" href="/admin-guide/organization/users">
    Invite members, assign roles, and manage access
  </Card>

  <Card title="Roles & Permissions" icon="shield-check" href="/admin-guide/organization/permissions">
    Full permission matrix for each role
  </Card>
</CardGroup>
