We’re excited to share a breakthrough from our 2025 Hackathon that moves us closer to our vision of a more seamless and client-centric experience: the Contextual Audit Log.

Clients will soon be able to view transaction edits directly within Addepar, eliminating friction and bringing greater transparency and confidence to their data. The Contextual Audit Log is a feature that will be accessible directly through the View Change History button in the transactions panel. 

This idea of contextualizing the audit log represents a significant shift toward giving users immediate, meaningful insights into their data, fostering greater transparency, trust and efficiency across the platform.

Priority #1: Eliminating friction

The Contextual Audit Log was developed in direct response to persistent pain points and clear demands from our clients, demonstrating our focus on a frictionless experience.

Historically, investigating data changes required users to manage a complex, multi-step process:

  • Data overload and usability: The General Audit log contains a large volume of data. That data overload makes it difficult for users to read, interpret and understand the sequence or context of changes.

  • Limited visibility: Access to the full audit log data is restricted to only a small subset of users with firm admin access, limiting transparency and collaboration across client teams.

  • Slower support resolution: This lack of on-demand visibility frequently led to support cases, which required our team to run long searches to isolate changes. A single request often meant downloading massive files over a broad period of time, which could exceed the current limitation of 100,000 rows, a frustrating roadblock for our clients.

This feature is a direct answer to multiple product ideas requesting more visibility into when changes are made. The Contextual Audit Log eliminates this bottleneck and transforms it into a seamless, self-service experience.

Key technical implementations: Bringing context to the forefront

Our technical approach focused on leveraging and enhancing existing capabilities to deliver an integrated experience, moving from a system of broad logs to one of pinpointed context.

  • API enhancement for context: The current audit log already contains the necessary transaction ID information, but this field was not exposed as a filterable parameter. We now expose the ID fields to allow for filtering on transaction ID.

  • Instant self-service via UI (Activity Feed): We decided to use a modal to display the activity. Instead of a large, tabular export, we created Contextual Change History that shows the change history right on the transaction screen. This new view presents changes as a clear activity feed, enabling users to see the changes that matter right where they happen. Users will be able to click on the Show Transaction History button directly in the transaction details to view this history.

  • Targeted data display: The tool works by parsing the data and providing a contextual payload based on the transaction ID. Users will also be able to download the filtered results.

Operational efficiency and future foundation

Audit logs are designed to provide context, showing who performed an action, what the action was and the result. By providing fast, self-service answers, we’re empowering our clients with instant data transparency, which in turn builds trust. This also frees up our support team for higher value tasks. 

This upcoming feature is just the first step. We plan to bring this same contextual, easy-access change history to other audit logs across the platform. Future opportunities for improvement include adding a filter for a specific attribute value and adding the ability to filter by transaction ID and transaction type on the main Audit Log page for a uniform experience. Ultimately, this project lays the foundation for a more robust and responsive platform, enabling our clients to operate with greater confidence and efficiency.

This feature is in its final validation stage, and we are targeting a release for early 2026.