SettleMint

Operator documentation

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, and operations teams use them to run system add-ons and repeatable scenarios.

Choose the guide family that matches the workspace you operate from. Start with platform setup for tenants and administrators, user management for participants and identity, compliance for evidence and policy, asset creation and servicing for token operations, data feeds for valuation inputs, system add-ons for settlement and yield, AI assistants for governed automation, and runbooks for end-to-end scenarios.

Rendering diagram...

DALP owns the console flows, role permissions, workflow execution, audit-log emission, indexed reads, and supported operating evidence in this section. Your organisation owns the policy decisions, role assignment, KYC review, issuer mandates, settlement approvals, and runbook ownership that you apply through those console 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.

What DALP covers

The console lets administrators set up the platform, manage participants, configure compliance, create and service assets, publish data feeds, install and run system add-ons, and follow documented runbooks. DALP defines the workspaces, role permissions, workflow behaviour, and recorded evidence. Organisation policy decides which operators receive which roles and when each governed action is allowed.

AreaDALP definesYour organisation defines
AccessConsole screens, role permissions, authentication flows, and audit-log emissionWhich users receive operator roles and how privileges are reviewed
OperationsSupported platform, user, compliance, asset, feed, and add-on workflowsApproval chains, custody handling, KYC review, settlement decisions, and policy ownership
EvidenceAudit logs, workflow status, indexed state, and console reportsRetention policy, regulatory reporting, control testing, and escalation procedures
ExclusionsDocumented console behaviour onlyLegal policy, custody policy, SLA commitments, integration automation, and regulator-specific procedures

Pick the right path

If you need to...Start hereThen read
Prepare a new tenant or administrator modelPlatform overviewFirst admin setup and Add administrators
Onboard participants or recover identityUser onboardingInvite users and Recover user identity
Configure or review complianceCompliance overviewPolicy templates and Verify KYC
Create a tokenized asset from the consoleCreate assetInstrument templates
Service an existing assetAsset detail workspaceMint assets and Pause and unpause
Operate data feedsData feeds overviewPublish a feed update
Install and run system add-onsSystem add-ons overviewXvP settlement overview and Yield schedule
Run an AI assistant inside operator controlsAI assistants overviewCLI AI agent integration
Follow an end-to-end scenarioRunbooks indexThe equity tokenization, IM onboarding, actions queue, and key rotation runbooks

Operating model

DALP separates console operations into four operator roles:

  • The platform administrator prepares the tenant, configures system components, manages administrator roles, and reviews platform health.
  • The identity and 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 actions queue, and follows runbooks for repeatable scenarios.

Most production deployments combine all four. Read the introduction for the console operating map, then route to the workspace the workflow needs. For API, CLI, webhook, and background-job automation, switch to the Developer guides.

Platform setup

User management

Compliance

Asset creation

Asset servicing

Data feeds

System add-ons

AI assistants

Runbooks

The runbook shelf collects console-led end-to-end scenarios for operations teams. Use the API-led equity tokenization runbook and the bond, deposit, equity, fund, and stablecoin runbooks under developer documentation when the same scenario starts from an API, script, or integration test.

On this page