# Support Audit Log Source: https://docs.astalty.com.au/guide/scheduling/support-audit-log > View recent activity and track changes made to Participants and supports. Scheduling add-on - This feature requires the Scheduling add-on, which is available on Astalty Premium. See How to enable Scheduling. ## Overview Use a support's Audit Trail to find who changed it, when it changed, what changed and the reason entered for the change. For each change, the Audit Trail records: - Time and Date the change was made - User who made the change - Details of what was changed - Reason for the change (when there are changes made to supports) > **Related** > > Active overnight periods (sleepover disturbances) also have their own audit trail showing who logged each disturbance and exactly when it was submitted. See [Viewing the Audit Trail for an Active Overnight Period](https://docs.astalty.com.au/guide/scheduling/adding-shifts/creating-a-sleepover-or-active-overnight-support#viewing-the-audit-trail-for-an-active-overnight-period). ## Viewing an Audit Trail on a Shift 1. Open [**Schedule**](https://app.astalty.com.au/scheduling/schedule). 2. Select the support you want to review. 3. Open **Actions** in the support toolbar. 4. Select **Audit Trail**. ![A support's Details tab with the Actions button highlighted and its menu open, with an arrow on Audit Trail between Unpublish Shifts and Email Notes.](https://docs.astalty.com.au/assets/audit-trail-actions-1.png) > **Related** > > The **Actions** menu also lets you email the Support Worker notes on a support. See [Emailing Support Notes](https://docs.astalty.com.au/guide/scheduling/emailing-support-notes). - The Audit Trail lists each change, when it occurred, who made it, and any reason they entered. - A support in a different timezone can show start and end time changes in that support's timezone rather than yours. - Adding or removing [custom allowances](https://docs.astalty.com.au/guide/scheduling/setup/custom-allowances) on a shift is recorded, naming the allowances added and removed. Only users who can see custom allowances see these entries. - Automated [SMS Reminders](https://docs.astalty.com.au/guide/settings/sms-reminders) sent for the support are recorded too. They appear on the **Reminders** tab of the Audit Trail rather than alongside the other changes - see [Reminders sent for a support](#reminders-sent-for-a-support). ![The Audit Trail tab of a support, beside Location Events and Reminders, listing Admin User publishing the shift, the push notification sent to Arlo Jones, an End Time change from 12:00 PM to 12:30 PM with its reason, the updated auto charge and the details the support was created with, each with its time.](https://docs.astalty.com.au/assets/audit-trail-results-1.png) > **Enter a useful reason for each change** > > When updating support details, always provide a clear reason. This will appear in the Audit Trail for transparency and future reference. ## Recording a Reason for a Change on a Shift If you need to record a reason for a change: - Click into the shift you want to update. - Select **Update Details**. ![A support's Details tab showing its date, times, SMS reminder, location and Charge Item Set, with the Update Details button highlighted.](https://docs.astalty.com.au/assets/image3-1757977923.png) - Make the necessary changes to the relevant fields. - Scroll down below **Admin Details** and enter the **Reason for Change** in the provided field. ![The support update form with a reason entered in the highlighted Reason for Change field, below Send SMS reminder for this support and above Charge Option and the Update button.](https://docs.astalty.com.au/assets/image4-1757977954.png) - Click **Update**. The shift will be updated with the new details, and the reason you entered will be saved. This reason will then appear in the Audit Trail for that shift, along with the date, time, and user who made the change. ## Reason for Unassigning Staff Any changes made to the attached Support Workers in a published shift will require a **Reason for Unassign.** ![A published support with the three dots menu on Arlo Jones's shift card highlighted and open, and an arrow on Unassign Support Worker below Reassign Support Worker.](https://docs.astalty.com.au/assets/unassign-support-worker-1.png) ![A Confirm dialog asking whether to unassign Ken Kessler from this shift, with the Reason for unassign field highlighted and an arrow on the Confirm button.](https://docs.astalty.com.au/assets/unassign-support-worker-2.png) When a worker is unassigned, the Audit Trail records the worker, the user who made the change, the time, and any reason entered. ![The Audit Trail tab with entries highlighted showing the Shift User changed from Arlo Jones to no one with the reason Arlo is unwell and cannot attend, then to Ken Kessler, and the unassigned and assigned push notifications sent to each worker.](https://docs.astalty.com.au/assets/audit-trail-update-support-worker-1.png) ## Travel Removed From a Support Every time travel is removed from a support or group support, the Audit Trail records it. The entry names the travel type and the driver, lists what the Support Worker had recorded against it, and says who actioned the removal: > Travel **From Support** for **Amy Worker** was removed. It had recorded odometer readings **500 to 530** and odometer photos attached. Removal actioned by **Jane Admin** The "It had..." sentence only appears when there was something to report, and covers odometer readings, whether odometer photos were attached, and the approved distance. Travel removed with none of these recorded produces the shorter entry: *Travel To Support for Amy Worker was removed. Removal actioned by Jane Admin*. > **Recorded start and end times aren't listed in the entry** > > The Audit Trail entry captures odometer readings, odometer photos and approved distance, but not the worker's recorded start and end times. Those times are shown in the [Remove recorded travel?](https://docs.astalty.com.au/guide/scheduling/travel-to-during-and-from#confirming-removal-of-recorded-travel) confirmation before you remove the travel, so check them there if they matter. Because the entry is written for every removal, the Audit Trail is also where to look for the removals that don't ask you to confirm first - including travel removed across a series of shifts, and travel dropped when a Participant is de-selected from a group travel row. See [Confirming Removal of Recorded Travel](https://docs.astalty.com.au/guide/scheduling/travel-to-during-and-from#confirming-removal-of-recorded-travel). ## Location Tracking You can view location tracking details recorded during a shift in the **Audit Trail**. To access this information, open the **Audit Trail** and select the **Location Events** tab. ![The Audit Trail window with an arrow on the Location Events tab, listing Arlo Jones clocking out, clocking in, ending and starting travel towards the shift, each with an address, Source: Native App and a time.](https://docs.astalty.com.au/assets/location-tracking-1.png) > **Important** > > Location data is only recorded at specific points: when a user clocks in, clocks out, starts travel, and ends travel. No location tracking occurs in the background while a shift is in progress. ## Reminders sent for a support If your organisation uses [SMS Reminders](https://docs.astalty.com.au/guide/settings/sms-reminders), the **Audit Trail** has a **Reminders** tab listing every reminder sent for that support. For each one you'll see the reminder window (for example *24 hours before*), when it was sent, the Participant it went to, the delivery status (for example **Sent**, **Delivered**, or **Failed**), and the message body. If none have gone out yet, it shows *"No reminders have been sent yet."* > **Replies aren't recorded here** > > The **Reminders** tab only records what was **sent** to the Participant - it doesn't capture their replies. To read a Participant's response, including a **YES** or **NO** confirmation, open the conversation in your [SMS inbox](https://docs.astalty.com.au/guide/settings/two-way-sms#using-the-sms-inbox).