Maker-Checker Tasks

Eclipse supports a maker-checker (dual-control) approval workflow. Certain operations — such as wallet transfers, withdrawals, and configuration changes — can be configured to require a second user's approval before they are executed. The Tasks page is where approvers review and act on pending items.

---

How Maker-Checker Works

1. A maker (initiating user) performs an action (e.g., initiates a wallet transfer).
2. Instead of executing immediately, the platform creates a task in PENDING state and notifies users with the relevant approver role.
3. A checker (approving user) reviews the task and either approves (EXECUTE) or rejects (REJECTED) it.
4. If multiple approvals are required, each approver reviews independently; execution proceeds only when all required approvals are recorded.
5. The maker cannot approve their own task.

Maker-checker is configured per role and per operation type. Contact your EFT Corporation account manager or refer to the Permissions Management section to enable it for specific roles.

---

Accessing the Tasks Page

Navigate to Dashboard → Tasks in the top-level navigation.

The tasks list shows all tasks relevant to the logged-in user — both tasks the user initiated (visible in the "My Tasks" section) and tasks awaiting the user's approval (matched by the user's roles).

Task Table Columns

---

Task States

---

Filtering Tasks

Use the status filter chips at the top of the task list to show tasks by state. By default, only PENDING tasks are shown. Select additional states to view historical tasks.

---

Approving a Task

1. Locate the task in the list and click View to inspect the full details of the pending operation.
2. If the operation is correct, click Execute.
3. A confirmation dialog appears: "Are you sure you want to execute the task?" Click Yes execute task.
4. The task transitions to EXECUTED on success, or FAILED if the underlying operation encounters an error.

If the task fails, the error response code and body are displayed in a dialog. The original operation was not applied — no funds moved, no records changed. Investigate the error and ask the maker to re-submit if appropriate.

---

Rejecting a Task

1. Click View to inspect the task.
2. Click Reject.
3. A confirmation dialog warns that the action cannot be reversed. Click Yes reject task.
4. A reason dialog opens — enter a brief explanation for the rejection.
5. The task moves to REJECTED state and the initiating maker is notified.

---

Discarding Your Own Task (Maker)

If you initiated a task and wish to cancel it before it is approved:

1. Find your task in the list (filter by your user ID or look under "My Tasks").
2. Click Discard.
3. Confirm: "Are you sure you want to discard the changes?" Click Yes discard changes.
4. The task moves to DISCARDED and is removed from approvers' queues.

---

Re-submitting a Discarded or Failed Task

Discarded and failed tasks cannot be re-activated. The maker must re-initiate the original operation from scratch (e.g., navigate back to the wallet transfer screen and submit again).

---

Multiple-Approver Scenarios

When a task requires more than one approver:

• Each checker sees the task in their queue independently.
• Each checker can approve or reject independently.
• If any checker rejects, the task moves to REJECTED immediately.
• The task only reaches EXECUTED after all required approvers have approved.
• A checker who has already approved will see the task as read-only until remaining approvals arrive or the task is rejected.

---

Permissions

To approve tasks, a user's role must be configured with the Tasks.Approve permission. To initiate operations that create tasks, the role needs the relevant operation permission (e.g., WalletTransfer.CREATE). Both permissions must be configured separately.

Refer to the Permissions Management section of the Operator Guide for configuration details.