# Registry overview

In this section
- [Manage custom assets](/products/wallet/user-interface/registry/manage-custom-assets) – Add, edit, enable, and disable your organization's custom assets


The registry is the Wallet-as-a-Service (Palisade) catalog of blockchains, assets, and currencies. It is the platform's source of truth for which blockchain networks, tokens, and fiat currencies are available, and for the properties of each — such as token decimals, contract addresses, standards, and block explorers.

To open the registry, go to **Settings** and select **Manage registry** on the **Registry** card. The registry page has three tabs:

| Tab | Contents |
|  --- | --- |
| **Assets** | Tokens and coins available on the platform, including your organization's custom assets. Each asset shows its blockchain network, symbol, contract address, status, and source. Filter by blockchain, source, and status, or search by name and symbol. |
| **Blockchains** | The blockchain networks the platform supports, with their status. |
| **Currencies** | Fiat currencies used for valuation and reporting, identified by their ISO 4217 code. |


![The registry Assets tab, showing assets with their blockchain, symbol, contract address, status, and source](/assets/registry-assets-list.7a6cecba0a0c3c40077bcd5023f66ac574b72fc2b42eb2c472720db1d18d8809.0ba50ef8.png)

The blockchains and currencies tabs are read-only. On the assets tab, owners and administrators can also [add and manage custom assets](/products/wallet/user-interface/registry/manage-custom-assets).

## Global and custom assets

Every asset in the registry is either part of the **global catalog** or a **custom asset**:

- **Global catalog assets** are available to all organizations and are managed by Palisade. You cannot edit them.
- **Custom assets** belong to your organization. Use them to work with tokens that are not yet part of the global catalog — for example, a newly issued token your organization holds. Custom assets are visible only to your organization.


The **Source** column shows where each asset came from:

| Source | Description |
|  --- | --- |
| **Palisade** | Added and maintained by Palisade. |
| **CoinGecko** | Imported by Palisade from the CoinGecko catalog. |
| **Customer** | A custom asset created by your organization. You can edit, enable, and disable these. |
| **Legacy** | Migrated from the platform's earlier built-in catalog. |
| **Auto** | Added automatically by the platform. |


## Verified and enabled

Two properties control how an asset appears and can be used:

- **Verified** — assets that Palisade has reviewed display a **Verified** badge next to their name. Custom assets you create are not verified.
- **Enabled** — the **Status** column shows whether the asset is active. Disabled assets remain in the registry but are not offered for new activity.


Verify custom asset details
The platform does not review custom assets. Before adding a custom asset, verify the contract address and decimals against the token issuer's official sources. An incorrect contract address can result in transacting with the wrong token.

## Permissions

| Action | Roles |
|  --- | --- |
| View blockchains, assets, and currencies | All roles |
| Add a custom asset | Owner, Administrator |
| Edit, enable, or disable a custom asset | Owner, Administrator |


For the full permission matrix across all roles, see [User roles and permissions](/products/wallet/user-interface/users-and-roles/user-roles-and-permissions#registry).