Overall admin structure
After signing in, Finger Manager uses a standard back-office console structure: a top header, permission-based navigation, a left-side function menu, a multi-tab work area, and a main content panel.
The actual modules, menu items, buttons, and data range shown to each user are determined by the current organization, enabled business modules, role permissions, and route-level access rules.
1. Top header
The top header is the fixed operating entry of the Manager console. It contains the Finger Manager logo, page navigation or breadcrumb area, and common tools on the right side.
Depending on the layout mode, the header may also display the horizontal top menu. If split menu mode is enabled, selecting a top-level module changes the available functions in the side menu.
Logo and navigation Identifies the current Manager system and switches between enabled top-level modules when top navigation is shown.
Breadcrumb Shows the current route path so users can confirm where they are in the system.
Global search Searches available pages or functions when search is enabled.
Notifications Shows system messages, pending reminders, and internal notices.
Language and theme May include locale switching, dark mode, full screen, and other console-level controls.
User account Provides profile-related actions, security options, and sign-out.
2. Left-side function menu
The left-side menu is generated from backend route configuration and permission rules. It is the main entry for daily operations.
Each menu item can define a route path, display title, icon, sort order, menu path, and permission code. If the current user does not have the required permission, the related menu or page is not available.
Some detail pages are intentionally hidden from the menu. For example, customer detail, account detail, fund detail, and report detail pages are opened from list pages, while the parent list entry remains highlighted.
Dashboard Overview data and daily work status.
User management User list, customer audit, customer detail, account detail, Pilot detail, and related hidden detail pages.
Fund management Fund pending review, wallet, customer wallet, deposit and withdrawal application pages.
IB / Broker management Broker or IB list, detail pages, audit detail, and customer ownership relationships.
Order management Mirror or open-position orders and historical closed-order records.
Reports Profit reports, fee reports, deposit and withdrawal reports, and hidden report detail pages.
Customer support Ticket management, session center, help center, announcement publishing, support settings, and technical support entry.
Risk control Risk map and risk-control settings, including user-product matching and related risk views.
Employee and role management Internal staff, roles, menu permissions, and operation permissions.
System settings Organization profile, system configuration, notification configuration, API, or other backend settings depending on enabled modules.
3. Multi-tab work area
Finger Manager can display opened routes as multiple tabs below the header. Operators can switch between list pages, detail pages, audit pages, and report pages without returning to the menu each time.
When a detail route is configured as a hidden menu route, it can still open in the workspace and keep the related parent menu active.
4. Main content panel
The main content panel is where the actual business operation is performed. In the real Manager console, this area is usually composed of page titles, filter forms, statistic cards, data tables, detail panels, forms, and action buttons.
For example, user management pages focus on customer search and customer records; order pages focus on open positions and historical orders; support pages focus on tickets, sessions, help center content, and announcement management.
List pages Used for customers, orders, funds, brokers, reports, tickets, announcements, and similar records.
Detail pages Opened from list records and usually hidden from the side menu, while the original list page remains the active menu entry.
Audit pages Used for customer audit, fund audit, broker audit, and other workflow approval tasks.
Configuration pages Used for risk control, notification settings, system settings, employee roles, and permission configuration.
5. Search, filters, and table operations
Most business pages are organized around filters plus a data table. Operators first narrow down the data set, then open a detail page or execute a permitted row action.
The exact fields differ by module, but common filters include user identifiers, order numbers, market, product, status, date range, broker, account, and business type.
6. Action buttons and workflow controls
Action buttons can appear in the page header, filter area, form footer, table rows, or detail panels. Common actions include search, reset, view, edit, submit, audit, approve, reject, export, publish, save, enable, disable, and refresh.
Whether a button is visible or usable depends on the current route permission and the user's operation permission. Users with view-only permissions may be able to open a page but not modify or export data.
7. Permissions and data scope
Finger Manager uses route permission and menu permission to control what each user can access. A route can define a permission code, and the menu is filtered according to the current user's role.
Permissions affect four levels: visible menus, accessible pages, visible data, and available operations.
This means two employees in the same institution may see different menu structures, data ranges, or action buttons.
8. Mobile and collapsed layout behavior
The real Manager layout supports desktop and mobile layout states. On desktop, the sidebar is usually visible when the menu is enabled. On smaller screens, the sidebar can be collapsed or opened as a mobile menu.
Finger Manager is primarily designed for desktop-width back-office use. Mobile access can help with quick checks, but complex work such as audits, reports, and product configuration is better handled on a desktop screen.
9. Practical navigation flow
A typical operation starts by confirming the current organization and account, selecting a business module from the top or side menu, narrowing the data with filters, opening the relevant detail or configuration page, and then executing the permitted operation.
For example, to review a customer, an operator enters User Management, opens the user list or audit list, searches by UID or email, opens the hidden detail page, checks customer status and records, and then performs the allowed audit or management action.
10. Confirm before operating
Before modifying customer data, fund status, product settings, order handling, support announcements, or system configuration, confirm the current organization, current menu path, selected record, permission level, and expected business impact.
Because some pages are hidden detail routes opened from a list, users should use the breadcrumb, page title, highlighted menu, and record identifiers together to confirm that they are operating on the correct object.
In short, Finger Manager should be understood as a permission-based operations console.
A practical workflow is: confirm organization and account, enter the correct business module, use filters to locate the target record, open the detail or configuration page, and perform only the operation allowed by the current role.
