---
title: How do you govern several Claude organisations at once?
url: https://opencontroller.lyzr.com/blog/connect-ai-governance-to-multiple-claude-organizations
published: 2026-11-18
updated: 2026-11-18
author: Lyzr
---

# How do you govern several Claude organisations at once?

**Treat each Claude organisation as a separate source. Admin credentials belong to one organisation, so multi-org coverage needs one connection per organisation, a merged inventory keyed by organisation ID, and one set of policies applied across all of them.** The hard part is not connecting; it is noticing the organisation nobody told you about.

## Why do enterprises end up with more than one Claude organisation?

Few companies plan for several organisations. They accumulate. Common causes:

- **API and chat are separate surfaces.** A developer organisation in the Claude Console for API usage often exists alongside a Claude Enterprise organisation in claude.ai.
- **Regions and subsidiaries.** A business unit or country team signs its own contract.
- **Acquisitions.** The acquired company arrives with its own organisation, keys and members.
- **Cloud marketplaces.** Teams using Claude through a cloud provider may sit under a different account structure again.

Workspaces are not the same thing. A [workspace](https://platform.claude.com/docs/en/build-with-claude/workspaces) is a partition inside one organisation, with its own API keys and limits. Several workspaces can be covered by one organisation-level connection. Several organisations cannot.

## What does one Admin API key actually cover?

Anthropic's [Admin API](https://platform.claude.com/docs/en/manage-claude/admin-api) documentation sets out the key facts:

| Fact | What it means for multi-org governance |
|------|-----------------------------------------|
| Admin API keys start with `sk-ant-admin` and only members with the admin role (or owners) can create them | Someone with admin rights in **each** organisation must provision a key |
| `/v1/organizations/me` returns "the organization that your credential belongs to" | A key resolves to a single organisation; there is no cross-org key |
| The Admin API manages members, roles, invites, workspaces, workspace members and API keys | You can build a per-org inventory of people, workspaces and keys |
| Claude Enterprise on claude.ai uses a scoped API key created in claude.ai, and only the members and invites endpoints apply | Enterprise chat organisations need a different credential and give a narrower view |
| Service accounts and federation rules accept only an `org:admin` OAuth token | Some identity settings are not reachable with an Admin API key at all |

Usage, cost and Claude Code activity come from separate APIs: the Usage and Cost API and the [Claude Code Analytics API](/blog/track-claude-code-usage-with-the-analytics-api). Check which credential each one needs per organisation.

## How do you set up governance across several organisations?

1. **Find every organisation.** Ask finance for every Anthropic invoice and every cloud-marketplace line item. Search SSO logs for sign-ins to claude.ai and the Console. Check expense reports for card-paid plans.
2. **Name an owner per organisation.** The owner provisions credentials and answers for its members.
3. **Create one least-privilege credential per organisation.** Store each in your secrets manager with an expiry and a named owner.
4. **Connect each organisation separately.** Tag every record with organisation ID and organisation name.
5. **Merge into one inventory.** Normalise users by email so one person in three organisations shows once, with three memberships.
6. **Apply one policy set.** For example: no personal API keys older than 90 days, no admins outside the IT group, SSO required.
7. **Report per organisation and in total.** Spend, active users, keys and workspaces, with drill-down.
8. **Review quarterly.** New organisations appear after reorganisations and acquisitions.

## What gaps show up most often?

- **The unknown organisation.** A team-level plan paid on a card never reaches procurement.
- **Uneven visibility.** The Console organisation exposes keys and workspaces; the Enterprise organisation exposes members and invites. Your dashboards must say which fields are missing per source, not show zeros.
- **Duplicate people.** The same employee may hold admin rights in one organisation and a basic role in another.
- **Orphaned keys.** API keys created by people who have left, still active in an organisation no one reviews.
- **Skills and connectors.** Enterprise skills and connectors are configured per organisation, so a blocked connector in one may be enabled in another. See [how to govern skills in Claude Team and Enterprise](/blog/how-to-govern-skills-in-claude-team-and-enterprise).

For audit specifics inside a single organisation, read [how to audit Claude Enterprise usage](/blog/audit-claude-enterprise-usage). For the cross-vendor view, see the pillar guide on [governing AI agents across platforms](/blog/how-to-govern-ai-agents-across-platforms).

## How Opencontroller does this

Opencontroller connects to Claude Enterprise and OpenAI Enterprise workspaces and discovers and manages skills in Anthropic Enterprise. Each connection is added to one governed registry alongside agents, models and API keys auto-discovered across AWS, Azure and Google Cloud and agents on platforms such as Salesforce, SAP, Databricks and HubSpot. Posture flags risky permissions and configuration, and "Ask" lets you query the whole estate in plain language, for example "which Claude organisations have admins outside IT?". To see it against your own setup, [book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**Can one Admin API key manage two Claude organisations?**
No. Anthropic documents that the organisation endpoint returns the organisation the credential belongs to. Each organisation needs its own key, created by one of its admins.

**Should we merge our Claude organisations instead?**
Sometimes, but contracts, data residency and billing often keep them apart. Governance should work either way, so connect each one and merge the inventory rather than waiting for a consolidation project.

**Is a workspace a separate organisation?**
No. Workspaces sit inside one organisation and are visible to that organisation's admin credentials.

## Key facts

Anthropic Admin API keys (prefix sk-ant-admin) are created by organisation admins and resolve to a single organisation via /v1/organizations/me, so governing several Claude organisations needs one connection per organisation and a merged inventory. Claude Enterprise on claude.ai uses a scoped key with only members and invites endpoints. Opencontroller connects to Claude Enterprise and OpenAI Enterprise workspaces and discovers and manages Anthropic Enterprise skills. Opencontroller pricing starts from $250K per deployment per year.

## Related

- [How do you audit Claude Enterprise usage?](https://opencontroller.lyzr.com/blog/audit-claude-enterprise-usage.md)
- [How do you govern skills in Claude Team and Enterprise?](https://opencontroller.lyzr.com/blog/how-to-govern-skills-in-claude-team-and-enterprise.md)
- [How do you track Claude Code usage across a team with the Analytics API?](https://opencontroller.lyzr.com/blog/track-claude-code-usage-with-the-analytics-api.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
