Organisation networks
Select which platform catalogue networks the active organisation can use, and whether it can use more than one at a time.
Networks controls which entries from the platform's network catalogue the active organisation can use, and whether the organisation can use more than one at once. This decides where the organisation's transactions can be submitted. A platform administrator manages the network catalogue and RPC connections for the DALP InstanceA DALP Instance is one self-contained copy of the platform, deployed inside a boundary you choose and connected to ledger networks you approve.Read the concept on the platform networks page.
The organisation gets its first network during onboarding: whoever creates the organisation picks the one chain its first system deploys to, and that choice becomes the organisation's default network going forward. Reach for this page only when the organisation needs another network beyond that default, or to check the state of one already being added. What you enable here is not private to this screen: a network becomes selectable for every member's own transactions the moment it reaches Active, and only for as long as it stays there.
The decision that shapes everything else on this page is whether the organisation needs one network or several.
Stay on one network
Tokens deploy in one place, one set of transaction history needs reconciling, and nothing needs to stay synchronized across chains. Choose this when all participants use the same network.
Turn on multi-network support
Members choose a network per transaction, tokens can exist on more than one network at once, and the organisation takes on the overhead of tracking activity across each network separately. Enable it when participants need different networks.
Enabling support does not deploy a network. Adding a network starts a deployment. You cannot disable support while a non-default network is Pending, Deploying, or Active.
Steps
Open Networks
Open Organisation settings, then Infrastructure, then Networks. Every organisation starts with multi-network support off, and that is the state you land in here: the page shows only the Multi-network support card and its status, nothing else. Turning that support on, in the next step, is what makes the Your networks card and its list appear. The list shows networks added to the active organisation.
Screen equivalent: with multi-network support off, the Multi-network support card and its status alone. Once it is
on, also the Your networks card listing each network the organisation can use and its current state.
Change network access
Turn on Multi-network support if the organisation needs more than one network: select Enable on that card, then confirm Enable multi-network support? in the dialog it opens. That confirmation is what makes the Your networks card appear; add a network from it: select Add network, choose one from the Network field in the Add a network dialog, then confirm Add network. The picker offers available EVM networks.
Adding an EVM network starts an on-chain deployment immediately; there is no draft state to save for later. Adding a network requires no other deployment to be running for the organisation. A managed custody provider configuration must support the network. The administrator also needs a bound signing wallet. Missing any requirement prevents deployment from starting. Troubleshooting below covers each. The page tracks each deployment step after the platform accepts the request. Reading network history waits for indexed data to catch up with the chain. That step needs no action from you.
A deployment that fails shows Retry on that network's own row. The figure below shows what that restart actually does.
The Platform API reference documents the organisation network endpoints. Adding a network starts a deployment; check its status until it becomes Active or Failed.
Three states block disabling multi-network support for a non-default network; Failed and Disabled are exempt. Retry on a Failed row starts a new deployment attempt at Pending; it does not resume the old one.
Two switches with similar names
Two separate settings decide whether an organisation can use more than one network. Their names differ only in letter case. Setting one does not set the other.
| Switch | Scope | Who sets it | What it gates |
|---|---|---|---|
multi_network_enabled | The whole platform. It is a row in the platform_settings table. | The platform operator, directly in the database. No Console page and no API route writes it. | The network that a new organisation's first system can deploy to. When the row is absent or not true, only the platform default network is permitted. |
MULTI_NETWORK_ENABLED | One organisation. Read at GET /api/v2/settings/MULTI_NETWORK_ENABLED. | An organisation Owner or a platform administrator, when they confirm Enable multi-network support? on this page. | Everything after onboarding: the Your networks card, Add network, the network switcher for members, and requests that name a non-default network. |
The platform row decides which networks the platform lets an organisation start on. The organisation switch decides whether that organisation adds and uses networks beyond its default.
Set them in this order
-
Set the platform row first, and only if the first system of a new organisation must deploy to a network that is not the platform default. A platform operator runs this statement against the platform database, before that organisation completes onboarding:
INSERT INTO platform_settings (key, value) VALUES ('multi_network_enabled', 'true') ON CONFLICT (key) DO UPDATE SET value = 'true'; -
Complete onboarding. The organisation picks its first network, and that network becomes its default.
-
Set the organisation switch after onboarding. An Owner or a platform administrator selects
Enableon theMulti-network supportcard and confirmsEnable multi-network support?. Then add each further network withAdd network.
Skip step 1 when the organisation starts on the platform default network. Adding a network after onboarding needs only the organisation switch. The platform row never replaces step 3.
Troubleshooting
The Networks page shows only the Multi-network support card, although the platform allows more than one network
The platform row multi_network_enabled and the organisation setting MULTI_NETWORK_ENABLED are separate. The
organisation setting is off until an Owner or a platform administrator confirms Enable multi-network support?. Until
then the page shows only the Multi-network support card. Read the setting at GET /api/v2/settings/MULTI_NETWORK_ENABLED to see the current value for the active organisation.
A network is missing
Ask a platform administrator to confirm that the network exists and is enabled in the platform catalogue; this page can only add what the catalogue already offers. Adding an unavailable chain id fails with DALP-9353.
Adding a network fails because another deployment is already running
Add-network is serialized per organisation: only one deployment runs at a time, whether it is the organisation's own initial deployment or a previously added network still working through Pending or Deploying. Wait for that deployment to finish, then retry. The server refuses to start a second one in parallel and reports DALP-9172.
Adding a network fails with no custody provider covering it
Custody provider configurations are scoped to specific networks, so an administrator's signing account has nothing to provision on a network that no managed configuration names. Add or extend a managed custody provider configuration for the network in custody settings, then retry adding it. The server reports DALP-12040.
Adding a network fails because the administrator has no wallet to sign with
The deployment signs from the account of the administrator submitting the add, and that account needs an EOA (Externally Owned Account) wallet bound to it to do so. Bind a wallet to the account, then retry adding the network. The server reports DALP-9173.
A member cannot select a network you just added
Confirm multi-network support is on: the network switcher a member uses stays hidden entirely while it is off, whatever this list shows. If support is already on, confirm the added network's own status has reached Active; a member's picker only offers networks in that state, so one still Pending, Deploying, or Failed stays invisible to them even with support on.
Disabling multi-network support fails or the control is greyed out
Check whether a non-default network is Pending, Deploying, or Active. Any of these states blocks the disable request (DALP-9169). Wait for an in-progress deployment to finish, or ask a platform administrator to review the active network's configuration. This page has no override for the restriction.
Frequently asked questions
Does enabling or disabling multi-network support change which network is the organisation's default?
No, in either direction. The default network is fixed once, at organisation creation, before this page exists to visit. Turning multi-network support on only adds networks alongside that default; turning it off only removes the organisation's ability to use those additions. The default keeps running through either change, and this page carries no control that moves it.
What happens to a network's deployment if I navigate away from this page while it's Pending or Deploying?
Nothing stops. The deployment runs on the server, independent of the browser tab that started it, so it keeps going whether or not anyone is watching. Returning to this page later, from any session with access, shows whatever status the deployment has reached by then. No separate control exists to stop a submitted deployment either way.
Can I remove a network from this page once it's been added?
No control on this page removes a network once it deploys. Retry only appears on a Failed row, and confirming it resubmits a new deployment attempt for that same network rather than taking the network out of use. Taking a network out of use platform-wide is a platform administrator's job on the separate platform network catalogue, not this one.