Documentation

Workflow Structure

Understand how Finger Manager organizes business tasks into standard workflows with sources, roles, statuses, operation records, notifications, and follow-up outcomes.

すべてのドキュメント

01

What is a workflow

In Finger Manager, a workflow is a standard internal process around a specific business matter. Its purpose is to make every item traceable from source to handler, status, record, and outcome.

  • Customer onboarding
  • KYC review
  • Deposit review
  • Withdrawal review
  • Account permission changes
  • Risk event handling
  • Report export
02

Task source

Tasks can originate from customer applications, system alerts, external system sync, administrator creation, risk rules, or internal team submissions.

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

Processing roles

Every workflow should have clear processing roles. Different roles can see different data and process different task types.

  • Operations staff
  • Customer service staff
  • KYC reviewers
  • Payment reviewers
  • Trading operations staff
  • Risk staff
  • Compliance staff
  • Administrators
  • Management
04

Processing statuses

Workflows need clear statuses so teams know which stage each item is in. Status changes should be recorded and reviewable later.

  • Pending
  • In progress
  • Awaiting additional information
  • Pending review
  • Approved
  • Rejected
  • Completed
  • Closed
  • Escalated
  • Exception handling
05

Operation records

Every key operation should keep a record for internal review, customer dispute handling, audit tracing, and management analysis.

  • Operator
  • Operation time
  • Operation content
  • Handling result
  • Notes
  • Attachments or proof materials
  • Status changes
  • Review comments
06

Notifications

Finger Manager can notify relevant team members through the mobile app or system notifications so teams can reduce missed or delayed handling.

  • New task alert
  • Approval reminder
  • Supplement reminder
  • Risk alert
  • Timeout reminder
  • Task completion alert
  • Status change alert
07

Common workflow examples

Common workflows include customer onboarding, KYC follow-up, deposit review, withdrawal review, risk event handling, and report export.

  • Customer onboarding: application, completeness check, KYC review, supplement request, status update, processing record
  • KYC follow-up: queue, document review, approve/reject/supplement, resubmission, status sync, audit log
  • Deposit review: application, review task, payment and client check, status decision, result record
  • Withdrawal review: application, account and risk check, escalation if needed, result record
  • Risk event handling: event creation, risk review, escalation, handling result, closure or follow-up
  • Report export: export request, queue, permission and scope processing, completion notification, download record
08

Workflow design principles

Workflow design should stay clear, permission-aware, traceable, reviewable, and usable on mobile when needed.

  • Simple and clear
  • Clear permissions
  • Traceable status
  • Reviewable records
  • Mobile collaboration
09

Launch suggestions

Before launching workflows in Finger Manager, enterprises can start with simple processes, test with a small group, and then expand to more teams and automation capabilities.

  • Map current business processes
  • Confirm owners for each process
  • Define task statuses
  • Set role permissions
  • Confirm notification rules
  • Prepare common notes and review reasons
  • Run a small-scope test
  • Gradually expand to more teams
10

Related documentation

Workflow planning should be read together with product concepts and the role model so task flow, responsibility, and permission boundaries stay aligned.

  • Product Concepts
  • Role Model
  • Implementation Planning
  • Operating Reference
  • API Reference
  • Security Notes