We rely on hubspot standard objects for operation, including services and projects.
Currently, Audit Log functionality and detailed property history tracking exclude activity associated with the native Services CRM object. While standard CRM objects (Contacts, Companies, Deals, Tickets) and Custom Objects provide audit log visibility and restoration capabilities, the Services object lacks this essential coverage.
For businesses that rely on HubSpot’s native Services object for daily operations, this gap creates critical operational and compliance risks:
-
Extreme Audit Risk: There is no centralised audit record showing who created, updated, or deleted service records or modified specific property values.
-
Data Loss & Inability to Restore: Without object-level activity tracking in the audit logs or full property history, reverting unauthorised or accidental changes to service data is impossible at scale.
-
Incentive to Bypass Native Features: Custom Objects already include robust audit and tracking functionality. Because the native Services object lacks this functionality, we are forced to consider migrating our entire service framework over to a Custom Object simply to mitigate business risk.
I suggest that Hubspot:
-
Extend Audit Log Coverage: Include all CRM object creation, updates, and deletion activity for the Services object in the global HubSpot Audit Log.
-
Property Value Activity: Ensure full property-level change tracking and historical value logs are available for all native object records, matching the functionality of core and custom objects.
-
Restoration Capabilities: Allow admins to track and restore modified or deleted records directly for all object types
HubSpot’s native objects should offer equal or superior governance compared to Custom Objects. Adding Audit Log and history tracking to the Services object will prevent customers from having to rebuild native features using Custom Objects and will help enterprise teams meet strict compliance and auditing standards.