Security administrators, organization administrators, compliance teams, audit teams, and IT administrators
Record Finger Manager back-office sign-in attempts, authentication results, IP addresses, devices, sessions, and abnormal access.
Record Finger Manager back-office sign-in attempts, authentication results, IP addresses, devices, sessions, and abnormal access.
يمكن تسليم الإشعارات التي يتم إعدادها في Finger Manager داخل Finger Trader App وفق القواعد والجمهور والجدولة.
Login Logs record information related to back-office users signing in to Finger Manager, including login time, login result, login method, source IP, device information, and abnormal login events.
They help institutions understand back-office account access and quickly investigate abnormal sign-ins, account locks, authentication failures, and other security issues.
Login Logs are an important part of the Finger Manager security audit system.
Login Logs are back-office access records automatically generated by Finger Manager.
Whenever a back-office user attempts to sign in, the system can record the event whether it succeeds or fails.
Examples include successful login, failed login, SSO login, MFA verification, account lock, account unlock, session invalidation, abnormal login attempts, and other authentication-related events.
These records show when, from where, and by which method a back-office account accessed the system.
Each login log can include login time, back-office user, User ID, Organization, login method, login result, IP address, country / region, device type, operating system, browser, Session ID, authentication method, MFA status, failure reason, and risk status.
Different login methods can record different fields.
When a back-office user successfully signs in to Finger Manager, the system creates a success record.
For example: User = Aki Tanaka, Login Time = 2026-08-28 15:32:18 JST, Login Method = SSO, IP Address = 203.0.113.10, Result = Success.
Successful login records confirm the actual access time and source of an account.
When a user fails to sign in, the system can also record the attempt.
Failure reasons can include authentication failure, wrong password, SSO verification failure, MFA verification failure, disabled account, locked account, invalid session, insufficient permission, or authentication timeout.
For example, Result = Failed and Reason = Authentication Failed. These records are important for account troubleshooting and abnormal access detection.
Finger Manager can use SSO for identity authentication.
After a user authenticates with a Finger Grid Account, access to the corresponding Finger Manager environment is determined by Organization, role, and permissions.
SSO login logs can record Finger Grid Account, SSO login time, Organization, login result, Session, IP address, and device information.
The unified identity system allows authentication across Finger Grid products to be managed consistently.
If an institution enables multi-factor authentication, login logs can also record MFA verification status.
Examples include MFA Required, MFA Success, MFA Failed, and MFA Timeout.
A typical flow is: user completes SSO authentication -> system requires MFA -> user completes second-factor verification -> Finger Manager creates a login Session. The whole authentication process can generate related security records.
Login logs can save the source IP address used to access Finger Manager, such as 203.0.113.10.
IP information can be used for login troubleshooting, security analysis, region inference, risk control, and internal audit.
If the same back-office account signs in from several obviously different IP addresses within a short time, administrators can inspect those records further.
Based on IP information, the system can record an approximate country or region, such as Japan, Hong Kong, Singapore, or United States.
This information is mainly used for security analysis and access record display.
IP-based location is a network-level inference and does not necessarily represent the user's precise physical location.
The system can record the device environment used during login.
For example: Device = Desktop, Operating System = macOS, Browser = Chrome; or Device = Mobile, Operating System = iOS.
Device information helps administrators decide whether the login matches the user's normal usage pattern.
Finger Manager can distinguish different authentication methods, such as SSO, Password, MFA, Enterprise Identity Provider, API Authentication, or other institution-configured authentication methods.
For institutions currently using SSO, back-office login is mainly authenticated through the unified Finger Grid Account.
After a user signs in successfully, the system can create a corresponding Session.
Login logs can be associated with Session ID, Session Start, Session Expiry, Logout Time, and Session Revoked.
When the user signs out or the Session expires, the system can record the corresponding status.
In addition to login events, the system can record Logout.
For example, Login at 15:30 and Logout at 18:15.
If the user does not actively sign out and the Session ends by timeout, the system can record Session Expired according to its rules. This gives a more complete view of account access.
When a user fails authentication repeatedly, the system can temporarily lock the account according to security policies.
A common flow is: multiple failed login attempts -> security rule is triggered -> account enters Locked status -> later login requests are rejected.
Login logs can save lock time, trigger reason, source IP, and failure count so administrators can decide whether the event was user error or abnormal access.
If an administrator unlocks an account, the system can generate a corresponding record.
For example: Action = Account Unlock, Operator = Security Admin, User = Aki Tanaka, Result = Success.
Account unlock is a security-related operation and can also be recorded in Operation Logs.
Login records help institutions identify abnormal access patterns.
Examples include a large number of failed logins in a short time, logins from uncommon countries or regions, new device logins, fast switching between multiple IPs, access outside normal working hours, disabled accounts attempting to sign in, and repeated MFA failures.
When these patterns appear, administrators can inspect account status or security logs further.
When login log volume is large, search can quickly locate records.
Common search fields include user name, User ID, Email, IP address, Session ID, and Organization.
Searching a specific back-office user can show that user's historical login records.
Login records can be filtered by time range, Organization, user, login method, login result, IP address, country / region, device type, and risk status.
For example, Time = past 24 hours and Result = Failed shows all failed login records from the most recent day.
Administrators can open a back-office user and view historical login records.
For example, Aki Tanaka in the past 30 days: Successful Login = 42, Failed Login = 2, Last Login = 2026-08-28 15:32 JST.
This helps quickly understand the account's usage status.
If an abnormal IP is found, administrators can search all access records for that IP.
For example, searching 203.0.113.10 can show which accounts used the IP, login times, success / failure status, and device information.
This is useful for analyzing bulk abnormal logins or shared network environments.
Back-office user details can show Last Login, which quickly confirms the most recent successful Finger Manager access time.
For example: Last Login = 2026-08-28 15:32 JST.
If an account has not signed in for a long time, administrators can decide whether the account still needs to be retained.
Newly created but unused back-office accounts can display Never Logged In or No Login Record.
Administrators can use this to confirm whether the invitation was accepted, whether the user completed account registration, and whether the user has started using Finger Manager.
Login logs are also controlled by permissions.
Normal back-office users may only view their own login records. Organization Admin can view login records for users under the current Organization. Security Admin or Super Admin can view login records across multiple organizations if authorized.
This prevents normal employees from viewing other users' security access history.
Login Logs mainly record who entered the system, including login time, IP, device, authentication method, and login result.
Operation Logs mainly record what the user did after entering the system, such as create, edit, publish, delete, permission changes, and other back-office operations.
Used together, they provide complete back-office behavior tracing. For example, at 15:30 Login Logs show Aki Tanaka signed in successfully. At 15:35 Operation Logs show Aki Tanaka changed AAPL trading hours.
When an institution finds an abnormal back-office operation, it can first use Operation Logs to identify the operator, then inspect that user's Login Logs at the same time.
For example: a critical permission was changed at 15:35 -> check Operation Log to confirm the account -> check Login Log to confirm login time, IP, country, device, and login method -> decide whether the operation was normal.
This correlation significantly improves security investigation efficiency.
Login logs can be retained according to institutional security or internal management requirements, such as 90 days, 180 days, 1 year, or multiple years.
Administrator account logs, security incidents, and abnormal access records can use longer retention periods.
Administrators with the required permission can export login logs for internal security audit, abnormal login investigation, compliance checks, IT security analysis, and management reports.
Because login logs contain IP, device, and account access information, export permission should be managed independently.
Login logs are mainly used for system security, access control, and internal audit.
When using, storing, or exporting login logs, institutions should follow their internal security policies and applicable data protection rules.
Full login-log access should not be granted to unnecessary personnel.
The workflow can be understood as: back-office user accesses Finger Manager -> Finger Grid / SSO authenticates identity -> MFA is performed if required -> system records the login request -> authentication succeeds or fails -> Login Log is generated -> user, time, IP, device, and authentication result are recorded -> Session is created after success -> user starts using Finger Manager -> logout or Session expiry occurs -> corresponding Session / Logout status is recorded.
Login Logs are an important part of the Finger Manager security and access audit system.
By recording back-office login time, authentication method, IP address, device information, and login result, the system helps institutions understand actual back-office account access.
Together with Operation Logs, role permissions, and account security policies, Login Logs can form a complete audit chain: who signed in, from where, when, whether authentication succeeded, and what actions were performed after login.
