Organisation custody
Manage the organisation's custody provider catalog, credentials, and execution health.
Custody manages the organisation's custody provider catalog. Add provider configurations, choose which ones accept new accounts, and manage their credentials and execution health. Each existing custody account keeps its provider binding when you add or disable another configuration.
Account creation and execution have separate controls. Disable new accounts removes a configuration from account creation. Quarantine execution blocks execution through that configuration and requires an audit reason. Use the control that matches the intended effect.
Steps
Review the provider catalog
Open Organisation settings, then Custody. Each configuration shows its provider, network scope, signing type, execution health, and availability for new accounts. The investor-provider badge identifies the configuration offered during investor onboarding.
A configuration can be available for new accounts while its execution health needs attention. Check both states before directing participants to it.
Add a provider configuration
In Add custody provider, select the provider and enter the network identifier. Supply the labelled fields the form shows for that provider. Credential fields are masked and write-only: use the show control to check what you typed; the platform never displays a stored credential. A provider without a known field set uses a masked key and value editor. A browser wallet does not require server-held signing credentials. The onboarding custody provider step uses the same form.
Select Add and probe provider. The platform checks the configuration before making it available for account creation. If the probe fails, correct the reported network, connection, or credential issue before trying again.
Control new account creation
Use Enable new accounts or Disable new accounts on the configuration. To use a healthy, enabled configuration during investor onboarding, select Make this the default investor provider.
The default is always offered to investors. To let investors choose another healthy configuration enabled for new accounts, select Also offer to investors on it. When more than one configuration is offered, the investor portal asks the investor to choose during onboarding between a browser wallet and a managed account, and suggests the default. The investor portal cannot open an embedded wallet yet, so it shows an offered embedded-wallet configuration as unavailable and never selects it. A configuration that is not offered is never listed, and the platform refuses a participant that an investor creates on it. An Owner of the active organisation or a platform administrator can still create a participant's managed account on it, provided it is healthy, enabled for new accounts, and lists the account's network. Disabling new accounts on a configuration withdraws its offer. When only the default is offered, the investor goes straight to it.
Changing this selection does not move existing accounts to another provider. Check the selected investor-provider badge after saving.
Rotate managed credentials
Fill in only the metadata and credential fields you want to change. Leave a credential field empty to keep its current stored value. To remove an optional stored credential, select Replace every credential, which replaces the whole credential set with the fields you enter. Then select Probe and rotate credentials. The platform probes the replacement and checks its custody identity before saving it. Rotation preserves the configuration's provider and credential source.
If another administrator rotates the same configuration at the same time, a version conflict can reject one request. Refresh the configuration and check the saved state before retrying. Do not assume that an error means no change was saved.
Quarantine or recover execution
Enter an audit reason, then select Quarantine execution to block the configuration. Correct the underlying incident before selecting Recover execution with a new reason.
The configuration card shows the latest quarantine or recovery event, including the actor, time, and reason. Probe checks the provider connection; use the health state and incident details together when deciding whether execution can resume.
Troubleshooting
No custody providers enabled
Add a provider configuration and confirm that it is healthy and available for new accounts. Participants need an available configuration before they can create custody accounts.
A credential rotation fails
Read the reported error before retrying. Check the field values, provider connection, network scope, and custody identity. Rotation cannot change the provider or credential source; create a separate configuration for that change.
Disabling new accounts did not stop existing accounts
This control affects account creation. Use quarantine when execution through the configuration must stop, and record the reason. Existing accounts retain their provider binding.
Delete unused is rejected
The platform checks whether the configuration is still in use before deleting it. Keep the configuration while accounts depend on it. Disable new account creation or quarantine execution when that is the required outcome.