Invite users
Send invitations for team members and external partners to join your platform from the Users page, optionally pre-assigning their platform roles, and understand what the recipient completes after accepting.
Invitations add people to your organization through a self-service sign-up flow. An owner or admin creates the invitation from the Users page, and the recipient accepts the link with the same email address that received the invitation. DALP checks the recipient email before the invitation can join the organization, so invitation links should not be forwarded to a different user.
Prerequisites
You need owner or admin access to Participants > Users, a completed platform setup with an organization created, and email configured for delivery or a secure channel to share the link manually.
Invite a user
Open the Users page
Go to Participants > Users in the sidebar. DALP shows user administration here. When your role can manage invitations, the page includes Users and Invitations tabs.
Start the invitation
Click Create or invite user. The sheet opens in invitation mode when your role can send invitations.
Leave Send invitation email enabled to create an invitation for the recipient. If email delivery is configured, DALP sends the invitation email automatically. If email delivery is not configured, DALP creates the invitation and shows a link you can copy.
Assign roles at invite time (optional)
The same sheet includes a role picker. Select one or more platform roles, grouped by responsibility, to grant the new user the moment they join. Leave the picker empty for a view-only invitation that grants no platform authority.
Granting roles is privileged. DALP asks you to confirm with your wallet PIN, a one-time passcode, or multi-factor verification before creating the invitation. A view-only invitation needs no confirmation.
DALP records the chosen roles on the invitation. It grants them on-chain automatically once the recipient accepts and finishes onboarding, unless the wallet that created the invitation is unavailable, deprovisioned, or no longer holds the admin role needed to grant them. In that case the invitation still completes, but the roles remain for manual grant afterward. You set the roles once, at invite time, rather than inviting the person and then granting each role separately after they join.
When the automatic grant does not complete, check the user's role membership after onboarding and grant any missing roles manually. See Add administrators for what each role allows and how to grant or change roles for users who have already joined.
Enter the recipient email and submit
Enter the recipient's email address and submit the form. DALP creates a member invitation for that address.
Submitting shows a progress toast: "Sending invitation..." while the request is in flight. When the request finishes, a success notification replaces it. The notification shows a confirmation, an error with a named reason, or a shareable link when email delivery is not configured. Error reasons include the email already belonging to a member or having a pending invitation.
The form does not clear without a result. If submitting appears to do nothing, wait for the notification and read the reason it returns.
The invitation link uses this shape:
/auth/invitation?invitationId=<id>&email=<invited-email>The recipient must sign up with the invited email address. If the browser is already signed in as another user, ask the recipient to sign out first. A private browser window is the safest option.
Share the link when email is not configured
When DALP cannot send email, the invitation sheet displays a link after submission.
Copy the link and send the link through a secure channel. Keep the invitationId and email query parameters unchanged.
Track invitation status
Open the Invitations tab on Participants > Users to monitor pending and accepted invitations. DALP keeps an invitation pending until the recipient accepts the invitation and completes sign-up.
What the recipient completes
After opening the invitation link, the recipient follows one of two paths:
| Recipient state | What happens |
|---|---|
| New user | DALP sends the recipient to the invitation sign-up page with the invited email pre-filled. After sign-up, the recipient returns to the invitation onboarding flow. |
| Existing signed-in user | DALP can accept the invitation from the authenticated invitation page when the signed-in user's email matches the invitation. |
During invitation onboarding, DALP validates that the invitation is still usable and belongs to the signed-in recipient, then accepts the invitation for that organization. The onboarding workflow creates an EOA wallet when the user does not already have one, creates or attaches the user's on-chain identity for the organization's system, grants organization membership, and provisions the user's smart wallet when advanced accounts is enabled.
If the invitation was already accepted, DALP resumes or finalizes the onboarding flow instead of asking the user to start again. If the invitation was rejected, canceled, expired, or opened by the wrong email address, DALP blocks the request and shows an error or retry path.
Once accepted, DALP offers the recipient a choice: set up account security or continue to the dashboard.
The invitation flow does not ask for a PIN or recovery codes before the recipient confirms.
Ask new team members to finish account security after the account joins the organization. DALP prompts for a wallet PIN later if a signing step needs one.
See User onboarding for the complete new-user flow.
When to create the user directly instead
Turn off the Send invitation email toggle only when you need DALP to create the account, wallet, and identity immediately. With direct creation, the administrator verifies the identity step and DALP does not send the normal invitation email to the recipient.
Use direct creation for controlled demos and pre-provisioned operational accounts. Direct creation also fits environments where an administrator owns the initial wallet and identity setup.
For ordinary team or partner onboarding, keep the invitation flow enabled.
Troubleshooting
| Issue | Solution |
|---|---|
| Invitation email not received | Check spam or junk folders, verify the email address, then use the invitation link from the Invitations tab if email delivery is unavailable. |
| User cannot accept invitation | Confirm the link was not modified, the platform URL is reachable, and the invitation is still pending. Send a fresh invitation if needed. |
| "You are not the recipient" | Sign out and sign up with the exact invited email address. A private browser window is the safest way to avoid an existing session using the wrong email address. |
| Cannot create invitation | Verify that you have owner or admin access to the Users page and that the email address is valid. |
| Error message after submitting | The invitation could not be created. Read the reason in the message: the email may already belong to a member or already have a pending invitation. Check the Invitations tab, then resend or invite a different address. |
Related guides
- Create users directly - Create accounts, wallets, and identities without sending an invitation
- User onboarding - New user experience after invitation acceptance
- Add administrators - Grant or change platform roles, including for users who joined without roles
- Verify KYC - Issue KYC verifications for users
How DALP administration is organized
Understand how DALP separates organisation administration, invitations, platform permissions, API keys, webhooks, providers, data feeds, security settings, and operator wallets.
Create or invite users
Create or invite users from the Users workspace, and know when to choose direct creation instead of an invitation.