# Operator documentation Source: https://docs.settlemint.com/docs/operators Choose the right DALP operator guide for platform setup, user management, compliance evidence, asset creation and servicing, data feeds, system add-ons, AI assistants, and runbooks. The operator guides are for signed-in console users running regulated digital asset workflows on DALP. Platform administrators use them to prepare roles. Identity teams use them to onboard participants and issue verifications. Asset operators use them to create and service tokens. Operations teams use them to run system add-ons and repeatable scenarios. Choose the guide family that matches your workspace. Platform setup and user management cover tenant configuration, role assignments, and participant records. Compliance covers evidence and policy. Asset creation and servicing span token operations and valuation inputs. System add-ons address settlement and yield; runbooks walk through end-to-end scenarios. DALP owns the console flows, role permissions, workflow execution, audit-log emission, indexed reads, and supported operating evidence. Your organisation owns the policy decisions, role assignments, KYC review, issuer mandates, settlement approvals, and runbook ownership you apply through those flows. These guides cover supported console workflows for signed-in operators. They do not define legal policy, regulator-specific procedures, SLA commitments, or workflows that only exist through APIs, the CLI, webhooks, or background jobs. Integration and automation work lives in the [Developer guides](/docs/developers). ## What DALP covers [#what-dalp-covers] The console gives administrators tools to set up the platform, manage participants, configure compliance controls, issue tokenized assets, publish data feeds, install add-ons, and follow documented runbooks. DALP provides the workspaces, role permissions, workflow behaviour, and recorded audit trail. Organisation policy decides which operators hold which roles and which governed operations run. | Area | DALP defines | Your organisation defines | | ---------- | ------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | Access | Console screens, role permissions, authentication flows, and audit-log emission | Which users receive operator roles and how privileges are reviewed | | Operations | Supported platform, user, compliance, asset, feed, and add-on workflows | Approval chains, custody handling, KYC review, settlement decisions, and policy ownership | | Evidence | Audit logs, workflow status, indexed state, and console reports | Retention policy, regulatory reporting, control testing, and escalation procedures | | Exclusions | Documented console behaviour only | Legal policy, custody policy, SLA commitments, integration automation, and regulator-specific procedures | ## Pick the right path [#pick-the-right-path] | If you need to... | Start here | Then read | | -------------------------------------------- | -------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | Prepare a new tenant or administrator model | [Platform overview](/docs/operators/platform-setup/platform-overview) | [First admin setup](/docs/operators/platform-setup/first-admin-setup) and [Add administrators](/docs/operators/platform-setup/add-admins) | | Onboard participants or recover identity | [User onboarding](/docs/operators/user-management/user-onboarding) | [Invite users](/docs/operators/user-management/invite-users) and [Recover user identity](/docs/operators/user-management/recover-user-identity) | | Configure or review compliance | [Compliance overview](/docs/operators/compliance/overview) | [Policy templates](/docs/operators/compliance/templates) and [Verify KYC](/docs/operators/compliance/verify-kyc) | | Create a tokenized asset from the console | [Create asset](/docs/operators/asset-creation/create-asset) | [Instrument templates](/docs/operators/asset-creation/instrument-templates) | | Service an existing asset | [Asset detail workspace](/docs/operators/asset-servicing/asset-detail-workspace) | [Mint assets](/docs/operators/asset-servicing/mint-assets) and [Pause and unpause](/docs/operators/asset-servicing/pause-unpause-asset) | | Operate data feeds | [Data feeds overview](/docs/operators/data-feeds/overview) | [Publish a feed update](/docs/operators/data-feeds/publish-feed-update) | | Install and run system add-ons | [System add-ons overview](/docs/operators/system-addons/introduction) | [XvP settlement overview](/docs/operators/system-addons/xvp-settlement/overview) and [Yield schedule](/docs/operators/system-addons/yield-schedule) | | Run an AI assistant inside operator controls | [AI assistants overview](/docs/operators/ai-agents/overview) | [CLI AI agent integration](/docs/developers/cli/ai-agents) | | Follow an end-to-end scenario | [Runbooks index](/docs/operators/runbooks) | The equity tokenization, IM onboarding, work queue, and key rotation runbooks | ## Operating model [#operating-model] DALP separates console work into four operator roles: * The platform administrator prepares the tenant, configures system components, manages admin roles, and reviews platform health. * The compliance operator onboards participants: registers identities, issues verifications, and maintains policy controls and evidence. * The asset operator creates tokenized assets, services live assets, and publishes data feeds against issuer-signed pricing. * The operations team installs add-ons, runs settlement and yield workflows, drives the work queue, and follows runbooks for repeatable procedures. Most production deployments combine all four. Read the [introduction](/docs/operators/introduction) for the console operating map, then route to the workspace the workflow needs. For API-driven and webhook automation, switch to the [Developer guides](/docs/developers). ## Platform setup [#platform-setup] Start here for platform setup. This page covers administrator role management, system components, and the sequence administrators follow before asset teams begin work. Initialise the platform with the first administrator account. Grant administrative permissions to operators in your organisation. Create and manage users in the evaluation environment. The evaluation environment uses a separate user set so production access controls stay intact. Grant or revoke platform administrator roles. Inspect smart wallet and paymaster configuration. Verify that account-abstraction settings are correct before users begin transacting. Inspect and manage operator wallets used for governed operations. ## User management [#user-management] Understand how administrator responsibilities divide across roles. Use this page to plan role assignments and clarify who owns each operational area before inviting users. Invite users to the platform with the right role and onboarding path. Create platform users with automatic wallet and identity setup. Walk new users through onboarding. The page covers identity registration, initial access, and the steps users must complete before they can hold or transfer assets. View and manage all participants and holders, including their asset roles, from a single workspace. Maintain a named list of wallet recipients. Operators pick from this list during transfer and servicing operations, reducing manual entry errors. Access private files attached to a participant or asset. Set up authenticators and recovery options for console operators and users. Restore console access for a locked-out user. The platform identity recovery workflow guides each step and records each operation in the audit log. Send KYC data for a participant to the configured compliance providers. Add a user to the identity registry so the platform can track compliance status and token eligibility. ## Compliance [#compliance] Start here for compliance work. The page covers identity, claims, transfer controls, and policy ownership from an operator perspective, including which decisions the platform enforces and which your organisation owns. Build reusable policy templates for asset programmes. Add or remove the entities authorised to sign KYC and compliance verifications. Only claims from listed issuers pass the compliance check. Review and manage KYC data for registered users. Issue KYC verifications to registered users. Verification status determines which assets the user can hold and which operations the platform allows. Gate transfers on a verified-identity claim. Set jurisdiction allow-lists or block-lists for an asset. The platform rejects transfers from blocked jurisdictions at the compliance layer. Hold an asset below the configured cap on unique holders. Set a minimum holding period that received units must satisfy before they can transfer to another wallet. Set the collateral ratios and backing requirements for an asset. The platform checks these thresholds before allowing mint or transfer operations. ## Asset creation [#asset-creation] Deploy a new tokenized asset from the asset designer. The wizard guides you through instrument selection, compliance configuration, and initial token parameters. Browse the 24 seeded system templates, grouped by asset class. Tutorial that walks an operator from a blank custom template to a published template the Asset Designer offers. Select the instrument template that matches the target asset class. ## Asset servicing [#asset-servicing] View facts, pending operations, and event evidence for a live asset, then run operations from one workspace. Add a token deployed outside DALP so it appears in platform reporting and controls. Confirm a named wallet record before approving a governed servicing operation. Grant or revoke administrator roles for a specific asset. Role changes take effect immediately and the platform records each change in the audit log. Operate a collateral-backed stablecoin from issuance through redemption. The page maps each lifecycle state to the console operations and compliance checks the platform requires. Check the portability evidence before an asset exit or migration. Issue new units to named investors. The platform records the mint in the audit log and updates the on-chain supply. Reduce the circulating supply by burning units against the configured cap. Restrict or release part of a holder balance for approved custodian cases. Move assets between wallets without holder consent. Use this for regulatory compliance orders or wallet recovery, and only with the required on-chain role. Convert holdings between configured asset classes under policy controls. Add or remove converter addresses. The platform checks this list before it allows a forced conversion to proceed. Enable or disable transfers for an asset. ## Data feeds [#data-feeds] Start here for data feed operations. The page explains how issuer-signed prices, NAVs, and oracle feeds work, and which operator role manages each feed type. Set up a feed topic to categorise a price, NAV, FX rate, or oracle value before publishing data. Deploy an issuer-signed feed, an aggregator adapter, or an external feed registration. Send a signed feed update using EIP-712 typed data. The platform records each update in the audit log and makes the value available to any asset that references the feed. Swap in a corrected feed or decommission a retired one. Register an exchange-rate feed for a new reporting currency. Once active, the platform converts asset values into that currency for display and reporting. ## System add-ons [#system-add-ons] Map visible system add-ons to their purpose, installation path, and production checks. Read this before installing any add-on. Select and install the system add-ons your asset programme needs. Inspect installed add-on workspaces and their operating evidence. Run multi-party asset exchanges. The add-on supports both local settlement legs and HTLC flows for cross-chain scenarios. Configure yield distribution schedules. The platform calculates each distribution against the schedule and records the payment in the audit log. Confirm platform prerequisites before starting bond lifecycle workflows. ## AI assistants [#ai-assistants] Integrate approved AI assistants into DALP operator workflows. The permission boundary does not change: the assistant can only call operations the operator is already authorised to run. ## Runbooks [#runbooks] This shelf collects console-led end-to-end procedures for operations teams. For API-driven workflows, the [equity tokenization runbook](/docs/developers/runbooks/equity-tokenization) and the bond, deposit, fund, and stablecoin runbooks are in [developer documentation](/docs/developers). Find the operator runbook that matches the scenario you need to run. Step through multi-organisation equity tokenization in the console. The runbook covers asset creation, participant onboarding, and the first mint operation. Step-by-step procedure to register an investor or identity holder and complete the identity management workflow. Work through pending approvals and exceptions in the queue. The runbook covers normal processing and how to escalate items that need manual resolution. Replace the claim signer key for a compliance provider without disrupting active verifications.