Viewing & Reporting on User Usage

Modified on Fri, 15 May at 4:45 AM

Main Admins can view detailed usage reports to track individual and platform-wide user activity — from uploads and downloads to form submissions and asset views.

Overview

IntelligenceBank's usage reporting gives Main Admins visibility into how users are interacting with the platform. Reports are available both at the individual user level and across all users globally.

Usage data is useful for:

  • Tracking user adoption — understand how actively users are engaging with the platform.
  • Monitoring specific actions — verify whether users have completed tasks such as uploading assets, downloading files, or filling out forms.
  • Overall platform activity tracking — get a broad view of what is taking place across your organisation's IntelligenceBank environment.
Note: Usage reporting is typically only available to Main Admins of the IntelligenceBank platform.

Viewing an Individual User's Usage Report

To view usage data for a specific user, follow these steps:

1Go to Admin UsersNavigate to the Admin > Users section of the platform.
2Locate the UserFind the user you want to review in the user list.
3Open Usage ReportSelect the usage report icon on the right-hand side of the user's row. This will open the usage report for that individual user.

Understanding the Report Columns

The usage report displays the following columns:

ColumnDescription
ModuleThe overall area of the platform where the action took place (e.g., Asset Library, Databases).
ActionA general description of what the user did — for example, viewing a file, uploading or creating an asset, downloading, editing, filling out a form, or editing a form.
ItemThe specific item involved in the action. For assets, this is the asset name. For database records or forms, this is the name of the record or form.
SourceOnly populates when the action occurrs via an External API (for example, through an IntelligenceBank connector).
Date & TimeThe date and time the action was performed, as recorded by the system.
UserThe name of the individual user who performed the action.
Emulated ByIndicates whether the action was performed by the user directly, or by a Main Admin who was emulating that user. See the How to Emulate A User article for more detail on user emulation.

Filtering and Exporting Usage Data

Both the individual and global usage reports default to the last 30 days. You can refine the data using the following options:

Date RangeUpdate the date range at the top of the usage report to view activity across a custom time period.
Module FilterFilter by a specific area of the platform. For example, select Resource to see only asset library activity, or Database to view form and record interactions. Select Search to apply the filter.
Export Usage DataSelect Export Usage Data to download the current report view as an Excel document directly to your computer. Note that exports are limited to the first 100.000 rows of usage data.

Viewing Global Usage

To view usage across all users on the platform, navigate to Admin > Users and select the usage report icon at the top of the page (rather than next to a specific user). This gives you a bird's eye view of all activity taking place across your platform.

The global report is structured identically to the individual user report. The key difference is that it covers all users rather than a single person. Additional filtering options are available in the global view:

  • User Groups — filter to see activity from a specific group.
  • Divisions — filter by a specific division.
  • Specific Users — narrow the report to one or several individual users.
  • Module — filter by platform area, as with the individual report (e.g., Resource, Database).

The global usage report can also be exported to Excel by selecting Export Usage Data.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article