Create your account and organisation
Create your Console account and deploy the organisation that owns your first DALP configuration.
Create the account you use to enter the Console, the platform's web application for operating assets. Then deploy the organisation that holds its settings, roles, and assets on the selected network. This tutorial ends when the Console confirms that the organisation is deployed and lets you continue to the dashboard.
An organisation groups the settings and roles used to operate assets. During setup, you choose its default network and currencies, then configure custody for its wallets.
You start with a signed-in Console account and nothing else. This tutorial produces one deployed organisation, using the selected default network, currencies, and custody provider. The default network stays fixed. Custody settings can add supported provider configurations later; existing accounts keep their custody binding. That organisation holds a wallet secured by a PIN and its recovery codes, and the dashboard confirms the organisation is active.
Steps
Open the organisation setup
Sign in with your account. The Console opens "Set up your organisation" when your account has no active organisation.
Enter the organisation details
Enter the "Organisation name", then choose the network and currencies supplied by the platform operator. Choose carefully: the network becomes the organisation's permanent default, and the Console offers no later screen to change it.
"Accounts and gas" sets two things: the kind of wallet your organisation's users hold, and who pays gas, the network fee, on the network you just chose. Choose one of three options:
- Smart accounts, Paymaster-paid: gives your organisation's wallets smart walletA Smart Wallet lets a tenant require several signers to agree before an instruction moves assets, with the rule enforced on chain, not by one private key.Read the concept capability. On each network where the organisation's paymaster is set up, it pays the gas, so users need no gas balance. Wallets gain an approval rule you can require before a wallet acts, and recovery. A new wallet still starts with a single signer, so nothing about daily use changes until you add more signers and a threshold later. You cannot switch back to plain wallets later. The option appears only when the platform has the account-abstraction feature, and it is the default there.
- Plain wallets, Relayer-paid: users keep standard wallets, and an organisation wallet called the relayer pays their gas on this network. Fund the relayer before users transact. If the network charges no gas, the Console notes that users can already send from their own wallets, so the relayer only adds an extra step and
Self-payis simpler. - Plain wallets, Self-pay: each user pays gas from the balance of their own standard wallet, a single private key with no on-chain approval rule. It is the default when the platform has no account-abstraction feature.
With plain wallets, the choice of who pays applies to this first network only. Each network you add later starts with users paying. You can change who pays on each network later in Organisation settings, under Transaction funding, with Change gas payer, which acts on the network the sidebar has active. With plain wallets, you can move the organisation to smart wallets later on the Wallet type page, when the platform offers them.
The transactions that deploy the organisation are paid by the deploying wallet whichever option you choose. Transaction funding compares the options in full.
If you cannot select "Continue", read the reason below the button. The form shows one reason at a time and updates it as you correct the details. For example, if your default currency is EUR and "Currencies" contains only EUR, add another approved currency, such as USD. If the message says no deployment network is available, reload the page and try again. The reason disappears when the details pass validation or submission starts.
Select "Continue". The Console saves the organisation and opens the custody provider step.
Set up the custody provider
The Console shows "Organisation custody provider". The organisation needs a provider the platform can sign with: it deploys the organisation and runs its automation.
Under "Set up the custody provider", "Provider" preselects the first managed provider. Select the exact option supplied by your platform operator. "Credentials" shows "Held by the platform" when the platform operator holds the signing keys and you supply no credentials. "Supplied by this organisation" connects your own external custody provider's workspace; paste the credentials the provider gave you. The line "Deploys on" names the network you chose in the previous step.
Select "Continue". The button reads "Checking the connection…" while the platform checks the provider. If the check fails, the Console shows the provider's error; correct the details and select "Try again".
The provider and credential source of this configuration cannot change later. After deployment, Custody settings can add other provider configurations and rotate credentials. Existing accounts keep their custody binding.
For the account and approval models behind these choices, read Smart Wallet and Custody Approval.
Create your account
The Console shows "Your account in" followed by the organisation name. You act in the organisation with this account. One card shows the provider with the "Managed" badge: the platform creates the key, holds it, and signs for you.
Select "Create account". The card shows "Creating your account…" and then the account address with "Yours". If the Console asks you to choose between accounts you already hold, select "Use this account" on the one to act with, or "Create a new account".
Deploy the organisation
The Console shows "Deploy" followed by the organisation name. The "Signing account" card shows the address of the account from the previous step, the provider, "Managed", and "Yours". This account signs the deployment.
Select "Deploy organisation". The Console shows "Deploying your organisation" and states that this may take a few minutes and that you can stay on the page. Deploying is one or more transactions on the network you selected, and each needs a small amount of that network's native currency to pay gas. If a wallet involved in the deploy, for example the "Organisation creator wallet" or the "Organisation bundler wallet", does not have enough, the Console opens "Fund your wallet to continue" with the recommended amount, the network, the current balance, and the address to send to. Send the stated amount to that address; the deploy resumes on its own once the funds arrive, and you do not need to do anything else. If the Console asks you to confirm your identity, it is asking for the six-digit PIN that authorises your wallet's transactions; set one if you have not already, then enter it.
If deployment fails, select "Try again". The Console uses the saved organisation details to submit another attempt. If those details are unavailable, it asks you to enter them again. The "Accounts and gas" choice stays as you made it in the earlier attempt, and the Console shows "Set during your earlier attempt. You cannot change it on retry." A successful deployment has no undo action, so confirm the default network before submitting.
If you leave the setup and come back, the Console opens the first step you have not finished.
Continue to the dashboard
When the deployment completes, the Console confirms that the organisation is deployed and offers two choices, "Go to dashboard" and "Invite team members". Choose "Go to dashboard". The active session then uses the new organisation.