Audit Log Redesign
Tuesday, November 10, 2026
What it is
Audit logs have been redesigned to help you find the events you need faster. There are now separate Security activity and CRM data changes tabs, event filters for each tab, and clear attribution that shows whether a person or an agent made a change. An actor filter replaces the modified by and source filters, so one search finds the person, agent or other source (like an integration) behind a change.
Why it matters
Security and CRM data events used to appear in the same log, so investigating a specific change meant sorting through unrelated entries. Tabbed events and focused filters take you straight to the events you need, and clear attribution between humans and agents shows you who or what made each change.
The Take
This should create the space to make it easier to see who's doing what, where, when, which is super important right now.
Per the panel, the audit log is redesigned. Security activity and CRM data changes now sit in separate tabs, each tab has its own event filters, and the log shows whether a person or an agent made a change. Chris read the panel's note that the new actor filter replaces the modified by and source filters: one search finds the person, agent or other source, like integrations, behind a change. It is in public beta for all hubs and tiers.
Casey picked this one and opened it. She has been one to check the audit log, she thinks it has improved over the years, and she likes these labels specifically, because if you are trying to figure out what happened when, having security activities and CRM data changes separate gives you more flexibility.
My read is that until this stuff becomes more observable, and this is going to make it a lot more observable, the actor filter is such a good filter. I have been creating properties and places in the CRM so that agents could stamp their names. That helped, but it is one of the only ways I knew of to see who did what without stamping it manually in some way. A log that attributes the change to a person or an agent on its own creates the space to see who is doing what, where, when, which is super important right now.
Here is the bigger reason. I am sure there are a lot of humans who have all of a sudden become very active in their HubSpot portal in ways they never were before, because they are using AI to do stuff. We need to be able to see that.
What to do: if you run AI connectors or agents against your portal, open the audit log this week, look at the CRM data changes tab and filter by actor for one agent you use, and check that what you see matches what you expect it did. If nobody but humans touches your portal, this is a nice-to-have and you can wait.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
FAQ
What shipped?
Per the panel, a redesigned audit log with separate Security activity and CRM data changes tabs, event filters for each tab, and clear attribution that shows whether a person or an agent made a change.
What changed in the filters?
Per the panel as Chris read it, a new actor filter replaces the modified by and source filters. One search finds the person, agent or other source behind a change, like integrations.
Why does it matter?
Per the panel, security and CRM data events used to appear in the same log, so investigating one change meant sorting through unrelated entries. The tabs and filters take you straight to the events you need.
Why is this useful now?
Chris said people who were never very active in their portal have become active because they are using AI, and that we need to be able to see that. He had been creating properties so agents could stamp their names; the attribution in the log makes it easier to see who is doing what.
What did Casey say about it?
Casey has checked the audit log before, thinks it has improved over the years, and likes the security activities and CRM data changes labels for working out what happened when.
Produced by Value-First Media