What This Update Actually Is
HubSpot's Audit Log tool got a full structural redesign. It now splits into two top-level tabs: Security Activity and CRM Data Changes.
Each tab has its own event type list, its own filters, and a unified Actor filter that replaces the old "Modified by" and "Source" filters. Time range selection now lives right in the filter bar.
Attribution got smarter too. The log now clearly labels whether a person or an AI agent made a change. That distinction matters more and more as AI agents take actions inside portals.
Any existing bookmarks or deep links you've saved will redirect to the new structure automatically. You don't need to touch a single setting for this to work.
Why HubSpot Shipped This
Before this change, every event type lived in a single log. Security events, record edits, property changes, login activity: all mixed together.
If a client called and asked why a contact's lifecycle stage changed last Tuesday, you had to scroll past login events, permission changes, and integration activity just to find it. That's slow and frustrating, especially in busy portals.
There's also a bigger driver behind this: AI agents. As HubSpot's Breeze agents take more autonomous actions inside the CRM, knowing whether a human or an agent made a change isn't a nice-to-have. It's a governance requirement. The redesigned attribution layer is HubSpot's answer to that growing need.
How to Use It Step by Step
- Navigate to Settings and open the Audit Log tool. You'll see two tabs at the top: Security Activity and CRM Data Changes.
- Pick the tab that matches your investigation. Security events like logins, permission changes, and SSO activity live under Security Activity. Record edits, property updates, and data changes live under CRM Data Changes.
- Use the Events filter to narrow by event type. Each tab only shows the event types relevant to that tab, so you won't see CRM events listed under Security and vice versa.
- Use the Actor filter to search by the person, AI agent, or integration that made the change. One search box, one unified result, no juggling two separate filter fields.
- Set your Time Range directly from the filter bar. No extra clicks to a date picker buried elsewhere.
- If you've bookmarked a specific Audit Log view, visit it. The redirect to the new structure happens automatically. Confirm the new URL and update your bookmark if you share it with teammates.
What It Touches in Your HubSpot Strategy
This update sits at the intersection of data governance, RevOps accountability, and AI agent oversight. It's not a flashy feature, but it touches every part of your portal.
Here's where you'll feel it most:
- CRM data hygiene investigations: quickly isolate which property changed, when, and who changed it, so you can fix root causes instead of symptoms.
- AI agent governance: the human-vs-agent attribution layer lets you audit what Breeze agents have actually done inside your portal, which is critical as agent autonomy grows.
- Security incident response: the Security Activity tab gives your IT or operations lead a clean, filtered view without noise from CRM activity cluttering the picture.
- Integration and automation auditing: the Actor filter now surfaces integrations and automated sources alongside humans, so you can tell whether a workflow or a connected app caused a data change.
Key Takeaway
The human-vs-agent attribution isn't cosmetic. As Breeze agents take actions autonomously inside your CRM, your ability to audit and govern those actions depends entirely on clear attribution. This redesign builds that foundation.
If your team is already working with AI agents, like the Customer Agent configuration tools HubSpot has been building out, the Audit Log redesign becomes your accountability layer for everything those agents touch.
It also pairs directly with how Breeze agents are expanding across the platform. If you want to understand the full picture of what agents can do and what guardrails you should have in place, the article on the HubSpot agentic platform gives you the strategic depth you need.
Key Takeaway
RevOps leaders should treat the Audit Log as a live governance tool, not just a historical record. Build a habit of reviewing CRM Data Changes after any major workflow or agent deployment to catch unintended behavior early.
Who Should Care Most
This update matters to any human with admin access or data oversight responsibility. Here's who gets the most value:
- HubSpot admins who regularly field "why did this change?" questions from sales or marketing. The tabbed structure cuts investigation time significantly.
- RevOps leaders who are deploying Breeze agents or complex automation workflows and need to verify that changes are happening as intended.
- Operations or IT leads responsible for security compliance who now have a clean, uncluttered view of login events, permission changes, and access activity.
- Growing companies with multiple integrations who need to trace data changes back to a specific source without manual cross-referencing.
Since this update is available across all hubs and tiers, even humans running a Starter-tier portal get the cleaner experience. There's no paywall here.
George's Take
I've been inside hundreds of HubSpot portals, and I'll tell you: the Audit Log used to be the tool you visited as a last resort because finding anything in it took forever. This redesign fixes that. But what I really want you to notice is the attribution layer. HubSpot is building a future where agents do real work inside your CRM, and that work has to be auditable. If you don't know whether a human or an agent changed a contact's status, you can't govern your data or your AI strategy. This update is quiet infrastructure for a noisier, more automated future, and I'm glad to see HubSpot building it now.
“The Audit Log redesign isn't about convenience. It's about accountability in a world where agents are making real decisions inside your portal. Know who did what. Every time.”
If you're not sure your portal's data governance is keeping up with the pace of automation and AI, that's exactly the conversation we have during a Sidekick strategy session. We review what's happening inside your portal, map your governance gaps, and help you build a system where every change is traceable and intentional. Book a strategy call and let's make your portal something you can trust.
Frequently Asked Questions
What changed in HubSpot's Audit Log redesign?
HubSpot split the Audit Log into two tabs: Security Activity and CRM Data Changes. Each tab has its own event type list and filters. A unified Actor filter replaces the old "Modified by" and "Source" fields. The log now clearly shows whether a human or an AI agent made each change.
Do I need to set anything up to use the new Audit Log?
No setup is required. The redesign rolls out automatically to all HubSpot accounts across all hubs and tiers. Any bookmarks or deep links you've saved will redirect to the correct new view automatically.
Who can see the HubSpot Audit Log?
The Audit Log is accessible to HubSpot admins. The redesigned version is available across all hubs and all tiers, including Free and Starter, so it's not gated behind a Pro or Enterprise plan.
What does the Actor filter do in the redesigned Audit Log?
The Actor filter is a single search field that replaces the old "Modified by" and "Source" filters. You can search for a specific person, an AI agent, an integration, or any other source to see all the changes that actor made within the selected tab and time range.
Why does the Audit Log now show whether a human or an agent made a change?
As HubSpot's Breeze AI agents take more autonomous actions inside the CRM, it's essential to know what was done by a human and what was done by an agent. This attribution supports data governance, compliance auditing, and responsible AI use. It also helps you debug unexpected changes faster.
How does the HubSpot Audit Log redesign affect RevOps workflows?
RevOps leaders can now audit CRM data changes without sifting through security events, and vice versa. The focused tabs and filters reduce investigation time and make it practical to review the Audit Log after every major workflow deployment or agent rollout, turning it from a last-resort tool into a routine governance check.
