Contents:

• Overview
• Use Cases
• Prerequisites
• Accessing Audit Logs
• Searching Audit Logs
• Interpreting Audit Logs
• Salesforce Reporting on the Log Object
• Considerations: Permissions, Security, and Data Handling
• Troubleshooting and FAQ

 

Overview

Audit Logs let you see the full story of what LeanData did to a record across all Orchestration and BookIt processes in a single chronological view. Instead of switching between per-object or per-product log pages to piece together a record's journey, you open the Audit Logs page, search by an identifier like email or Salesforce ID, and review every LeanData node, edge, ownership change, and scheduling action that touched that record.

This guide is written for RevOps and Sales Ops admins who troubleshoot routing and scheduling decisions, and for anyone who fields "what happened to this record" questions inside their organization.

Use Cases

Audit Logs help admins answer "what happened to this record" questions quickly and confidently. Common scenarios include:

• Troubleshooting why a lead was assigned to a specific owner across both routing and scheduling.
• Tracing a record's full journey when Orchestration routes it and BookIt for Forms books a meeting on the same record.
• Investigating concurrent processing when multiple graphs act on related records, such as a lead routing graph and an account routing graph running simultaneously.
• Auditing ownership changes, booking outcomes, or node decisions for a specific record without switching between per-object log pages.
• Sharing a single log link with teammates that captures every LeanData action on a record, rather than coordinating across several pages.

 

Prerequisites

Audit Logs run on a cloud log infrastructure layer that lives outside Salesforce. Because audit logs contain CRM data, LeanData cannot move that data on your behalf. Your organization initiates use of Audit Logs by syncing audit logs to the cloud. Once enabled, your audit log data is indexed in cloud storage so it can be searched across products and objects in seconds.

New Audit Logs are an opt-in capability. Until an admin syncs audit logs to cloud storage, you continue to see the legacy per-product Audit Log pages.

To enable Audit Logs:

1. From the LeanData app, navigate to Admin > Settings > Reporting tab > Store Audit Logs in the Cloud.
2. Under Step 1: Sync your Salesforce Audit Logs, click Start Syncing. Confirm and authorize that you want to proceed. This initiates a job that syncs your audit logs to cloud storage.
3. Once your audit logs finish syncing, under Step 2: Enable Advanced Search and Filtering, toggle the setting on to transition to the New Audit Logs interface.

What Gets Copied to the Cloud

• Audit log records produced by Orchestration and BookIt routing.
• Routing context already present in those logs, including matched records, owner changes, node decisions, and deployment metadata.
• Customer CRM data outside of audit logs is not copied.

 

Accessing Audit Logs

After Audit Logs are enabled, Audit Logs appears as a top-level entry in the LeanData app navigation. Open it from the left sidebar.

Bookmarks and shared URLs that point to legacy audit log pages also redirect to the unified experience with the appropriate filter applied, so links you have previously shared with teammates continue to work.

 

Searching Audit Logs

The first time you open Audit Logs in a session, you land on a search-first page. You have three ways to search: Basic Search, Recommended Searches, and Advanced Searches.

Basic Search

The Basic search bar accepts an email, Salesforce ID, name, or company, and allows you to filter by date range and object type.

Click Search to return every log LeanData has produced for the selected criteria, across products and objects, in a single chronological view.

Recommended Searches

Recommended Searches give you quick access to common searches without needing an exact identifier in hand.

Click one of the recommended search tiles to run that search.

Advanced Searches

If a basic search or a recommended search does not fulfill what you are looking for, you can add more filters by clicking the advanced search toggle at the top. This opens a filter panel that lets you filter results by criteria such as New or Previous Owner, Outcome, and many others.

Click Search once you have applied your filters to re-run your search.

 

Interpreting Audit Logs

Page Navigation

1. Your filter parameters appear on the left.
2. On the top right, you can expand or collapse the logs depending on how you want to view them.
3. You can copy a link to the logs with your saved search parameters.
4. You can download a CSV of the log information.
5. You can reprocess selected logs:
   • Click Reprocess Logs in the upper left.
   • Use the checkboxes to select the logs you want to reprocess. Ineligible logs are not selectable.
   • Click Show Selected Only to focus on your selection, or Return to Search and Filters to bring the rest back into view.
   • Click Reprocess Logs in the top banner to start.
   • LeanData reprocesses these logs on the active graph using their original entry edge.
     • If your user has the LeanData Custom Objects Full Access permission set, reprocessing runs in real time and your user is the User of record.
     • Without that permission set, reprocessing runs asynchronously in a batch and the LeanData Integration User is the User of record.
