# Actions work queue
Source: https://docs.settlemint.com/docs/user-guides/runbooks/actions-work-queue
Review upcoming, pending, and completed actions from the DALP Actions page.
The **Actions** page is the operator work queue for tasks that need attention. Open it from the sidebar at **Actions** or go directly to `/actions`.
Use this page to review actions you can execute, actions scheduled for later, and completed or expired history.
The page groups the same action dataset into **Pending**, **Upcoming**, and **Completed** tabs. It refreshes the list while you keep it open.
## What appears in Actions [#what-appears-in-actions]
The Actions queue combines on-chain and account-level tasks that are relevant to your organization and user account.
Current action types include:
| Type | What it covers |
| ---------- | --------------------------------------------------------------------------------- |
| Bond | Bond maturity, redemption, and yield-claim actions |
| Settlement | XvP settlement approval and execution actions |
| KYC | Account-level KYC update requests |
| Action | Other action records that can be shown but are not yet executable from the portal |
Each row shows the action name, target address when there is one, executor count when available, status, schedule time, and expiry time when applicable.
## Access and execution permissions [#access-and-execution-permissions]
Users must be signed in to the onboarded DALP portal and have access to the
organization system to view the Actions queue. The API scopes listed actions to
that active system.
Execution also depends on the action itself:
* The action must be **Pending**.
* The action type must be supported by the portal.
* On-chain actions need a valid target address.
* Rows show executor count when the action source provides executor addresses.
Execution can still be rejected by wallet verification, on-chain checks, or
action-specific validation.
* Account-level KYC update requests are off-chain actions and open the KYC
update form instead of an on-chain executor flow.
If an action cannot be executed from the portal, the row shows **Unavailable**.
## Status tabs [#status-tabs]
| Tab | Statuses shown | How to use it |
| ------------- | --------------------- | ------------------------------------------------------------------------------------------------ |
| **Pending** | Pending | Work that is active now. Supported pending actions show an **Execute** button. |
| **Upcoming** | Upcoming | Work that is scheduled for a future activation time. |
| **Completed** | Completed and expired | Operational history. Completed rows include completion time and executor address when available. |
Expired actions are shown with completed history because they no longer require action. They remain useful for audit and operational follow-up.
## Execute a pending action [#execute-a-pending-action]
### Open the Actions page [#open-the-actions-page]
Go to **Actions** in the sidebar.
The page opens with the **Pending** tab selected.
### Review the row [#review-the-row]
Check the action name, type, target address, executor count when shown, schedule time, and expiry time before acting.
For KYC update requests, the row is shown as an account action because it does not target an on-chain contract address.
### Execute the action [#execute-the-action]
Click **Execute** on a supported pending action.
The portal opens the action-specific flow:
* Bond maturity confirmation for maturity actions
* Redemption for redeem actions
* Yield claim for claim-yield actions
* KYC update form for KYC requests
* XvP approval or execution flow for settlement actions
If the action type cannot be executed from the portal yet, the row shows **Unavailable** instead of an executable action.
### Recheck the queue [#recheck-the-queue]
After execution, return to the Actions page. The queue refreshes automatically, and the action moves out of **Pending** when the underlying operation is complete.
## Search, filter, and export [#search-filter-and-export]
The table includes search, filters, column controls, pagination, and CSV export. Use these controls to narrow the queue by action name, type, date fields, target, or executor fields available in the table.
## Token-specific actions [#token-specific-actions]
Some token detail pages also show the Actions component scoped to that token.
Token-scoped views show actions whose target matches the token address for that page.
Account-level KYC actions only appear in the main Actions queue. KYC actions do not have an on-chain target address.
## Related guides [#related-guides]
Review and approve settlement flows.
Execute settlement flows when the settlement is ready.
Complete or update requested KYC information.