Documentation

Workflow Structure

What a workflow is. In Finger Manager, a workflow is a standard internal process built around a type of business item. Client onboarding, KYC review, deposit review, withdrawal review, account permission changes, risk event handling, and report exports can all be designed as workflows.

Documentation

01

Basic Workflow Components

A standard workflow usually includes a task source, processing role, processing status, operation records, and notifications. Its purpose is to make every item clear in source, owner, status, operation history, and final outcome.

  • Tasks may come from client requests, system alerts, external system sync, administrator creation, risk rules, or internal team submissions.
  • Each workflow should have a clear processing role.
  • Workflows need clear statuses so teams understand the current stage of each item.
  • Every key operation should be recorded.
  • Finger Manager can remind relevant users to handle tasks through the mobile app or system notifications.
02

Task Sources

Tasks may come from client onboarding requests, KYC missing-document requests, deposit requests, withdrawal requests, account permission changes, symbol rule adjustments, risk event alerts, report export tasks, customer service tickets, or manually created administrator tasks.

  • Client onboarding request
  • KYC missing-document request
  • Deposit request
  • Withdrawal request
  • Account permission change
  • Symbol rule adjustment
  • Risk event alert
  • Report export task
  • Customer service ticket
  • Administrator-created task
03

Processing Roles and Statuses

Common roles include operations users, customer service users, KYC reviewers, payment reviewers, trading operations users, risk reviewers, compliance users, administrators, and management. Common statuses include pending, in progress, waiting for additional documents, waiting for review, approved, rejected, completed, closed, escalated, and exception handling.

  • Different roles can view different data and handle different task types.
  • Status changes should be recorded and available for later review.
04

Operation Records and Notifications

Operation records usually include operator, operation time, action, result, notes, attachments or supporting materials, status changes, and review comments. Notifications include new task alerts, approval reminders, missing-document reminders, risk alerts, timeout reminders, task completion notices, and status change notices.

  • These records support internal review, client dispute handling, audit tracing, and management analysis.
  • Mobile notifications help teams reduce missed handling and delayed handling.
05

Common Workflow Examples

Finger Manager can support common workflows such as client onboarding, KYC follow-up, deposit review, withdrawal review, risk event handling, and report export.

  • Client onboarding workflow: the client submits onboarding materials, the system creates a task, operations checks completeness, KYC reviewers review, missing documents are requested when needed, and client status is updated after approval.
  • KYC follow-up workflow: client materials enter the KYC queue, reviewers mark approved, rejected, or missing documents, and supplemented materials return to review.
  • Deposit review workflow: the client submits a deposit request, the system creates a payment review task, and operations or finance users verify status and record the result.
  • Withdrawal review workflow: reviewers inspect account status, KYC status, and risk alerts, and may submit the item to risk or management review.
  • Risk event workflow: a risk handling task is created, risk users inspect event details, and the task is handled or escalated by risk level.
  • Report export workflow: the user submits a report export task, the system creates a report queue, and export time, operator, and report type are recorded.
06

Workflow Design Principles

Workflow design should stay simple, clear, permissioned, traceable, reviewable, and usable from mobile.

  • Simple and clear: each workflow should help the team know who handles it, what is handled, and what comes next.
  • Clear permissions: each role should only see and handle data within its responsibility.
  • Traceable status: task status should be visible without relying on chat history or manual questions.
  • Reviewable records: key handling actions should be logged for audit and dispute handling.
  • Mobile collaboration: important tasks and reminders should be viewable and actionable from mobile to improve response speed.
07

Workflow Launch Suggestions

Before launching Finger Manager workflows, organizations can map existing business processes, confirm owners for each process, define task statuses, configure role permissions, confirm notification rules, prepare common notes and review reasons, test with a small scope, and then expand to more teams.

  • Finger Manager supports starting from simple processes and gradually adding more modules and automation capabilities.