# Project Activity Analytics and Usage Monitoring

**URL:** <https://community.qonic.com/t/project-activity-analytics-and-usage-monitoring/350>\
**Category:** Feature Requests\
**Created:** [September 18, 2026, 10:19am UTC](https://community.qonic.com/t/project-activity-analytics-and-usage-monitoring/350 "2026-09-18T10:19:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Johan\_De\_Cock](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.qonic.com/johan_de_cock/32/235_2.png) [@Johan\_De\_Cock](https://community.qonic.com/u/Johan_De_Cock)\
**Post date:** [September 18, 2026, 10:19am UTC](https://community.qonic.com/t/project-activity-analytics-and-usage-monitoring/350/1 "2026-09-18T10:19:34Z")

</div>

During recent discussions about license management, an important question emerged: “Can we track how actively a project is being used in Qonic?” This seems particularly relevant for future decisions around project archiving and deletion.

Currently, activity visibility is quite limited (at least in the interface), though I suspect log data exists somewhere in the system. Here are several analytics features that would be valuable:

**1. User Activity Tracking**

- When did a user last log in to a specific project?
- What is the login frequency per project?

_Use case:_ When promoting BIM adoption at the management level, it’s important to verify that teams are actively using the tools provided. If issues arise, management needs visibility into whether offered tools are actually being utilized.

**2. Project Activity Timeline**

- How does Qonic usage evolve over time for specific projects?
- Ideally, we’d see a bell curve pattern showing project lifecycle activity
- Distinguishing between “read” activities (consultation) vs. “write” activities (modifications) would help determine the optimal moment to change project status

_Use case:_ This would enable proactive portfolio management rather than reactive cleanup when license limits are exceeded. When activity drops off, it signals the right time to archive (and eventually delete post-delivery).

**3. Detailed Activity Logging**

- Complete activity log for specific users on a project/model, including all actions performed
- Similar to document tracking available in Bricsys 24/7

_Use case:_ This addresses potential disputes with external parties. For documents, it eliminates “I didn’t know document ABC was available” claims. For models, while opening a model doesn’t guarantee detailed review, we could at least verify whether someone opened a new model from a supplier or contractor when it became available.

Would these analytics capabilities be feasible to implement in a future release?