6. Your search results show every log that meets your search criteria, with the most recent at the top.

Each log entry uses a three-panel layout: Object, Path, and Outcome.

Object Panel

The Object panel shows information about the record itself at the time it was processed.

1. A label indicates which object and product acted upon the record for this log.
2. The name of the record. You can also copy a link to this specific log to share with someone, or open the record in Salesforce.
3. Fields that were on the record at the time of processing. This snapshot helps identify what was on the record at processing time versus what may have been updated later.
4. The Routing Deployment field links to the specific FlowBuilder deployment that processed the record.
5. Processed At shows the timestamp of when LeanData picked the record up.
6. Explain this Log opens the LeanData Audit Log Assistant to summarize how LeanData processed the record. This assumes you have enabled this feature. For more information, see the LeanData AI Assistant Guide. 
7. More Info opens additional fields from the record at processing time.

Path Panel

The Path panel shows the exact path the record took through a routing graph for this transaction, including each node it interacted with and the outcome from each node.

• The first entry is the trigger node and edge that brought the record into the graph. Records initiated by the resumption of a Track SLA node or real-time processing are called out explicitly.
• Each subsequent entry shows the node type, node name, and the exit edge.
• Match nodes display the chosen match plus any other candidates that were considered. More Info shows the filter and tie-breaker criteria used.
• The path ends in a terminal edge, typically End of Flow.

Outcome Panel

The Outcome panel summarizes the actions for this particular transaction.

1. Triggering Action: insert, update, scheduled job, one-time job, and other entry types.
2. Action Outcomes: a summary of what LeanData did during processing.
3. Ownership / Booking: the new owner and the previous owner of the record, or the booking information for a scheduled meeting in the case of LeanData scheduling.
4. More Info: expand to see more details about the actions LeanData took.

Following a Record's Journey Across Products

The unified view stitches Orchestration and BookIt logs together so you can see the full sequence of LeanData decisions on a record in one place. Common patterns this surfaces:

• A lead routed by Orchestration that then books a meeting through BookIt for Forms.
• A BookIt Handoff event that triggers a downstream contact or account log.
• Concurrent graphs running on the same record, such as a lead routing graph and a related account routing graph updating simultaneously. Entries are timestamp-ordered, and the deployment name on each entry tells you which graph produced it.

AI Audit Logs Assistant

In the bottom right corner, a button opens the LeanData AI Audit Logs Assistant.

The assistant lets you use natural language to ask questions and understand your audit logs.

For more detailed information, see the LeanData AI Assistant Guide.

 

Salesforce Reporting on the Log Object

Audit Logs are written to the LeanData__Log__c Salesforce object, so you can build native Salesforce reports from your logs. For more information, see Routing Logs Object Reporting Guide.

 

Considerations: Permissions, Security, and Data Handling

• Access: Users with the LeanData Dashboard Access can view audit logs. Only users with LeanData Custom Objects Full Access can enable or disable the cloud storage for Audit Logs.
• Data residency: Audit log data is stored in encrypted Amazon Web Services (AWS) cloud storage operated by LeanData. Audit log data is isolated per customer tenant.
• LeanData AI Assistant Scope: Customer audit log data is indexed for search only. It is not used to train AI models, and it is not shared across customers.

 

Troubleshooting and FAQ

A search returned no results.

• Confirm the date range is wide enough. Logs are kept only for the configured retention period (90 days by default). If you searched by email or name, try the Salesforce ID instead.

Older logs are missing or look truncated.

• Logs older than the configured retention period are deleted nightly. If the missing logs are within retention, contact LeanData Support.

A filter is unavailable.

• Some filters only apply to certain log types. Scheduled User, for example, only applies to BookIt logs. Adjust the filter set or broaden your result scope.

Syncing Audit Logs with Cloud Storage appears greyed out.

• You need admin settings access to enable cloud audit logs. Confirm with the workspace admin who manages your LeanData settings.

A BookIt log isn't appearing alongside an Orchestration log for the same record.

• BookIt meeting logs are out of scope for the unified view. Other BookIt routing logs should appear in the chronological view. If they do not, contact LeanData Support and include the record's Salesforce ID and the approximate processing time.

 

Summary

Audit Logs bring Orchestration and BookIt audit data into a single, searchable chronological view so admins can quickly investigate how LeanData processed a record.  Understand the full record journey across Salesforce Obects and LeanData processes.  

For questions or additional assistance please contact LeanData Support.