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

# Overview

> Organizations let teams collaborate on shared Archie projects with pooled credits, role-based access, and centralized billing.

An organization in Archie is a shared workspace where a team of builders collaborates on projects. Organizations have their own plan, billing, members, and integrations — separate from individual user accounts.

## When do I need an organization?

You need an organization when more than one person needs to build, edit, or deploy. The Pro plan supports collaboration through invitations, but only Team and Enterprise plans let multiple builders share a workspace, pool AI credits, and assign per-project roles.

If you are working solo, your personal account is enough. You can create an organization later and migrate projects in.

## What is in an organization?

An organization holds:

* **Projects** — applications built with Archie
* **Members** — users granted access at the org level
* **Roles** — Frontend Builder, Backend Builder, Admin, and custom roles on Enterprise
* **Plan and billing** — Team or Enterprise subscription, pooled credits, shared invoices
* **Integrations** — GitHub, Slack, and any other org-wide connections

## Organization vs. account vs. project

Archie's three scopes:

* **Account** — your personal user. See [Managing your account](/introduction/account/managing-your-account).
* **Organization** — a team workspace.
* **Project** — an individual application.

Settings live at the most granular level that makes sense. Personal preferences on your account. Plan and team on the organization. Data model and environments on the project.

## Multiple organizations

You can belong to many organizations — for example, your own org for personal projects and your employer's org for work. The org switcher in the top nav changes which projects are visible. Your account preferences stay the same across orgs.

## Creating one

Open the org switcher and click **Create organization**. Name the org, choose a plan, invite teammates. Full walkthrough in [Setting up an organization](/introduction/organizations/setting-up-an-organization).

## Agency and white-label

Enterprise plans add agency capabilities: per-customer project isolation, customer-specific RAG, white labeling, and custom client handoff workflows. See [Enterprise overview](/introduction/enterprise/overview).

## FAQ

<AccordionGroup>
  <Accordion title="When do I need an organization vs. an individual account?">
    Use a personal account if you're working solo. Move to an organization when more than one person needs to build, edit, or deploy — Team and Enterprise plans give you a shared workspace, pooled credits, and per-project roles.
  </Accordion>

  <Accordion title="Can I move existing projects from my personal account into an organization?">
    Yes. Open the project, go to settings, and transfer ownership to the organization. Your collaborators keep access; the project's billing moves to the org plan.
  </Accordion>

  <Accordion title="How do credits work in an organization?">
    Team and Enterprise organizations have a shared credit pool. Admins can set per-member credit limits so a single user can't burn the whole budget. Pooled credit usage and per-member breakdowns appear on [Plans and credits](/introduction/getting-started/plans-and-credits).
  </Accordion>

  <Accordion title="Can someone belong to multiple organizations?">
    Yes. Use the org switcher in the top nav to change which projects are visible. Account-level preferences stay the same across orgs.
  </Accordion>

  <Accordion title="What if I'm the only admin and need to leave the org?">
    Promote another member to admin first. Archie blocks removing the only admin to prevent lockout — once a second admin exists, you can step down.
  </Accordion>
</AccordionGroup>