# Lifecycle after issuance Source: https://docs.settlemint.com/docs/architecture/start-here/lifecycle-after-issuance How DALP operators manage an issued asset after deployment, from the asset detail workspace through supply, transfer, pause, role, compliance, feature, and audit operations. **Purpose:** Explain the day-two operating model for an issued DALP asset. * **Doc type:** Explanation * **What you'll find here:** * Which surfaces operators use after an asset is deployed * How common servicing actions relate to token roles, compliance, and features * Where to read the detailed user and API guides for each operation * **Related:** * [Asset model](/docs/architecture/start-here/asset-model) * [Asset issuance](/docs/architecture/flows/asset-issuance) * [Asset detail workspace](/docs/user-guides/asset-servicing/asset-detail-workspace) * [Token lifecycle API](/docs/developer-guides/api-integration/token-lifecycle) *** ## The short version [#the-short-version] After issuance, a DALP asset is operated from the asset detail workspace, the Unified API, and the token's configured feature pages. Operators use these surfaces to monitor holders and transfers, manage supply, pause or unpause activity, run permitted servicing actions, update token-level roles, and reconcile events. The exact actions available for an asset depend on its token roles, compliance modules, enabled token features, wallet verification state, and current asset state. ## Operating surfaces [#operating-surfaces] | Surface | Use it for | Notes | | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | Asset detail workspace | Review the issued asset, holder table, actions, compliance configuration, documents, feature tiles, and the Manage Asset menu. | The workspace only shows actions and tabs that apply to the current asset and system configuration. | | Manage Asset menu | Start common operator workflows such as minting, pause or unpause, forced transfer, verification actions, collateral updates, transfer approvals, and token-sale creation when available. | Menu entries are permission-gated and can be hidden or disabled when the asset state, role, feature, or system check does not pass. | | Token lifecycle API | Automate creation, minting, transfer, burn, feature, and reconciliation workflows. | State-changing calls return synchronous transaction metadata or async status links, depending on the operation. | | Token feature pages | Operate feature-specific workflows such as maturity redemption, fixed treasury yield, conversion, AUM fees, transaction fees, and historical balance reads. | Read the token's attached features before submitting a feature mutation. | ## Common post-issuance operations [#common-post-issuance-operations] | Operation area | What changes | Primary control | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------- | | Supply servicing | Minting increases supply; burning decreases supply and can target one or more holder balances. | Supply-management token role, wallet verification, holder balance checks, and asset state checks. | | Transfer control | Normal holder transfers must pass identity and compliance checks; forced-transfer workflows are custodian operations for exceptional servicing cases. | Token-holder balance and compliance checks for normal transfers; custodian permission for forced transfers. | | Pause state | Pausing blocks selected token operations until an authorized operator unpauses the asset. | Emergency token role and current paused state. | | Token roles | Role grants and revocations change which operators can administer, govern, manage supply, or run emergency workflows for the token. | Token admin role. | | Compliance configuration | Operators can review and, where permitted, configure token-level compliance modules and parameters. | Compliance-manager or governance-controlled routes, depending on the operation. | | Feature operations | Configured features add day-two actions such as maturity, redemption, yield claims, treasury top-ups, fee configuration, conversion, and historical balance reads. | The feature must be attached; each operation uses the role or signer condition for that feature. | | Reconciliation | Operators review action status, token events, holder balances, transfers, documents, and feature status after transactions confirm. | Actions, events, holder, transfer, document, and feature reads. | ## Feature-gated lifecycle actions [#feature-gated-lifecycle-actions] Not every issued asset has the same day-two operations. Feature actions should be treated as available only when the token reports the matching feature attached. Examples of feature-gated operations include: * maturity-redemption operations for maturing, early maturity, treasury top-ups, treasury updates, wallet-treasury allowance, and holder redemption; * fixed-treasury-yield operations for treasury setup, top-ups, and holder yield claims; * conversion operations for triggers, conversion windows, holder conversion, forced conversion, and authorized converters; * fee operations for rate, recipient, exemption, freeze, collection, or reconciliation workflows, depending on the configured fee feature; * historical balance reads for holder snapshots and reporting. Treasury-backed feature operations depend on denomination-asset funding. A top-up funds the configured feature treasury or legacy redemption pool. Top-ups do not mint new payout assets. ## Read before you mutate [#read-before-you-mutate] Before running a lifecycle mutation, confirm: 1. The token exists and the current user can see it in the asset detail workspace or token read endpoint. 2. The caller has the token role or signer condition required for the operation. 3. The asset is in the right state, such as unpaused for minting, sufficient holder balance before burning, or matured for redemption. 4. The required compliance module, token feature, treasury, trigger, or collateral configuration is present. 5. Wallet verification is current when the workflow signs a transaction. 6. The resulting transaction status, action record, event, holder balance, or feature status has been reconciled before retrying. ## Where to go next [#where-to-go-next] | If you need to... | Read next | | ------------------------------------ | -------------------------------------------------------------------------------------- | | Review an issued asset in the UI | [Asset detail workspace](/docs/user-guides/asset-servicing/asset-detail-workspace) | | Mint new supply | [Mint assets](/docs/user-guides/asset-servicing/mint-assets) | | Burn outstanding supply | [Burn assets](/docs/user-guides/asset-servicing/burn-assets) | | Pause or unpause an asset | [Pause or unpause an asset](/docs/user-guides/asset-servicing/pause-unpause-asset) | | Change token-level administrators | [Change asset admin roles](/docs/user-guides/asset-servicing/change-asset-admin-roles) | | Review all API operation flows | [Token lifecycle API](/docs/developer-guides/api-integration/token-lifecycle) | | Understand configured token behavior | [Token features](/docs/architecture/components/token-features) | | Understand transfer eligibility | [Compliance transfer](/docs/architecture/flows/compliance-transfer) |