A GPS tracking platform should let each person perform only the actions required for their role while protecting changes that affect account access. This ALTAGAMA GPS update adds specific permissions for registering phones as tracking devices and strengthens email address changes with two-step verification.
It also reorganizes password, profile, and security screens, corrects sensor 1 states received from Elink trackers, and improves API use by custom mobile applications.
Permissions for adding phones as GPS devices
ALTAGAMA GPS allows a compatible phone to work as a tracking device. With this update, account administrators can grant other users the permission needed to add phones without giving them complete administrative control.
The control supports limited and ongoing authorization. Limited authorization is useful when a team member needs to register a phone for one installation or onboarding task. Ongoing permission is better suited to technicians or managers who add phones regularly as part of their work.
This separation follows the principle of necessary access: each user receives the capability required for the task, while the account owner retains control over who can expand the list of tracked devices.
How phone tracking can be used
A compatible phone can share its location with ALTAGAMA GPS and appear with other authorized devices on the map and in history. This can support field personnel, coordinate a visit, supervise a work team, or provide temporary tracking before a dedicated tracker is installed.
Operation depends on the phone user granting the required location permissions and on the device maintaining the necessary connectivity, battery, and app execution conditions. Position frequency and continuity also depend on the mobile operating system and phone configuration.
Two-step verification for account email changes
The email address is used as a sign-in identifier and a channel for important communications. Changing it now requires two checks: entering the current password and confirming a code sent to the new address.
This flow helps demonstrate that the person requesting the change knows the current credential and can access the new email account. It also reduces typing mistakes because the update is not completed until the received code is entered.
For a business, this protection is especially useful when account responsibility changes or a corporate address is updated. An administrator can make the change and confirm that the new inbox is available before using it for sign-in.
Reorganized profile, password, and security screens
Interfaces related to the user profile, password, and other security options were redesigned to separate each task more clearly. Users can better identify which information they are changing and complete the corresponding process without mixing sensitive actions.
Clearer organization supports account maintenance: updating a profile, changing a password, and verifying a new email address are presented as distinct flows. This reduces confusion and helps apply the appropriate checks to each change.
Correct sensor 1 state for Elink trackers
ALTAGAMA GPS corrected the interpretation of sensor 1 states in Elink protocol messages. When a compatible tracker reports this input, the platform can consistently represent whether the sensor is active or inactive.
The sensor may represent different conditions depending on the model, wiring, and installation configuration. For example, an integrator may associate it with an ignition input, door, or another available signal, but its meaning must be defined according to the actual equipment.
Correct reading adds context to the GPS location and supports more reliable review of events or activity periods. It does not create a signal that the hardware does not send: a compatible Elink tracker and a properly installed input are required.
Corrected API use for custom mobile applications
API use by custom ALTAGAMA GPS mobile applications was corrected. This benefits organizations and integrators that offer a mobile experience with their own identity and need to exchange authorized information with the platform.
For users, the correction supports more consistent communication between the custom app and its enabled features. For technical teams, the integration should follow the public API contract, authenticate users through a supported flow, and request only authorized data or actions.
Specific capabilities depend on the application, its permissions, and the public services it uses. The update corrects communication with ALTAGAMA GPS, while each app remains responsible for managing location permissions, connectivity, and its user experience.
How this supports a field operation
Consider a company onboarding a temporary technician. An administrator can grant limited authorization to add the technician's phone as a tracking device without providing other administrative capabilities. The technician shares location during visits, and coordinators can view it in ALTAGAMA GPS.
If the responsible account address later changes, the administrator confirms the current password and the code sent to the new email. At the same time, vehicles with Elink trackers retain correct sensor 1 readings, and a custom mobile app can communicate through the corrected API use.
Public technical summary
- Specific permissions let authorized users add phones as tracking devices.
- Limited or ongoing authorization can match the user's responsibility.
- The current password and a code sent to the new address are required before changing the sign-in email.
- Profile, password, and account security screens were redesigned.
- Sensor 1 state interpretation was corrected for compatible Elink tracker messages.
- API use by custom ALTAGAMA GPS mobile applications was corrected.