Create or invite users from the DALP workspace

Create or invite users from the Users workspace, and know when to choose direct creation instead of an invitation.

The Users workspace gives administrators two onboarding paths. You can send an invitation that the recipient accepts, or you can create the user account, wallet, and on-chain identity immediately without emailing the recipient.

Use direct creation when you need an account ready now: a demo user, training account, test holder, or passive token holder who only needs to receive assets. Use an invitation when the recipient should control the first login and complete their own onboarding.

Prerequisites

Permission to manage users in the current organisation.
Permission to invite or create users (the available button depends on your workspace).
Wallet verification (PIN or 2FA) when creating a user directly.

Choose the right onboarding path

Use case	Recommended path	Why
Prepare demo, test, or training accounts	Create user	The account, wallet, and identity are ready before the session starts.
Prepare passive holders who only need to receive assets	Create user	The administrator can create the account without waiting for the holder to accept an invitation.
Add active platform operators	Invite user	The recipient controls the first login and can complete their own onboarding.
Add external users under stricter credential policy	Invite user	The user starts from the invitation flow instead of inheriting an administrator-created account.

Create a user directly

Navigate to user management

Go to Participants > Users in the sidebar. The button appears as "Create or invite user" when your permissions allow either path.

Users page with Create user button

Switch from invitation to direct creation

Click "Create or invite user". If the form shows a "Send invitation email" toggle, turn it off. The form then asks for the display name and email address used for the new account.

Enter the user details

Enter the recipient's display name and email address, then click "Create user". DALP validates the email address before it opens the verification prompt.

Verify identity creation

Complete the verification prompt with your wallet verification method. This authorises the wallet and identity transactions.

If DALP opens wallet security setup instead, finish the PIN and recovery-code wizard before retrying.

Confirm the account is ready

Once the transactions confirm, the user appears in the Users table with their wallet and identity details. The table shows whether the identity is registered or still pending registration.

What DALP creates

Direct creation creates the user account and the blockchain components needed for that user to hold assets.

Created item	What it means operationally
User account	The email address becomes the sign-in identifier.
Generated password	Administrators do not know the password. The user must reset it before signing in.
Wallet address	DALP creates the user's externally owned account.
Managed private key storage	The platform manages the private key for the created wallet.
On-chain identity contract	The user gets the identity used by registry and compliance workflows.
Identity registry state	The Users table shows whether the identity is registered or pending registration.

After direct creation

If the user must sign in, direct them to the platform login and password reset flow.
If the Users table shows the identity as pending, register the user before relying on the account in asset workflows.
Grant administrative roles separately if the user will manage users, assets, compliance, or platform settings.
Issue or update KYC and other required verifications according to your organisation policy.
Add the user to the registries, cap tables, approvals, or distribution processes that require the account.

Finish a user whose identity creation did not complete

Direct creation runs in two stages. DALP first creates the account and wallet, then deploys the on-chain identity. If the second stage does not finish, after a network or transaction error, the account and wallet still exist but the identity does not. The Users table shows the identity as pending in this case.

To finish a stranded account, run direct creation again with the same email address. When the email already belongs to a user in your organisation that has a wallet but no on-chain identity, DALP resumes identity creation for the existing wallet instead of reporting a duplicate. You do not need to delete and recreate the account.

DALP reports that the email already exists only when the account is not a partial failure. This covers a user that already has an on-chain identity, a user outside your organisation, or an account DALP cannot resolve.

The created user can set their own password through the login page:

Open the platform login page.
Choose "Forgot password" or "Reset password".
Enter the email address used during creation.
Follow the reset instructions and set a new password.
Sign in with the email address and new password.

Limits and operating notes

Direct creation does not send an invitation email. Use invitations when the recipient should start from an invitation link.
Administrators cannot read the generated password. Users who need access must reset their password.
Directly created users skip invitation onboarding, so review their roles, registry membership, and compliance status before relying on the account.
Creating the wallet and identity requires wallet verification from the administrator who runs the step. If DALP opens PIN or recovery-code setup, complete that setup first and then create the user.

Troubleshooting

Issue	Solution
Create or invite button is not available	Check that you have user management permissions in the current organisation.
Direct creation is not available	Check that your account can create users, not only send invitations.
User creation fails	Confirm the email address is valid, complete the required fields, finish any PIN or recovery-code setup shown by DALP, then retry. If the account and wallet were created but the identity did not finish, run direct creation again with the same email to resume identity creation.
User cannot sign in	Ask the user to reset their password from the login page and confirm the email address matches the created account.
Identity still shows pending	If the user has a wallet but no identity address, the identity step did not complete: run direct creation again with the same email to resume it. If the identity exists but is not yet registered, register the user instead, then refresh the Users table. See Register user.

Register user - Register a wallet-backed user identity
Add administrators - Grant administrator access after creation
Admin operating model - Understand administrator responsibilities
Developer guide: create users - Create users through the API

Create users

On this page