Current challenge
Fleet Manager currently does not provide a clear way to identify who made a particular change within an account. This becomes especially important when an account has multiple administrators, or in situations where there is concern that an administrator account may have been compromised.
Changes to areas such as aircraft settings, site access, member invitations, permissions, and visibility can have a significant impact, but there is currently no straightforward way to determine which administrator made the change.
Visibility changes are particularly important. Accidentally granting the wrong users visibility or access to aircraft tracks could have repercussions for a customer's business, making it important to have accountability and traceability around these actions.
Proposed solution
Introduce an Activity / Audit Log within Fleet Manager that records significant administrative changes and identifies who performed them.
Ideally, this would be presented as a chronological feed showing information such as:
Who made the change
What was changed
Where the change was made
When the change occurred
Where appropriate, the previous and new values
For example:
John Smith changed Aircraft ABC123 visibility from "Site A" to "Site A + Site B" on the Aircraft Settings page – 14:32, 1 October 2026.
The feed could cover key administrative actions including aircraft configuration, visibility and permissions, site access, member invitations, user changes, and other security-sensitive settings.
Customer benefit
An audit log would provide greater accountability for organisations with multiple administrators, make accidental changes easier to investigate, and help customers identify potentially unauthorised activity.
Importantly, it would provide a traceable record for changes affecting aircraft and track visibility, where an incorrect configuration could expose information to users who should not have access to it.