A GPS tracking account can contain locations, routes, alerts, reports, and operational data for vehicles or assets. Protecting that access matters even when a strong password is used. We therefore introduced two-factor authentication, also known as 2FA, to add a temporary verification step to ALTAGAMA GPS sign-in.
With 2FA enabled, knowing the password is no longer enough to enter the account. The user must also provide the current code generated by a compatible authenticator app. This second check reduces the risk of access when a password has been exposed, reused, or obtained through deception.
What two-factor authentication means
Two-factor authentication combines two different checks. The first is something the user knows: a password. The second is a temporary code available in an authenticator app previously linked to the account.
These codes change periodically and work only for a short interval. Even if another person learns the password, they would still need access to the configured authenticator to complete sign-in.
ALTAGAMA GPS supports authenticator apps compatible with temporary codes, including well-known options for mobile phones and credential managers. The selected app can follow each company's device and security policies.
How to enable 2FA in ALTAGAMA GPS
The option is available in the user's account settings. The process first confirms that the person making the change controls the credentials and associated email, then allows the code-generating app to be linked.
- Open account settings and select the option to enable two-factor authentication.
- Confirm the current password.
- Enter the verification code sent to the account email.
- Scan the code displayed by ALTAGAMA GPS with a compatible authenticator app or use the available linking key.
- Enter the temporary code generated by the app to confirm that the connection works.
Protection becomes active only after the first temporary code is validated successfully. This prevents an account from being left with an authenticator that was not linked correctly.
What changes during sign-in
After the usual credentials are entered, a protected account requests the security code generated by the app. The user opens the authenticator, locates the ALTAGAMA GPS entry, and provides the current code.
This additional step applies to platform access and protects the functions available to that user, such as the map, route history, device management, alerts, and reports. Existing permissions continue to determine what each person can view or change.
If the code changes while it is being entered, the new value should be used. The time on the phone running the authenticator should remain synchronized so temporary codes can be validated.
How 2FA helps protect a GPS tracking operation
- Exposed passwords: makes a leaked credential less likely to be sufficient for accessing locations and routes.
- Shared computers: adds a personal check when several people use workstations in an office or control center.
- Remote work: strengthens access for managers who review a fleet away from company facilities.
- Staff changes: reduces risk during transitions while administrators review users, permissions, and sessions.
- Administrative access: adds a barrier for accounts that can change devices, groups, alerts, or settings.
A real-world case: protecting a monitoring center
A transport company uses ALTAGAMA GPS to supervise vehicles, receive alerts, and review routes. A manager works from several locations and the password becomes exposed after an attempted sign-in on a deceptive page.
Without a second check, that password could provide access to operational information. With 2FA enabled, the attempt also requires the temporary code available in the manager's authenticator. The company gains time to change the password, review security activity, and confirm that permissions remain appropriate.
The same measure is valuable for administrators, security companies, logistics operators, cold-chain managers, and customers who review assets through individual accounts.
Protected removal of the second factor
ALTAGAMA GPS also protects the process used to disable 2FA. The user must confirm the current password and complete a verification sent to the associated email before the second factor is removed.
This check prevents someone who finds an open session from easily disabling the security measure. Enabling and disabling 2FA are connected with the account's security history to support later review.
The second factor should not be disabled only for convenience. When replacing a phone, plan the authenticator transition while access to the previous device and registered email is still available.
Recommendations before enabling 2FA
- Confirm that the account email is current and protected.
- Install an authenticator app from a trusted source.
- Protect the phone with a screen lock and keep its date and time synchronized.
- Do not share passwords, temporary codes, screenshots of the linking code, or setup keys.
- Give team members individual accounts instead of using one shared credential.
- Review users, permissions, and security activity periodically, especially after staff changes.
What to do when a phone changes or is lost
Before replacing a device, review the transfer or backup options offered by the selected authenticator app. Each application handles this process differently.
If codes can no longer be generated, use ALTAGAMA GPS support and verification channels. Never send a password or temporary code in response to an unsolicited message. Support may request identity checks to protect the account before assisting with access.
Keeping the associated email current is essential because it participates in the checks used when this protection is changed.
2FA complements permissions and good practices
Two-factor authentication protects sign-in, but it does not replace proper administration. Each team member should have an individual user, receive only the required permissions, and lose access when the responsibility ends.
It is also important to use unique passwords, close sessions on public computers, review security activity, and keep contact details current. Combining these measures protects tracking information more effectively than any one measure alone.
Benefits for ALTAGAMA GPS customers
- An additional layer for protecting locations, routes, and settings.
- Temporary codes generated by compatible authenticator apps.
- Activation confirmed through a password, email, and a valid first code.
- Additional verification on subsequent sign-ins.
- Protected removal to prevent unauthorized changes.
- Security change history to support account review.
Technical summary for users and administrators
- 2FA is configured per user account from security settings.
- Linking uses an application compatible with temporary codes.
- Activation requires password confirmation, email verification, and a valid authenticator code.
- Later sign-ins request a password and temporary code when the function is enabled.
- Disabling the function requires identity checks again.
- Device time accuracy affects temporary code validation.
- 2FA reduces the risk of a compromised password but does not replace permissions, unique passwords, or activity review.
Explore GPS tracking, security, alerts, reports, and administration in the ALTAGAMA GPS plans and features.