# User onboarding

Source: https://docs.settlemint.com/docs/operators/user-guides/runbooks/onboard-user-im
Register an onboarded wallet in the identity registry, issue KYC verification, and confirm the user is ready for asset rules that require identity claims.



Identity Managers register onboarded accounts in the identity registry. Registered accounts can then be evaluated by DALP compliance rules.

The runbook covers the handoff from account onboarding to registry registration. The workflow then shows where KYC claim issuance by a trusted issuer fits. Asset rules can still require more claims.

## Prerequisites [#prerequisites]

Before you start, confirm these conditions:

* You have the **Identity Manager** role for registry registration.
* You have the **Verification Issuer** role for issuing KYC verifications, or you have a verifier ready to take over after registration.
* The issuer identity that will issue the KYC verification is configured as a [trusted issuer](/docs/operators/user-guides/compliance/configure-trusted-issuers) for the KYC topic.
* The user has completed [User Onboarding](/docs/operators/user-guides/user-management/user-onboarding) and has an on-chain identity address.
* The operator wallet used for the transactions has enough native gas for the selected network.

## How the workflow fits together [#how-the-workflow-fits-together]

DALP separates account creation, registry registration, and claim issuance. A user can have an account and wallet before the identity registry recognizes that identity address. Registering the identity records the jurisdiction used by compliance rules. Issuing the KYC verification adds the claim that KYC-aware asset policies can check.

| State                | What it means                                                                      | What to do next                                             |
| -------------------- | ---------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| Pending registration | The user has completed onboarding, but the identity address is not registered yet. | Register the identity with the correct jurisdiction.        |
| Registered           | The identity address is in the registry.                                           | Issue the required verification claims.                     |
| Verified             | The user has the KYC verification from a trusted issuer.                           | Check whether the target asset needs any additional claims. |

## Onboard the user [#onboard-the-user]

<Steps>
  <Step>
    ### Verify user readiness [#verify-user-readiness]

    1. Open **Participants** > **Users**.
    2. Find the user.
    3. Confirm the user has an **Identity address**.

    When no identity address is present, pause this runbook. Ask the user to complete [User Onboarding](/docs/operators/user-guides/user-management/user-onboarding). After onboarding completes, return to the user profile.

    ![User list showing the identity address column](/docs/runbooks/onboard-user-im-user-list.webp)
  </Step>

  <Step>
    ### Register the identity [#register-the-identity]

    Registration adds the user's identity address to the on-chain identity registry with the jurisdiction used by compliance rules.

    Follow [Register User](/docs/operators/user-guides/user-management/register-user) to:

    * select the user from the Users list;
    * click **Register Identity**;
    * choose the jurisdiction from the user's approved documentation;
    * submit the registration transaction.

    <Callout type="info" title="Jurisdiction drives compliance checks">
      Select the jurisdiction from the user's legal residence or incorporation evidence. Compliance modules can use that
      country code when evaluating whether an asset transfer is allowed.
    </Callout>

    After the transaction confirms, reopen or refresh the user profile and confirm the user shows **Registered**.

    ![User profile showing Registered status](/docs/runbooks/onboard-user-im-registered.webp)
  </Step>

  <Step>
    ### Issue the KYC verification [#issue-the-kyc-verification]

    With the identity registered, follow [Verify KYC](/docs/operators/user-guides/compliance/verify-kyc) to issue the KYC verification from a trusted issuer identity:

    * open the user's profile;
    * click **Manage verifications**;
    * click **Issue verification**;
    * select &#x2A;*Know Your Customer (KYC)**;
    * submit the verification transaction.

    <Callout type="info" title="Trusted issuer status matters">
      DALP compliance rules only accept a claim when the issuer is trusted for that claim topic. A green shield next to the
      KYC verification shows the issuer is trusted for that topic.
    </Callout>

    ![Verification list showing KYC with a trusted issuer shield](/docs/runbooks/onboard-user-im-kyc-verified.webp)
  </Step>

  <Step>
    ### Confirm completion [#confirm-completion]

    After the KYC verification transaction confirms:

    * the user's profile shows the KYC verification;
    * the verification shows the trusted issuer shield;
    * asset rules that require KYC can evaluate the user;
    * asset-specific claims still need to be issued separately.

    ![Fully verified user profile](/docs/runbooks/onboard-user-im-complete.webp)
  </Step>
</Steps>

## Troubleshooting [#troubleshooting]

| Issue                                      | What to check                                                                                                                   |
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
| Register Identity is not visible           | Confirm your account has the Identity Manager role and the user has an identity address.                                        |
| Registration transaction fails             | Confirm the operator wallet has gas, the selected jurisdiction is correct, and the user identity is not already registered.     |
| Issue verification is not visible          | Confirm your account has the Verification Issuer role, claim-creation permission, and a registered identity for the user.       |
| KYC verification has no green shield       | Confirm your issuer identity is configured as a trusted issuer for the KYC topic.                                               |
| User still cannot receive the target asset | Check whether the asset requires more claims, trusted issuers, jurisdiction rules, or investor-status verifications beyond KYC. |

## Related guides [#related-guides]

* [User Onboarding](/docs/operators/user-guides/user-management/user-onboarding) explains the account and wallet setup that must happen before this runbook.
* [Register User](/docs/operators/user-guides/user-management/register-user) covers the registry transaction in detail.
* [Verify KYC](/docs/operators/user-guides/compliance/verify-kyc) covers issuing verification claims.
* [Configure Trusted Issuers](/docs/operators/user-guides/compliance/configure-trusted-issuers) explains how to trust issuer identities for specific claim topics.
* [Claims and identity](/docs/architects/architecture/concepts/claims-and-identity) explains how DALP evaluates identity claims during token operations.