[SFS] How to Track Dispatcher Console (Gantt) Access Using Salesforce Event Monitoring

Option 1 — Event Log File Browser (UI)

Use this option if you prefer a no-code approach via the Salesforce Setup UI.

1. Go to Setup > Quick Find and type Event Log File Browser.
2. Select the date range you want to review.
3. Download the VisualforceRequest event type as a CSV file.
4. Open the downloaded CSV file in a spreadsheet application such as Excel or Google Sheets.
5. Filter the URI column for rows that contain the value FSL__vf001_ServiceExpert.
6. Each matching row identifies a dispatcher who accessed the Dispatcher Console:
   1. The USER_ID column contains the Salesforce User ID of the dispatcher.
   2. The TIMESTAMP column shows the exact date and time of access.

Option 2 — SOQL Query via the API

Use this option if you need to query programmatically or export results at scale via the Developer Console, Workbench, or a connected app.
To retrieve VisualforceRequest event log files via the API, query the EventLogFile object filtering for EventType equal to VisualforceRequest, ordered by LogDate descending. This returns one record per daily log file. Each record contains a downloadable binary body that represents a CSV file of all Visualforce page load events for that day.
To identify Dispatcher Console access within the log file:

1. Download the binary body of the EventLogFile record via the Salesforce REST API using the /sObject/EventLogFile/{Id}/LogFile endpoint.
2. Parse the downloaded file as a CSV.
3. Filter rows where the URI column contains FSL__vf001_ServiceExpert. Each matching row represents a single Dispatcher Console page load.
4. Use the USER_ID column to identify the dispatcher and the TIMESTAMP column for the access time.

Option 3 — Approximate Tracking (No Shield License Required)

Use this option if your org does not have Salesforce Shield or the Event Monitoring add-on. This method provides an approximate indicator only and is not suitable for precise audit or compliance requirements.
Each dispatcher in Field Service has a record in the FSL__UserSetting__c object that stores their Gantt display preferences, such as territory filters and scheduling view settings. The LastModifiedDate field on this record updates whenever the dispatcher changes their configuration settings inside the Dispatcher Console.
To use this as an approximate proxy for Dispatcher Console access:

1. Query the FSL__UserSetting__c object, selecting FSL__User__c, FSL__User__r.Name, and LastModifiedDate, ordered by LastModifiedDate descending.
2. The resulting list ranks dispatchers by when they most recently modified their Gantt settings.
3. Treat the LastModifiedDate as a proxy for recent activity — note that this field reflects the last settings change, not necessarily the last page load. A dispatcher may open the Gantt without modifying any settings, in which case this date will not update.
   
   

Known Limitation:  In-Gantt Actions Are Not Individually Logged
Salesforce Event Monitoring records the Visualforce page load event when a user opens the Dispatcher Console, but it does not differentiate individual actions performed within the Gantt — such as drag-and-drop scheduling, service appointment candidate selection, or custom action execution.
These actions execute within the Field Service managed package context and are not captured as separate entries in the EventLogFile object. The supported event types in EventLogFile do not include granular in-Gantt interaction events.
Impact: You can confirm that a dispatcher accessed the Dispatcher Console (page load), but you cannot use Event Monitoring alone to confirm what actions they performed inside the Gantt after opening it.