The Audit Log plays a crucial role in maintaining transparency by recording when a user attempts to update or change data within the system, across key object types within aXcelerate. The Audit Log provides a clear record of changes made within the system, including time, date, actor and object.
Key highlights include:
- Track User Intent: Logs when a user attempts to change or update data and the intended change.
- Increased Oversight & Accountability: Helps Internal teams monitor user activity and maintain data integrity.
Accessing the Audit Log
Access to the Audit Log is controlled by the Audit Log Access permission (set to Full Access) in the user's role settings.
Warning: As the Audit Log permission is a Full Access permission, enabling this permission for a user will allow them to view data, typically controlled by System Field restrictions or whether the View option has been enabled against a permission group.
Once configured, the Audit Log will appear under the Settings item within the navigation menu.
Audit Log filtering
Access to the Included Audit Log is available to clients on both Standard and Turbo packages. Platinum services clients will have access to additional granularity as outlined below.
Included Audit Log:
- View data for the last 90 days
- View changes made to a specific object
Enhanced Audit Log (Exclusive to Platinum Service):
- View up to 1 year of data at a time within the last 3 years
- View changes made to a specific object or by a specific actor
- Filter between dates to view data from a specific point in time
Note: Please reach out to our Customer Success Team here to discuss the benefits of Platinum Service, including the Enhanced Audit Log.
Warning: Changes made before 28/02/2025 will not be displayed within the results, as these predate object tracking. To find a comprehensive list of tracked items and the date tracking began for each, please see the Data in the Audit Log section below.
Object: Filter by the specific object that has been changed or updated. First, select the object type from the dropdown, then choose the relevant option. For example, if Workshop is selected as the object type, you will then be prompted to enter the Workshop ID to refine the results.
Actor: Filter by the user who performed the action. Defaults to the current user. In future, "system" actors will also be included for automated changes made by the aXcelerate system.
Date Range: When using Actor View, filter between two dates.
To return to the default view, simply select the Reset icon.
Data in the Audit Log
Name
Description
Date & Time (UTC)
The specific date and time of the change
Actor
The user who has implemented the change
Object Type
The type of object updated. A full list of supported Object Types is available below
Object
The specific object updated
Action
The type of activity the actor attempted (update, create, or delete)
Field
The specific field within the page that was interacted with-if applicable
Change
The change that occurred
Data in the Audit Log can be accessed through the By Actor or By Object view. Currently, certain objects can only be tracked within a specific view. The available objects and the dates tracking began are listed by view below:
Object Type
Date tracking began
Users
28/02/2025
User Roles
28/02/2025
Contacts
28/02/2025
Qualification Auto Certificate Configuration
28/02/2025
Courses/ Classes
28/02/2025
Workshops
28/02/2025
Workshop Bookings
28/02/2025
Trainers
28/02/2025
Portfolio Types
14/06/2025
Object Type
Date tracking began
Contact
28/02/2025
User
28/02/2025
User Role
28/02/2025
Trainer
28/02/2025
Qualification Auto Certificate Configuration
28/02/2025
Workshop
28/02/2025
Workshop Enrolment
28/02/2025
Portfolio Item
28/02/2025
Note: If you’d like to request additional object support or provide feedback on this feature, please fill out our feedback form.
In most instances, audit log entries reflect actions that were successfully executed. However, it’s important to note that even in the rare case of unsuccessful attempts, where a change did not ultimately go through, these are still captured and displayed in the log.
Because of this, we recommend using the Audit Log primarily to track user intent and identify who attempted to perform specific actions, rather than relying on it as a definitive Change Log that reflects actual data modifications. This tool can be used in conjunction with internal processes to understand user activity and maintain data integrity.
Example log entry
A log entry will contain data within each field relevant to that event.
In the above log, we can see that Debra Kennedy (Actor) submitted a change to a Contact (Object Type) to update the Contact Name section (Field) from blank to Jonesy (Action) on Ellen Ripley’s contact page(Object) on 23/06/2025 at 4:34 am (Date & Time).
Audit Log F.A.Q
Is the Audit Log the same as a Change Event Log?
The Audit Log records attempted changes made by users in the system. In most cases, these entries reflect changes that were successfully applied. However, even if a change fails, the attempt is still logged and shown. We recommend using the Audit log to confirm who attempted to perform a specific action within the system rather than as a Change Log.
Can I see more info about using the audit log?
Why do some entries show no field or change?
This typically means it's a “parent” record associated with a nearby timestamp. For example, there might be a blank “Update contact” record with records below indicating which fields were changed. Check adjacent entries for more details.
Will automated actions (carried out by the system) be visible within the log?
At this time, the log will only display actions completed by an Actor (User)
How can I provide feedback on the Audit Log?
There is a Feedback icon in the top right corner of the Audit Log Dashboard. This will open a Google Form in a new tab where feedback can be provided directly to our team.
Audit Log planned improvements
We plan to add additional functionality as this feature matures. Some items on our roadmap for this product include the following:
- Back-end export of Audit logs
- Expanded actor support, including system-initiated changes
- Ability to view audit logs for a specific object (e.g., Class or Workshop) directly from the Object’s detail page