Skip to main content

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.

Setting up an organization is a four-step flow: create, configure, invite, and connect integrations.

​
1. Create the organization

Open the org switcher in the top-left of any Archie page and click Create organization. You provide:
  • Name — visible to members and on invoices.
  • Slug — used in URLs and identifies the org programmatically. Lowercase, hyphens, no spaces.
  • Logo — optional, displayed in the org switcher and member views.
The first user to create the organization becomes its initial admin.

​
2. Choose a plan

Organizations need at least the Team plan for multi-builder collaboration. From the new org, open Settings → Billing:
  • Team — $30 per seat per month, minimum 5 seats, maximum 25. 400 AI credits per seat per month, pooled.
  • Enterprise — custom pricing, unlimited seats, advanced governance, compliance add-ons.
Add a payment method or, on Enterprise, request invoice billing. See plans and credits for full breakdowns.

​
3. Invite your team

Open Organization → Members and click Invite member. For each invitee, provide:
  • Email — the invitation goes to this address.
  • Role — Frontend Builder, Backend Builder, Admin, or a custom Enterprise role.
  • Optional credit limit — cap on credits this member can consume per cycle.
Members get an email with a one-click sign-in link. They are added to your organization on accept. See managing team members for the full role and permission model.

​
4. Connect integrations

Most teams connect at least GitHub (for source control) and Slack (for notifications). Open Organization → Integrations to add them. See organization integrations for the full list.

​
Migrating personal projects in

If you started on a personal account and want to move projects into your new organization, open the project settings and click Transfer ownership. Choose the target organization. The project moves over with its history, environments, and integrations intact. Personal credits do not transfer — the project consumes org-pooled credits going forward.

​
Removing the organization

If you ever need to delete an organization, all members must be removed first, all projects archived or transferred out, and the subscription canceled. The action is irreversible — see contacting support for guided deletion.