{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/060cb746d59f4c978e27d642fd43a146\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/060cb746d59f4c978e27d642fd43a146-72ef835bbc36d543.gif","duration":77.043633,"title":"Using Ashby Audit Logs for Change Tracking","description":"This Loom explains how to use Ashby audit logs to investigate a specific event and understand opt-in feature changes. The video focuses on filtering activity over the past week and searching by event category to see which opt-in features were enabled; it then shows how to drill down to the actor if needed. After running the search, it identifies that on October 13, Walter Mellon enabled the MCP server as an organization setting via the Ashby app. It also demonstrates filtering by channel to review application changes made through the Ashby MCP, including a stage change by Julie for candidate Sophia Alvarez, with a link target to open the full record context."}