HubSpot audit log: where to see who changed what, and what it misses

Does HubSpot have an audit log, and where is it?

Yes. HubSpot has an account-level audit log, plus two narrower histories that answer most "who changed this?" questions faster: property history on each record and revision history on each workflow. Which one you open depends on what changed.

The account audit log is under the settings icon, then Account Management > Audit Logs. Only Super Admins can view and export it. What it covers depends on your subscription: HubSpot's help page lists logins, security activity and some CRM object activity on Starter, with more categories such as property updates, workflows and approvals on higher tiers, and some filters reserved for Enterprise.

If you only remember one thing: the audit log tells you who acted in HubSpot, property history tells you what a value used to be, and workflow revision history tells you how an automation changed.

How do I see who changed a property on a HubSpot record?

Open the record, click Actions at the top of the left sidebar and choose View property history. For a single property, hover over it and click the property history icon. The panel shows Changed to, Date and Source for each change, and you can filter by property, source or date.

The Source column is where most diagnosis happens. HubSpot labels each change with where it came from, for example:

• CRM UI: someone edited the value by hand.
• CRM Bulk Action: a bulk edit in HubSpot.
• Workflow: an automation set the value.
• Integration or Data Integration: a connected app or sync wrote it.
• Import: a file import.
• Forms: a form submission.

If lifecycle stages suddenly flip, a long run of "Workflow" or "Import" sources on the same day usually points you at the cause in minutes. For edits that came from the CRM UI, an import or a workflow, hover over the row and use Restore to put the old values back.

Two limits to know. History is capped by revision count, not by date: HubSpot keeps 45 revisions per contact property and 20 per company, deal, ticket or custom object property. And to look across many records at once, go to Settings > Properties, hover over the property, click More and choose Export property history; tick Include Source Information so the file shows which user or tool made each change.

How do I see who changed a HubSpot workflow?

Open the workflow under Automation > Workflows, then click View > Revision History at the top left. The right panel lists every change, newest first, with what changed, when and which user did it. This needs Professional or Enterprise and Super Admin or Workflows permissions.

You can filter by Date Range, Event (for example a changed enrollment trigger or timing setting) and User. Entries labelled "Unknown user" generally come from HubSpot itself, not from a teammate.

To see the workflow as it was, hover over a revision and click View; the read-only copy includes its settings at that moment. To go back, click Revert. Be careful with live workflows: if the workflow is on, the reverted version starts running immediately. HubSpot's advice is to turn it off, revert, check it, then turn it back on. Reverting is not supported for revisions with webhook or custom code actions, so use the read-only view as a reference and rebuild by hand.

Enrollment triggers are the edits to check first when a funnel number moves. A trigger that suddenly enrols a wider list, or stops enrolling a form's contacts, changes lead counts, scores and handoffs without any visible error.

What does the HubSpot audit log record, and what does it miss?

The audit log records actions taken by HubSpot users. HubSpot states that property updates not made by a user, such as form submissions, don't appear in it, and the default All Logs, Login History and Security Activity views show the last 30 days.

That makes it good for access and accountability questions (who exported contacts, who removed an admin, who deleted records) and weaker for performance questions. A few useful details from HubSpot's help page:

• Export report sends the current view or the full log by email.
• A security activity export covers the last year.
• Deleted records can be restored from the audit log within 90 days of deletion.
• Content activity is kept for 365 days on Content Hub Starter and Professional, with no limit on Enterprise.

What none of HubSpot's histories show is everything around the CRM: a new landing page, a changed Google Ads bid strategy, a GTM release that broke the form tag, a consent banner, a sales team rule agreed in a meeting. When MQLs drop, the cause is often outside HubSpot, and the audit log will look perfectly quiet. That is why a CRM history on its own rarely answers "why did leads drop?". The guide on explaining a conversion drop to a client covers the outside causes in more detail.

How do I isolate which change caused a CRM problem?

Start with the date the number moved, list every change from the days before it, inside and outside HubSpot, rule out tracking first, then test one hypothesis at a time. HubSpot's histories give you the CRM side; the rest has to come from your ad platforms, website releases and team notes.

1. Date the shift
2. Rule out tracking
3. Pull CRM histories
4. Add outside changes
5. Test one hypothesis

1. Date the shift. Find the first day the metric broke from its normal range, not the day someone noticed.
2. Rule out tracking. Check that forms still submit, the tracking code still loads and the counts in HubSpot match your ad platforms and analytics.
3. Pull the CRM histories. Filter workflow revision history and property history to the week before the shift; note every trigger, scoring and lifecycle change.
4. Add the outside changes. Ad edits, budget moves, landing page and form releases, tag publishes, new sales rules.
5. Test one hypothesis at a time. Revert or segment by the most likely change and watch whether the metric returns.

With every change on one timeline, the pattern is usually obvious: you would see the scoring workflow edited on Thursday and the form changed on Friday, both before Tuesday's drop, instead of reading four histories in four tabs. A marketing change log gives you that view; in Changeline Google Ads edits can be imported automatically and the team logs HubSpot, website and tracking changes next to them.

Example: a client asks why MQLs from the demo form fell by 40% on Tuesday. The agency lines up the changes from the previous week. Google Ads moved budget to Performance Max on Monday, but traffic to the demo page was stable. The form lost its phone field on Friday, yet submissions held. Workflow revision history then showed that on Thursday a teammate edited the lead scoring workflow's enrollment trigger, which left demo-form contacts out. Reverting the trigger brought MQLs back within two days.

How do I keep a change history that HubSpot doesn't keep?

Log every change that can move pipeline numbers in one shared place, at the moment you make it, with date, owner, reason and the expected effect. HubSpot's histories are capped by revision count, partly by plan and only cover HubSpot, so they work as evidence, not as your history.

A simple rule for CRM teams: if a change alters who enters a workflow, how leads are scored or routed, which fields a form asks for, or how a deal stage is defined, it gets logged. Write the reason too; "lowered MQL threshold from 60 to 50 to feed the new SDR" is far more useful in three months than "edited scoring".

Before each monthly review, export the property history for the properties your reports depend on (lifecycle stage, lead status, deal stage) so you keep a copy beyond the revision caps. The marketing change log template gives you columns to start with, and if lead volume is fine but quality fell, the post on why lead quality dropped walks through the causes.