Organization administrators, system administrators, operations leads, compliance teams, and authorized back-office managers
Manage institutional entities, organization hierarchy, and organization-level business boundaries in Finger Manager.
Manage institutional entities, organization hierarchy, and organization-level business boundaries in Finger Manager.
Notifications configured in Finger Manager can be delivered precisely inside Finger Trader App according to rules, audience, and schedule.
Organizations are used to manage institution entities, organization hierarchy, and organization-level base information in Finger Manager.
For brokers, financial institutions, group companies, or customers with multiple business entities, organizations can represent the required institutional layers and bind back-office users, teams, roles, permissions, and business data to those layers.
Organization is a foundation for Finger Manager permission control and data isolation. Back-office users, teams, roles, customers, products, notifications, and part of the business data can be managed according to organization relationships.
An Organization represents an independent institution entity or business entity inside Finger Manager.
It can represent a broker head office, group company, subsidiary, regional company, brand entity, business department, licensed entity, or country / regional operating entity.
A simple institution can use one organization. A group with multiple regions, brands, or legal entities can create multiple organizations and manage them through a hierarchy.
An administrator with the required permission can create a new organization in Finger Manager.
Common fields include organization name, Organization ID, short name, region, country / area, time zone, default language, contact information, organization status, parent organization, and description.
After creation, the system establishes an independent organization identifier for the entity.
Each organization can have a unique Organization ID. The ID is used internally to distinguish institution entities and associate back-office users, customers, roles, teams, APIs, notifications, product configuration, system logs, and other business data.
Even when two organizations have similar display names, the system can identify them accurately through Organization ID.
Finger Manager can create organization hierarchies based on the institution's real structure.
For example, a Global Broker Group can contain Japan Entity, Hong Kong Entity, and Singapore Entity. A Head Office can contain Retail Brokerage, Institutional Business, and Wealth Management.
This makes legal entity, regional, and business-line relationships clearer in the back office.
Organizations can have a parent organization and form parent-child relationships.
For example, a group headquarters can be the parent organization, with Japan, Hong Kong, and Singapore subsidiaries underneath it.
Group administrators can be authorized to view data across several child organizations, while subsidiary users can be limited to their own organization.
Each Finger Manager back-office user can belong to a specified organization.
The system can use the user's organization to determine the default data access range. For example, a normal employee under Japan Entity can be limited to customer and business data belonging to Japan Entity.
Roles can be managed within an organization scope. Different organizations can use the same role names while keeping different permission configurations.
This allows each institution entity to configure access control according to its own internal management rules.
Teams can be created inside an organization. For example, Japan Entity can contain Operations Team, Compliance Team, Customer Service Team, and Trading Team.
This forms an Organization -> Team -> User management structure. Organization handles institutional boundaries, while Team handles internal collaboration and personnel grouping.
Organization can serve as an important data isolation boundary in Finger Manager.
Users in Organization A can be limited to Organization A's customers, orders, products, notifications, and back-office users. Normal users in Organization B cannot access Organization A data.
Only administrators with cross-organization permission can access data across multiple organizations.
Customer data can belong to a specified organization. A customer opened under Japan Entity can be assigned to Japan Entity, while a customer opened under Hong Kong Entity can be assigned to Hong Kong Entity.
This allows customer data to be managed according to the responsible institution entity.
Different organizations can have different product and market configurations.
For example, Japan Entity can provide Japanese stocks, US stocks, and ETFs. Hong Kong Entity can provide Hong Kong stocks, US stocks, and other products.
Through organization configuration, the same Finger Manager system can support multiple business entities while preserving their separate product structures.
Notifications can also be managed by organization. For example, Japan Entity can publish Japanese holiday trading arrangements only to users belonging to Japan Entity, while Hong Kong Entity publishes its own Hong Kong market notices.
Different organizations can independently manage announcements, Push Notifications, In-App Notifications, Email, SMS, Banner, and Marquee content.
Each organization can have organization administrators. Based on permissions, they can manage back-office users, teams, roles, permissions, customers, products, notifications, and system settings within their own organization.
Without cross-organization permissions, an organization administrator cannot manage another organization.
Group-level customers can create administrators with cross-organization permission.
For example, a Group Administrator can be authorized to view Japan Entity, Hong Kong Entity, and Singapore Entity and switch between them.
This is suitable for headquarters, regional management centers, group compliance teams, group technology teams, and management teams.
Organizations can have statuses such as Active, Disabled, Pending, or Archived.
When an organization is disabled, its back-office user login or related business functions can be restricted while historical records remain available according to the institution's retention rules.
Each organization can maintain its own default settings, such as default language, time zone, currency, brand name, logo, contact information, notification sender, SMS Sender ID, Email Sender, App configuration, and other institution-level parameters.
These settings can be used as defaults for business modules under that organization.
Institutions with multiple legal entities or financial licenses can create separate organizations for each entity.
For example, ABC Group can contain ABC Securities Japan, ABC Securities Hong Kong, and ABC Capital Singapore. Each entity can separately manage customers, employees, products, markets, notifications, permissions, and data while group headquarters retains authorized oversight.
Important organization-related operations can be recorded in Finger Manager logs.
Examples include creating an organization, editing organization information, adding administrators, changing organization status, adjusting hierarchy, modifying organization permissions, and deleting or disabling an organization.
Logs help confirm who performed which action on which organization and when.
The workflow can be understood as: create Organization -> set base information -> set parent organization -> create organization administrator -> create roles and permissions -> create teams -> add back-office users -> associate customers, products, and business data -> isolate data by organization scope -> operate independently under each organization.
Organization is a foundational management unit in the Finger Manager organization and permission system.
Institutions can use Organization to build legal entity, region, brand, or business structures, and then manage back-office users, teams, roles, permissions, and business data within those structures.
Through hierarchy and data isolation, one Finger Manager deployment can support both a single institution and complex multi-entity, multi-region group architectures while maintaining clear permission and data boundaries.
