A new organisation cannot hold settings, members or assets until the platform deploys its on-chain system on a network: the registries, permissions, compliance rules and asset templates that every later action uses. The Console's organisation setup collects what that deployment needs in four steps, deploys it, and shows each phase until the organisation is ready. If an organisation owner invited you, open the invitation link instead: it takes you to that organisation's join screen, and you skip this setup.
- Step 1 of 2: Account and organisation
- Step 2 of 2: Issue your first asset
An organisation is the unit that owns settings, members, roles and assets in the Console. A network is one blockchain the platform connects to, named by its chain ID.
The setup runs in four steps: Organisation, Custody provider, Your account and Deploy, and the deploy step can pause for custody approval or funding.
The Console opens the setup when your account has no active organisation and no pending invitation. If you have a pending invitation, the Console opens that invitation instead. If your email address is unverified, it opens “Verify your email to see your invitation” with “Send a new link” and “Sign out”.
The person who deploys must be an owner of the organisation or a platform administrator, the role that administers the whole DALP deployment. When your platform lets only platform administrators create organisations, everyone else sees “Ask a platform admin to create your organisation” instead of the deploy button, with the reason “Only a platform admin can create an organisation on this platform.” On a deployment that runs a single organisation and already has one, the Console signs a new account out instead of opening the setup.
Ask your platform operator, the team that runs your DALP deployment, which network, currencies and custody provider to use, and how much native currency the network needs for gas, because the deployment pauses until its wallets are funded. The setup shows only networks that are enabled and ready for a first deployment. When the platform offers no choice of network at onboarding, it shows the platform default network only.
If someone invited you to an existing organisation, your invitation link opens that organisation's join screen instead, where you can accept or reject the invitation. If the invitation was cancelled or has expired, the Console opens this setup form with a notice that says so and names the organisation when it can. Ask the person who invited you to send a new one. A link that was already accepted, declined or cancelled, or that has expired, no longer offers sign-up: it says what happened and offers “Sign in” instead.
What a new organisation sets up first
The setup asks for these, in this order. The first step, “Organisation”, covers items 1 to 3, and items 4 to 6 are the other three steps. Once you select “Continue” on the first step, the name, the network and the “Accounts and gas” choice cannot change, so settle them with your platform operator before you start.
- Organisation details: the name, the currencies the organisation works with, its default currency, and the languages its members can choose.
- Network: the network the organisation's first system deploys on. It becomes the organisation's default network and does not change later.
- Accounts and gas: the kind of wallet the organisation's users hold, and who pays the network fee, called gas, on the first network.
- Custody provider: the provider the platform signs with for this organisation. The step is skipped when the organisation already has one.
- Your account: the managed account that signs the deployment.
- Deploy: the platform deploys the system. When a wallet it needs is short of funds, the deployment pauses until you fund it.
After the deployment, set up your transaction PIN and recovery codes, submit your own KYC information, and invite your team. What to do next lists each.
Steps
Open the organisation setup
Sign in. The Console opens “Set up your organisation”. The track at the side lists the four steps: “Organisation”, “Custody provider”, “Your account” and “Deploy”. A summary panel repeats your choices as you make them.
If you leave the setup and come back, the Console opens the step you have not finished. Reloading the page during a deployment returns to its progress.
Enter the organisation details
Before you select “Continue” on this step, check the name, currencies, network and “Accounts and gas” choice. “Continue” creates the organisation and makes it your active organisation. After that, the name, the network and the “Accounts and gas” choice cannot change in the setup, and an organisation on smart wallets cannot switch back to EOA wallets.
The “Set up your organisation” form at the first of four steps.
In the screenshot, “Currencies” has five currencies chosen, all ten “Languages” are on, “Default currency” is set to “Euro (EUR)”, “Network” to local, and “Accounts and gas” to “Smart wallets, Paymaster-paid”. “Organisation name” is still empty, so “Continue” stays unavailable and shows the reason beside it. The side panel lists the values chosen so far.
Fill in the form:
- Organisation name: up to 32 characters. Members and invitees see this name. A name that another active organisation already uses is refused with “Another organisation already uses this name. Choose a different name.”
- Currencies: the currencies your organisation works with. The platform creates an exchange-rate feed for each currency other than the default currency. You can add currencies later, but you cannot remove one once it is enabled.
- Languages: the languages members can choose in the Console. English is always on. You can change this later on Languages.
- Default currency: the organisation's base currency. Pick at least one other currency in “Currencies”, because each exchange-rate feed pairs the default currency with another one.
- Network: the platform default network is preselected and marked “Default”. With one network available, the form shows it without a choice. The note under it reads “This organisation's first system deploys on this network, and it becomes the organisation's default. It can't be changed later.” To work on more networks later, an owner turns on multi-network support on Organisation networks.
“Accounts and gas” sets two things at once: the kind of wallet the organisation's users hold, and who pays gas on the network you chose. The options read as a wallet kind and a payer:
- Smart wallets, Paymaster-paid: users get smart wallets, contract wallets with approvals and recovery. On networks where the organisation's paymaster is set up, the paymaster pays the gas, so users need no gas balance. The first network ends on Paymaster-paid when its deployment leaves the paymaster with a ready signing key, and on Self-pay otherwise. On a network that charges gas, the deployment also asks for the paymaster's deposit, unless the network funds it on its own. The option appears only when the platform enables account abstraction, and it is then the default. Its note reads “You cannot switch back to EOA wallets later.”
- EOA wallets, Relayer-paid: users keep EOA wallets, standard wallets controlled by one private key, and an organisation wallet called the relayer pays their gas. Fund the relayer before users transact. On a network that charges no gas, the option adds a note that users can already send from their own wallets, so Self-pay is simpler.
- EOA wallets, Self-pay: each user pays gas from the balance of their own wallet. It is the default when the platform does not enable account abstraction.
The platform refuses smart wallets on a network that cannot run them, which is when account abstraction is off or the network has no paymaster set up. Continue then fails and nothing is created. The API answer names the network and the reason. Pick an EOA option for that network, or ask your platform operator to set up account abstraction on it first.
The wallet kind applies to the whole organisation. Who pays gas is a setting for each network, and each network you add later starts on Self-pay. An organisation on EOA wallets can move to smart wallets later on Transaction funding, and an owner changes the gas payer for each network on the same page. Whatever you choose, the deploying wallet pays for the transactions that deploy the organisation.
When “Continue” is disabled, the reason shows beside it. The form shows one reason at a time, in this order:
- “Enter an organisation name before you continue.”
- The name length rule.
- “Fix the organisation name before you continue.”
- “Pick at least one currency before you continue.”
- “Pick a default currency before you continue.”
- “Add a currency other than the default currency.”
- “No deployment network is available yet. Reload the page and try again.”
When the network list is empty, the form shows “No network available” and asks you to contact your platform operator.
Select “Continue”.
Set up the custody provider
The Console shows “Organisation custody provider” with the line “This organisation needs a provider the platform can sign with. It deploys the organisation and runs its automation.” A custody provider holds the signing keys for the organisation's accounts. A browser wallet signs only while its owner is present, so the setup offers managed providers only.
The Console skips this step when the organisation already has a managed custody provider enabled.
Under “Set up the custody provider”:
- Provider: choose the provider your platform operator named.
- Credentials: “Held by the platform” means the organisation signs through the provider account whose credentials the platform operator configured, so you enter nothing. The keys stay with the provider, or with the platform when the provider is the local key store. “Supplied by this organisation” connects your organisation's own workspace at that provider, and the form asks for the credentials the provider issued.
- Exclusive to this organisation: shown for credentials your organisation supplies. When on, keys from this configuration are used only in this organisation, and accounts from other organisations cannot use it. You cannot change it after creation.
The line “Deploys on” names the network you chose and EVM. The note under the form reads “This configuration's provider and credential source can't change later. You can add other providers and accounts after deployment.” Custody covers the providers you add later.
Select “Continue”. The button reads “Checking the connection…” while the platform checks the provider. When the check fails, the form shows the provider's error with “Try again”. Correct the details, then select “Try again”.
Create your account
The Console shows “Your account in” followed by the organisation name, with the line “You act in” the organisation “with this account.” The account card is marked “Managed”: the custody provider you chose in the previous step creates and holds the key, and the platform asks it to sign for you. With the local key store, the platform holds the key itself.
Select “Create account”. The card reads “Creating your account…” and then “Yours. Held by” the provider name.
If you already hold accounts that can act in this organisation, the Console shows “Choose how you act in” the organisation name. Select “Use this account” on the one to act with, or “Create a new account”. An account that signs with your own browser wallet cannot deploy, because the organisation needs an account the platform can sign with.
When your managed account belongs to another network, the step reads “Your managed account is linked to another network. Add a managed account for the selected deployment network.”
Deploy the organisation
The Console shows “Deploy” followed by the organisation name, and “Deploys the organisation's system on” the network name. The “Signing account” card shows the provider, the “Managed” and “Yours” badges, the account's signing address, and its smart wallet address when it has one. The note reads “This account signs the deployment.”
The “Modules” group lists each licensed module your deployment offers, such as “Primary market”, “Secondary market” and “Client portal”. Every module is ticked. Untick the ones your organisation will not use. A module you leave unticked is switched off for the organisation, and you can change this later in Organisation settings. Switch application layers on or off lists which modules a deployment offers.
A completed deployment cannot be run again or undone, and the organisation keeps its default network. Select “Deploy organisation”.
The Console shows “Deploying your organisation” with “This may take a few minutes. You can safely stay on this page.” The progress tree lists each deployment phase with its status, and the reason when a phase fails. The deployment runs on the server, so closing the page does not stop it.
While the deployment runs, it can pause in three ways:
- Custody approval: when your custody provider holds a transaction for approval, the phase shows “Pending approval” with “An approver must accept this step in your custody admin before the deploy can continue.” An approver accepts it in the provider's own admin console. Custody approval explains the approval model.
- Funding: every transaction pays gas in the network's native currency. When a wallet the deployment needs, such as the “Organisation creator wallet”, cannot pay, the Console shows “An account for your new organisation needs funds”. It names the recommended amount, the network and the current balance.
- Send the funds: the organisation has no other members, so you send them yourself. Select the confirmation that you are sending the stated currency on that network to show the funding address, then send the funds. The setup resumes on its own once they arrive, and “Funds received, continuing” confirms it. The funds become the organisation's money.
- Funding window: when the request has a deadline, the dialog shows when the window closes and how much time is left. If the funds do not arrive in time, it reads “Funding window expired” with what to do next, such as “Fund the address below, then try again.” Arrange the funds before you deploy.
- Full batches: the request can also name a larger balance that lets the deployment send its registrations in full batches. With less, it sends smaller batches, and the gas fees paid stay the same. Transaction funding covers funding requests in full.
- Background setup: when the indexer, the service that reads the chain into the platform, is catching up, the Console shows “Almost ready” and checks again after a countdown that follows the retry interval the platform suggests, at most about 30 seconds. Select “Check now” to check at once. The deployment continues on its own when the indexer is ready.
Continue to the dashboard
When the deployment completes, the Console shows “Organisation deployed. Finish your setup” with your wallet and a list of next steps. Next to “Go to dashboard”, the list shows the setup items you still have open, such as “Set your transaction PIN” and “Save your recovery codes”, and “Invite team members” when there is room. Select “Go to dashboard”. The new organisation becomes your active organisation.
What to do next
- Set your transaction PIN and recovery codes: select “Set your transaction PIN” on the completion screen, or open “Security” from the account menu at the top right. The Console also asks for this before your first signing action. Security explains wallet verification.
- Submit your KYC information: open Profile from the account menu and fill in Information. Profile covers the review.
- Invite your team: select “Invite team members”, or later open “Organisation participants”, then “Users”. Roles and permissions covers roles.
- Add networks: an owner adds more networks on Organisation networks.
- Issue an asset: continue with Issue your first asset.
When the deployment fails
A failed deployment shows “Deployment failed”, the error, and a reference. Two choices follow: “Try again”, described as “Reload and try the deployment again”, and “Contact support”. “Contact support” opens an email to SettleMint support at [email protected] on every instance, whoever runs it. When your institution runs its own support desk, give the reference to your platform operator instead.
Select “Try again”. The Console starts a new attempt straight away with the stored default currency, currencies, network and “Accounts and gas” choice, and shows the progress screen. The retry signs with the custody account you already hold on that network, or with a custody provider that covers it. When the earlier attempt already created the organisation's system on chain, the retry continues on that system instead of creating a second one.
When the Console no longer has the saved details, it says “We don't have your organisation's saved details to redeploy. Fill the form in and deploy again.” The form then opens as “Finish setting up your organisation” with “Your previous attempt didn't complete. Pick a currency to try again.” The name stays locked. When the earlier attempt recorded them, the account choice reads “Set during your earlier attempt. You cannot change it on retry.” and the network reads “Chosen during your earlier attempt. It can't be changed on retry.”
A retry is refused while another attempt for the organisation is running, and for an organisation that already finished its setup.
A smart-wallet deployment also checks the balance of the organisation's bundler, the wallet that sends its smart account bundles. When it is below target, the platform raises a funding request for the operator to fulfil. The platform sizes that funding request from the network's live fee quote. When the network has no fresh quote, the deployment fails at that step with a retryable error saying the network's fee pricing is unavailable, and does not continue with an unfunded bundler. Ask your platform operator to restore the network's RPC and fee policy, then select “Try again”.
When the deployment stalls
A deployment that stops reporting does not stay on the progress screen for ever. The platform checks for stalled deployments every minute. A deployment that has reported nothing for 90 seconds, with no running process behind it, is marked failed with the reason “The deployment stopped reporting and no execution is running it.” The Console then shows the failed screen, and “Try again” starts a new attempt as described above.
When the connection to the progress stream drops, the Console reconnects and reads the deployment's state again, so a reload is not needed.
The failed screen appears only when the platform reports that the deployment failed. A progress stream that drops or fails before the deployment reports a result never shows it. The Console keeps the steps it showed, adds “Reconnecting to live updates”, and reads the deployment's status every 10 seconds. While the platform still runs the deployment, the Console reconnects and shows the current step. When the platform reports it complete or failed, the Console shows that result. When the platform holds no deployment for the organisation, the Console returns to the deploy step so you can start one. Accepting an invitation follows the same rules.
Create another organisation
On a platform that runs several organisations, a person who already runs one can set up another. Open the account menu at the top right, point at Organisation and choose “Create organisation”. The menu offers it when creating organisations is not limited to platform administrators, or when you are a platform administrator.
The Console opens the same setup with an editable name and the same four steps. Opening it changes nothing until you submit the first step.
- Before you submit the first step, “Cancel” returns you to the dashboard.
- After the first step and until the new organisation is deployed, “Switch organisation” takes you back to your other organisations. It shows on the custody provider, account and deploy screens and on the failed screen.
- Starting the setup again resumes your unfinished organisation instead of creating a second one. Until it is deployed, it stays in the Organisation submenu of the account menu, and choosing it resumes its setup.
When your organisation is archived
A platform administrator can archive an organisation. When every organisation you belong to is archived, the Console shows “Your organisation is archived” with “A platform administrator archived your organisation and can restore it.” and “Sign out”. When you may create an organisation, it also offers “Create an organisation”, and the setup form then shows “You are not a member of an active organisation. Create one, or ask a platform administrator to restore yours.”
The screen does not refresh on its own. After a platform administrator restores the organisation, reload the page or sign in again.