The rollout of Activity Insights has generated mixed reactions across engineering teams. The concept of a drawing timeline with user attribution is valuable for coordination and traceability. The implementation, however, exposes architectural constraints that many CAD managers discover only after deployment.
This guide consolidates field experience, version differences, deployment strategy, and performance implications. It includes everything from enabling logging correctly to disabling the feature entirely when required.
What Activity Insights Actually Is
In modern releases of:
- AutoCAD 2024
- AutoCAD 2025
- AutoCAD 2026
Activity Insights replaces the legacy Drawing History (DWG History) palette. It records:
- Save events
- User identity (Autodesk ID–based)
- Drawing operations (PURGE, XREF attach/detach, etc.)
- Version data when used with supported cloud platforms
The system logs activity to small JSON files stored in a defined path. The palette reads these files to build the timeline.
Understanding this file-based model is essential for troubleshooting.
The Core Challenge: Why the Palette Is Empty
An empty palette usually results from one of four architectural issues.
1. Identity and Licensing
Activity Insights depends on Autodesk ID authentication.
Common causes:
- User not signed in
- Trial or NFR license behavior
- Expired sign-in session
If AutoCAD does not validate the user identity, logging may not trigger.
2. Local Log Path Fragmentation
By default, logs are written to:
C:\Users\{user}\AppData\Local\Autodesk\ActivityInsights\Common
Result:
- Each user sees only their own activity.
- No cross-user visibility.
- No collaborative value.
This is the most common deployment oversight.
3. Version Architecture Changes (2024 → 2025+)
The transition from 2024 to 2025 introduced a FileProvider-based architecture.
Practical consequences:
- SharePoint/OneDrive behavior changed.
- Version history may not appear in 2025/2026 even if it worked in 2024.
- The legacy DWG History model no longer applies.
Understanding version behavior is critical before rolling this out enterprise-wide.
4. Permissions and Security Policies
In enterprise environments, empty palettes often trace back to:
- Read-only shared folders
- NTFS permission inheritance conflicts
- Antivirus blocking creation of small JSON files
- Roaming profiles with restricted local app data
Activity Insights requires:
- Write permissions
- Low-latency file access
- No endpoint security interference
Without these, logging silently fails.
Version Comparison Summary
AutoCAD 2024
- Transitional behavior
- DWG History still present
- Limited cloud integration
AutoCAD 2025
- Fully shifted to Activity Insights
- FileProvider architecture
- Increased cloud dependency
AutoCAD 2026
- Further integration with cloud document services
- Stronger alignment with Autodesk Docs
Cloud vs Local Server Behavior
If using:
- Autodesk Docs
- BIM 360
Behavior changes significantly:
- Versioning handled natively
- Logging is cloud-coordinated
- Fewer performance issues from small local files
If using traditional file servers:
- Logging depends entirely on ACTIVITYINSIGHTSPATH
- Network latency directly affects save performance
- VPN connections often introduce visible delays
Making Activity Insights Work for a Team
Unified Logging Configuration
Command:
ACTIVITYINSIGHTSPATH
Set this to a shared UNC path:
\\Server\CAD_Standards\ActivityLogs
Avoid mapped drives (e.g., Z:). UNC paths are more reliable across user profiles and remote sessions.
Capacity Planning
Each save generates a small (~1 KB) JSON file.
In large deployments:
- 400 users
- Frequent saves
- 12 months retention
This can accumulate into millions of small files. Storage systems handle large files better than large quantities of small files. Plan accordingly.
AutoCAD LT Considerations
Users of AutoCAD LT may contribute to logging but not fully visualize history.
Ensure:
ACTIVITYINSIGHTSSUPPORT = 1
ACTIVITYINSIGHTSVIEWEDLOGGING = On
LT users must generate logs so full AutoCAD users can see activity.
Performance Impact and Latency
If AutoCAD freezes on QSAVE, check:
- Network speed
- Log path location
- VPN latency (>100 ms is problematic)
Activity Insights writes logs in real time. If the path is slow, AutoCAD waits.
Kill Switch
Disable support:
ACTIVITYINSIGHTSSUPPORT = 0
Module-Level Disable
Rename:
C:\Program Files\Autodesk\AutoCAD 20xx\AutoCAD Activity Insights
This prevents the module from loading entirely.
Use cautiously in managed environments.
Additional System Variables to Review
Depending on version:
- ACTIVITYINSIGHTSAUTOSYNC
- ACTIVITYINSIGHTSVIEWEDLOGGING
- ACTIVITYINSIGHTSSUPPORT
- ACTIVITYINSIGHTSPATH
Auto-sync settings may increase background file operations in shared environments.
Desktop Analytics and Telemetry
The timeline data comes from local/network files.
Separate from this is general Autodesk telemetry, governed by:
- Customer Involvement Program settings
- Desktop Analytics configuration tools
These do not control Activity Insights logging, but they often cause confusion during audits.
Known Architectural Limitations
These behaviors are inherent to the design:
- Not retroactive — only records events after activation
- Dependent on absolute file paths
- Copying DWGs to another server may break activity linkage
- Renaming outside supported cloud platforms disrupts tracking
- No built-in automatic purge
- Not optimized for high-latency VPN connections
- Large quantities of JSON files degrade server performance over time
Understanding these limitations prevents misaligned expectations.
Retention and Maintenance Strategy
There is no native purge function.
Recommended approaches:
- Scheduled batch deletion (files older than 30–60 days)
- IT-managed retention policy
- Storage tiering if logs must be preserved
Without maintenance, the log directory becomes cluttered.
When to Use It — and When Not To
Use Activity Insights if:
- You are on Autodesk Docs
- You require audit traceability
- You need user-level timeline accountability
Disable or localize it if:
- Performance is a higher priority than audit
- You operate over VPN
- Your environment is file-server based with limited IOPS
This feature was built with a cloud-first model. It performs best there.
FAQ
Does Activity Insights replace Drawing History?
Yes. In 2025 and newer versions, Activity Insights is the successor to DWG History. It combines versioning (cloud-dependent) with drawing event tracking.
Why does the palette say “Update Share Location” when it is already set?
Common causes:
- Insufficient folder permissions
- Mapped drive instead of UNC path
- Incorrect ACTIVITYINSIGHTSPATH configuration
Always test with a UNC path.
Is data sent to Autodesk servers?
The timeline events are generated from local or network JSON files in the defined log path.
General usage telemetry is governed separately by Desktop Analytics settings.
Can I control how long history is retained?
No native purge exists.
Retention must be managed externally via scripting or IT policy.
Will it work on drawings saved to my local Desktop?
Yes, but only you will see the activity unless the log path is shared.
Why does performance degrade over time?
Likely causes:
- Excessive small JSON files
- Network latency
- Antivirus scanning the log directory
- Fragmented storage volumes
What breaks activity tracking?
- Moving drawings outside supported cloud environments
- Changing file paths without preserving log references
- Copying files between servers
- Permission changes on the log directory
Final Assessment for CAD Managers
Activity Insights is technically sound but environment-sensitive. In controlled cloud deployments, it delivers meaningful audit capability. In traditional file-server environments, it introduces overhead that must be managed deliberately.
Deploy it intentionally. Monitor performance. Define retention. Or disable it cleanly.
Anything less leads to confusion and support tickets.
