# User guides

Source: https://docs.settlemint.com/docs/operators/introduction
Console-led operating guides for administrators and operations teams running regulated digital asset workflows on DALP.



These guides cover every console task after the environment is ready to run. The [operator index](/docs/operators) routes you to the right task guide across platform setup, participant onboarding, asset servicing, compliance, data feeds, and the system add-ons and runbooks your operations team needs.

This section is for signed-in console operators. API integration developers use the [Developer guides](/docs/developers) instead. A platform administrator prepares roles and system components. Identity and compliance teams register participants and maintain policy enforcement. Asset operators create and service tokens. Operations teams run add-ons and repeatable procedures.

## Operating model [#operating-model]

DALP organises console work into seven areas: platform setup, participant management, asset creation and servicing, compliance review, data feeds, and add-ons. Runbooks cover repeatable end-to-end procedures. Each area maps to a distinct operator role with its own permissions and audit trail.

<Mermaid
  chart="`
flowchart TD
Admin[&#x22;Platform administrator&#x22;] --> Setup[&#x22;Platform setup&#x22;]
Admin --> Users[&#x22;User management&#x22;]
ComplianceOperator[&#x22;Compliance operator&#x22;] --> Compliance[&#x22;Compliance controls and evidence&#x22;]
AssetOperator[&#x22;Asset operator&#x22;] --> AssetCreation[&#x22;Asset creation&#x22;]
AssetOperator --> AssetServicing[&#x22;Asset servicing&#x22;]
DataOwner[&#x22;Data owner&#x22;] --> Feeds[&#x22;Data feeds&#x22;]
OperationsTeam[&#x22;Operations team&#x22;] --> Addons[&#x22;System add-ons&#x22;]
OperationsTeam --> Runbooks[&#x22;Runbooks&#x22;]

Setup --> Controls[&#x22;Roles, wallets, settings, components&#x22;]
Users --> Controls
AssetCreation --> Tokens[&#x22;Token terms and permissions&#x22;]
AssetServicing --> Tokens
Compliance --> Evidence[&#x22;Identity, claims, templates, backing checks&#x22;]
Feeds --> Evidence
Addons --> Settlement[&#x22;Settlement and yield operations&#x22;]
Runbooks --> Recovery[&#x22;Repeatable operating procedures&#x22;]
`"
/>

The console does not replace legal policy, custody rules, bank architecture, or external provider obligations. You use it to apply the operating model your organisation has already chosen. DALP records the product workflow and the audit trail for each step.

## Match the interface to your role [#match-the-interface-to-your-role]

DALP gives each operator a distinct entry point. Use the console for guided human workflows and evidence review. Use the API or generated client for system-to-system work. Subscribe to events when downstream systems need to react after DALP records state changes.

| Operator persona                | Primary interface                                     | Typical work                                                                                                             | Start here                                                                                                        |
| ------------------------------- | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- |
| Platform administrator          | Console platform settings and user management         | Prepare organisations, administrators, roles, system components, webhooks, feeds, and add-ons before asset teams operate | [Platform setup](/docs/operators/platform-setup/platform-overview)                                                |
| Compliance or identity operator | Console participant and compliance workspaces         | Manage users, entities, KYC, trusted issuers, verification topics, and policy templates                                  | [Compliance](/docs/operators/compliance/overview)                                                                 |
| Asset operations team           | Console asset designer and asset detail pages         | Create assets, manage token roles, mint, burn, pause, force transfer, and review token events                            | [Create asset](/docs/operators/asset-creation/create-asset)                                                       |
| Operations or settlement team   | Console add-on workspaces and runbooks                | Run settlement, yield, recovery, and other repeatable cross-workflow procedures                                          | [Review add-on workspaces](/docs/operators/system-addons/review-addon-workspaces)                                 |
| Integration developer           | Platform API, generated TypeScript client, and events | Automate asset, user, compliance, settlement, webhook, and monitoring workflows without screen work                      | [Developer guides](/docs/developers) and [Events](/docs/api-reference/tokens/token-events)                        |
| Auditor or reviewer             | Read-side console views, API reads, and event history | Review permissions, identities, asset state, transaction history, webhook delivery, and logs                             | [Authorization](/docs/compliance-security/security/authorization) and [Operability](/docs/architects/operability) |

Your signed-in console account still needs the relevant platform permission, wallet confirmation when required, and on-chain role for the submitted operation. Console access does not grant mint, burn, recovery, compliance, or policy authority by itself. Use [Authorization](/docs/compliance-security/security/authorization) when designing your role sets.

## Choose the right guide [#choose-the-right-guide]

| If you need to...                                                      | Start here                                                                             | Typical owner                                         |
| ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | ----------------------------------------------------- |
| Prepare the workspace before asset teams operate                       | [Platform setup](/docs/operators/platform-setup/platform-overview)                     | First administrator or permission manager             |
| Monitor user lifecycle events after participant changes                | [Webhook events](/docs/api-reference/tokens/token-events)                              | Identity manager or organisation administrator        |
| Create a tokenised asset from the console                              | [Asset creation](/docs/operators/asset-creation/create-asset)                          | Asset issuer or asset operator                        |
| Mint, burn, pause, transfer, or update token roles                     | [Asset servicing](/docs/operators/asset-servicing/mint-assets)                         | Asset operator, custodian, or supply manager          |
| Register an existing EVM token in the console                          | [External token registration](/docs/operators/asset-servicing/register-external-token) | Asset operator or registry manager                    |
| Maintain named wallet records for operator forms                       | [Address book contacts](/docs/operators/user-management/manage-address-book-contacts)  | Identity manager or operations team                   |
| Open private KYC, organisation, or administrator files                 | [Private file access](/docs/operators/user-management/open-private-files)              | Document owner, organisation member, or administrator |
| Configure policy templates, KYC, trusted issuers, or collateral checks | [Compliance](/docs/operators/compliance/overview)                                      | Compliance manager or verification operator           |
| Publish or update data that assets depend on                           | [Data feeds](/docs/operators/data-feeds/overview)                                      | Data owner or operations team                         |
| Run optional settlement, token sale, or yield workflows                | [System add-on workspaces](/docs/operators/system-addons/review-addon-workspaces)      | Operations team with the required add-on roles        |
| Follow a repeatable scenario across several pages                      | [Runbooks](/docs/operators/runbooks)                                                   | Implementation lead or operations team                |

<Callout type="info" title="For developers">
  Looking to automate these workflows programmatically? See the [Developer guides](/docs/developers) for API integration
  and type-safe client usage.
</Callout>

## Platform setup [#platform-setup]

<Cards>
  <Card title="Platform overview" href="/docs/operators/platform-setup/platform-overview">
    Complete reference for platform setup, administrator roles, and system configuration. Start here before inviting other administrators or configuring asset programmes.
  </Card>

  <Card title="First administrator setup" href="/docs/operators/platform-setup/first-admin-setup">
    Create the first administrator account and prepare the platform for use.
  </Card>

  <Card title="Add administrators" href="/docs/operators/platform-setup/add-admins">
    Grant administrative permissions to users. Each role carries a defined set of console capabilities and on-chain authority.
  </Card>

  <Card title="Change admin roles" href="/docs/operators/platform-setup/change-admin-roles">
    Update the roles of existing platform administrators. Role changes take effect immediately and the platform records each update in the audit log.
  </Card>
</Cards>

## User management [#user-management]

<Cards>
  <Card title="User onboarding" href="/docs/operators/user-management/user-onboarding">
    See what new users encounter when they first join the platform, including identity registration, wallet setup, and first-login steps.
  </Card>

  <Card title="Invite users" href="/docs/operators/user-management/invite-users">
    Send invitations to team members and external partners. Each invitation assigns a role and routes the recipient through the right onboarding path.
  </Card>

  <Card title="Create users" href="/docs/operators/user-management/create-users">
    Create user accounts directly. The platform sets up the wallet and identity record automatically.
  </Card>

  <Card title="Register user" href="/docs/operators/user-management/register-user">
    Add a user to the identity registry for compliance tracking and token eligibility.
  </Card>

  <Card title="Manage address book contacts" href="/docs/operators/user-management/manage-address-book-contacts">
    Maintain named wallet records for operator forms. Operators select recipients from this list during transfer and servicing operations rather than entering addresses manually.
  </Card>

  <Card title="Open private files" href="/docs/operators/user-management/open-private-files">
    Learn which users can access private KYC and organisation documents, including administrator files, and the steps to open them.
  </Card>
</Cards>

## Asset creation [#asset-creation]

<Cards>
  <Card title="Create asset" href="/docs/operators/asset-creation/create-asset">
    Deploy a new tokenized asset using the Asset Designer wizard. The wizard guides you through instrument selection, compliance configuration, and initial token parameters.
  </Card>
</Cards>

## Asset servicing [#asset-servicing]

<Cards>
  <Card title="Mint assets" href="/docs/operators/asset-servicing/mint-assets">
    Issue new units of a security to named investor accounts. The platform updates the on-chain supply and records the operation in the audit log.
  </Card>

  <Card title="Burn assets" href="/docs/operators/asset-servicing/burn-assets">
    Reduce the circulating supply. The platform burns units against the configured cap and records each burn in the audit log.
  </Card>

  <Card title="Forced transfer" href="/docs/operators/asset-servicing/forced-transfer">
    Move assets between wallets without holder consent for regulatory compliance or recovery.
  </Card>

  <Card title="Pause and unpause assets" href="/docs/operators/asset-servicing/pause-unpause-asset">
    Pause transfers on a live asset, then lift the pause when the situation is resolved.
  </Card>

  <Card title="Register external tokens" href="/docs/operators/asset-servicing/register-external-token">
    Add an existing EVM token to DALP from the External Tokens workspace. Once registered, the token appears in platform reporting and can use console controls.
  </Card>

  <Card title="Asset detail workspace" href="/docs/operators/asset-servicing/asset-detail-workspace">
    View token facts, pending operations, and event evidence for a live asset.
  </Card>

  <Card title="Change asset admin roles" href="/docs/operators/asset-servicing/change-asset-admin-roles">
    Grant or revoke administrator roles for a specific asset. The platform records each change in the audit log and applies it to on-chain permissions.
  </Card>
</Cards>

## Compliance [#compliance]

<Cards>
  <Card title="Compliance overview" href="/docs/operators/compliance/overview">
    Understand the compliance modules available in DALP and how to configure them during asset creation. Start here before setting up any compliance controls.
  </Card>

  <Card title="Policy templates" href="/docs/operators/compliance/templates">
    Build reusable compliance module templates for assets that share the same policy pattern.
  </Card>

  <Card title="Configure trusted issuers" href="/docs/operators/compliance/configure-trusted-issuers">
    Set the entities authorised to sign compliance verifications. Only claims from listed issuers pass the compliance check.
  </Card>

  <Card title="Verify KYC" href="/docs/operators/compliance/verify-kyc">
    Issue KYC verifications for users. Verification status controls which assets a user can hold and which operations the platform allows.
  </Card>

  <Card title="Collateral requirement" href="/docs/operators/compliance/collateral">
    Set the collateral backing requirements for an asset.
  </Card>
</Cards>

## System addons [#system-addons]

<Cards>
  <Card title="System addons overview" href="/docs/operators/system-addons/introduction">
    Map system add-ons to their purpose, installation path, and production checks. Read this before installing any add-on.
  </Card>

  <Card title="XvP Settlement" href="/docs/operators/system-addons/xvp-settlement/overview">
    Run multi-party asset exchanges using local settlement legs or HTLC flows. The add-on records each leg and its evidence before releasing the final step.
  </Card>

  <Card title="Yield Schedule" href="/docs/operators/system-addons/yield-schedule">
    Configure yield distribution schedules for bonds and other yield-bearing assets. The platform calculates and records each payment against the schedule.
  </Card>

  <Card title="Review addon workspaces" href="/docs/operators/system-addons/review-addon-workspaces">
    Open installed workspaces for XvP settlement, token sale, and other add-on operations.
  </Card>
</Cards>

## AI assistants [#ai-assistants]

<Cards>
  <Card title="AI assistants" href="/docs/operators/ai-agents/overview">
    Connect approved AI assistants to DALP operator workflows. The permission scope does not change: the assistant can only invoke operations the operator is already authorised to run.
  </Card>
</Cards>

## Runbooks [#runbooks]

The [top-level runbook index](/docs/operators/runbooks) is the main index for DALP runbooks. It keeps UI-led procedure walkthroughs close to the user-guide pages you need alongside them.

Console runbooks start with your steps in the DALP console. The [developer runbooks](/docs/developers#runbooks) cover the same workflow shape for API, SDK, or CLI execution. The equity tokenization walkthrough appears in both sections because the UI and API versions serve different readers.

<Cards>
  <Card title="Equity tokenization in the console" href="/docs/operators/runbooks/equity-tokenization">
    UI-led walkthrough for setting up a multi-organization equity tokenization scenario.
  </Card>

  <Card title="User onboarding" href="/docs/operators/runbooks/onboard-user-im">
    Complete workflow to register a user and issue KYC verification.
  </Card>
</Cards>