01Basic Concepts
An enterprise account is the organizational entity in Finger Manager. It can contain multiple members, teams, roles, modules, and business data. A member is an authorized user under the enterprise account. A role is a set of permissions. Permissions determine what a member can view, handle, modify, and export. Teams are used to organize member relationships.
- Enterprise account
- Member
- Role
- Permission
- Team
02Common Roles
Common Finger Manager roles include super administrator, administrator, operations user, customer service user, KYC reviewer, payment reviewer, trading operations user, risk user, compliance user, and management user.
- Super administrator: manages enterprise accounts, members, role permissions, modules, system configuration, data scope, operation records, and workflow rules.
- Administrator: manages member accounts, assigns teams and roles, configures some modules, views team data, and manages task queues and basic reports.
- Operations user: views client records, follows client status, handles operations tasks, views tickets and notes, and handles basic review queues and related reports.
- Customer service user: views basic client information, creates or handles client tickets, follows KYC missing-document items, adds client notes, and receives task alerts.
- KYC reviewer: views KYC materials, handles review tasks, marks approved, rejected, or missing documents, adds review notes, and views history.
- Payment reviewer: views payment review queues, handles deposit and withdrawal requests, marks payment status, submits exception tasks, and exports related reports.
- Trading operations user: views account trading status, handles symbol permission requests, follows trading operations tasks, and records account status changes.
- Risk user: views risk events, handles abnormal alerts, reviews client risk status, and submits restriction review or escalation requests.
- Compliance user: views audit records, permission change records, risk handling history, exception events, and operation logs.
- Management user: views business overview, team performance, risk overview, report data, and key indicators.
03Permission Types
Finger Manager permissions can be divided into view permissions, operation permissions, management permissions, and export permissions. Export permissions should be configured carefully and only assigned to people with a clear business need.
- View permissions: view client records, KYC information, payment records, risk events, reports, and operation logs.
- Operation permissions: approve, reject, request missing documents, submit review, modify client status, create tasks, and close tasks.
- Management permissions: add members, delete members, modify roles, configure modules, set workflows, and manage enterprise information.
- Export permissions: determine whether a member can export data or reports.
04Data Scope
Finger Manager can configure different data scopes according to enterprise needs, helping organizations keep information secure and responsibilities clear when many people collaborate.
- Only personal tasks
- Team data
- Designated department data
- Designated region data
- Designated client group data
- Full enterprise data
05Role Configuration Suggestions and Best Practices
Small teams can start with administrator, operations user, reviewer, and management roles. Medium teams can separate customer service, KYC review, payment review, risk, and management roles. Large teams can create more detailed roles by headquarters, region, IB management, customer service, KYC, payment operations, trading operations, risk, compliance, and management.
- Minimum permission principle: members should only have the permissions required to complete their work.
- Review permissions regularly, especially after staff changes, role changes, or team restructuring.
- Assign administrator permissions carefully and only to trusted core users.
- Keep records for key operations such as approval, rejection, permission changes, exports, and risk handling.
- Handle resignation and role changes promptly by disabling accounts or adjusting permissions.
06Role Model Launch Steps
Organizations can launch the role model by mapping the organization structure, confirming teams that will use Finger Manager, defining each team's responsibilities, setting base roles, configuring view and operation permissions, configuring data scope, inviting members, testing permissions, launching formally, and reviewing permission settings regularly.
- The role model is not a one-time setup. Organizations can keep adjusting it according to business growth and internal management requirements.
