Organizations
An Organization groups one or more projects under a shared Pro or Enterprise plan, a single billing account, and a unified LLM configuration. Any project added to an org automatically inherits the org's plan and LLM settings — per-project overrides are disabled while the org governs them.
Core concepts
| Concept | What it is |
|---|---|
| Org | A billing and access container for one or more projects |
| Member | A user with a role-based access level across all org projects |
| LLM mode | Whether evaluations use LitmusLab's LLM or your own API key |
| Claim code | A short-lived code used to transfer a standalone project into an org |
Plans
Organizations are available on the Pro and Enterprise plans. A new org starts with a 14-day free trial — no credit card required to begin testing.
When you're ready to activate:
- Go to Org Settings → Subscription
- Choose your billing cadence (Monthly or Annual)
- Choose your LLM mode (LitmusLab Managed or Customer LLM)
- Enter a credit card — your subscription starts immediately
LLM modes
LitmusLab Managed
LitmusLab provides the LLM for all qualitative evaluations. Your team doesn't need to supply any API keys. Pricing includes 2,000 test flows per month; additional flows are billed at $50 per 1,000.
During a trial, orgs are always on LitmusLab Managed. You select a mode at activation time.
Customer LLM
Bring your own LLM provider API key. LitmusLab passes evaluation requests through to your provider — you're billed directly by them for token usage. LitmusLab's per-flow pricing does not apply, but a lower base subscription rate reflects this.
To configure: go to Org Settings → Subscription and enter your model name and API key. The org-level key overrides any key set on individual projects.
Billing
Monthly — charged each calendar month.
Annual — charged once per year at a discounted rate. The monthly equivalent and savings percentage are shown when you're selecting a plan.
To update your payment card, click Update card in the Subscription tab. The new card is saved to your account and applied to future charges without any service interruption.
Members and roles
Every org member can access all projects under that org. Roles determine what each member can do:
| Role | Permissions |
|---|---|
| Admin | Manage members, billing, LLM config, and all org projects |
| Editor | Create and edit tests, contexts, environments, and collections across all org projects |
| Viewer | Read-only access to all org projects and run results |
Every org must have at least one Admin at all times — the last admin cannot be demoted or removed.
To invite someone: go to Org Settings → Users, enter their email and select a role. If they don't have a LitmusLab account yet, a placeholder is created and they'll set their password on first login.
Projects
A project can belong to at most one org at a time. When a project joins an org it is upgraded to the org's plan; when it leaves it reverts to Free.
Adding a project
From Org Settings → Projects, click Claim project and choose one of:
- By claim code — the project owner generates an 8-character code in their project's Subscription settings (valid for 48 hours). Enter it here to transfer the project.
- From your projects — if you own standalone projects, select one from the dropdown to add it directly without a code.
Removing a project
Click Remove from org next to any project. The project reverts to the Free plan and becomes standalone again. Users who only had access through the org lose access to that project; users who were added directly to the project via project membership are not affected.
Generating a claim code (project owner)
In Project Settings → Subscription, click Upgrade to Pro → Get a claim code. Share the generated code with your org admin. Codes expire after 48 hours.