# Managing Registries
Source: https://docs.chain.link/ace/guides/identity-manager/manage-registries
Last Updated: 2026-04-06

> For the complete documentation index, see [llms.txt](/llms.txt).

## What are registries?

A **registry** in ACE is the top-level organizational unit for the Identity Manager. Each registry bundles two types of sub-registries:

- **Identity registries** — map wallet addresses to [Cross-Chain Identifiers (CCIDs)](/ace/concepts/cross-chain-identity#the-cross-chain-identifier-ccid).
- **Credential registries** — manage the lifecycle of credentials linked to CCIDs.

Each sub-registry corresponds to a smart contract deployed on a specific blockchain. A single registry can span multiple chains by including sub-registries on each target network. For a deeper explanation of the registry model and how it fits into the identity lifecycle, see [Cross-Chain Identity](/ace/concepts/cross-chain-identity).

## Create a registry

## View registries

## Multi-chain setup

Registries are designed to work across multiple chains. Each entry in `identity_registries` and `credential_registries` targets a specific `chain_selector`, and the platform deploys (or imports) a contract on each specified chain independently.

A typical multi-chain configuration:

- **Identity registries** on every chain where users interact — so the IdentityRegistry on each chain can resolve wallet addresses to CCIDs locally.
- **Credential registries** on every chain where policies need to verify credentials at runtime.

Because CCIDs are chain-agnostic identifiers, a credential issued on one chain's CredentialRegistry is logically valid across all chains. The multi-chain deployment ensures that each chain has a local copy of the registry contracts for low-latency, on-chain lookups. For more on how this model works, see [Cross-Chain Identity](/ace/concepts/cross-chain-identity).

> **NOTE**
>
> You must have a [CRE Connect Wallet](/ace/getting-started/account-setup#4-set-up-cre-connect-wallets) deployed on each
> chain before ACE can deploy managed registry contracts there.

## Update a registry

You can update a registry's name, description, and add new sub-registries. Updates are **additive** — you can add new identity or credential sub-registries to additional chains, but you cannot remove existing sub-registry pairs.

## Share across organizations

You can grant another organization read access to a registry you own, so it can use your identities and credentials as a credential source without re-issuing them. Grants are read-only for the recipient and can be revoked at any time. For the full workflow — granting, discovering registries shared with you, using them, and revoking — see [External Registries](/ace/guides/identity-manager/external-registries).

## Archive a registry

Archiving a registry deactivates it and prevents any further operations. Before archiving, all identities associated with the registry must be removed or archived first.

> **NOTE**
>
> All identities in the registry must be archived or removed before the registry itself can be archived. Attempting to
> archive a registry with active identities returns an error.

## Related pages

- [Cross-Chain Identity](/ace/concepts/cross-chain-identity) — conceptual background on CCIDs, registries, and credential sources
- [Managing Identities and Credentials](/ace/guides/identity-manager/manage-identities) — register identities and issue credentials within a registry
- [Managing Credential Types](/ace/guides/identity-manager/manage-credential-types) — define and manage the credential types used in credential registries
- [Coordinator API Reference](/api/ace/coordinator/docs) — full API schema and parameters