# Usage Analytics

Section to monitor Wilson's resource usage: How many users are there? How many questions are submitted? How much space does the Knowledge Base occupy?

<figure><img src="/files/o0GHuJxj2Rw9yYMElzDn" alt=""><figcaption></figcaption></figure>

Is possible to:&#x20;

* Check type and status of license
* Check active features (API, data scientist)
* Monitor the number of admins
* Monitor processed pages
* Monitor usage of questions

#### Per-user conversation history

\
Administrators can access the full conversation history for each user. This feature is particularly useful for:

* Understanding recurring issues or knowledge gaps
* Reviewing how the assistant supports field operations
* Verifying how information is being used in operational contexts
* All historical conversations are organized chronologically and can be filtered by date, topic, or keyword.

<figure><img src="/files/Jy67reWKelge8PIRdNO8" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
To access the converastion history you must enter a range of date
{% endhint %}

#### Audit log

A complete **Audit Logs** feature improve transparency and traceability across Wilson.

This new system tracks all key user actions and makes them easily accessible through a dedicated interface.

{% hint style="info" %}
Access requires the specific *Audit Logs permission*.
{% endhint %}

This tab provides:

* A searchable, filterable table of all logged actions
* Filters for date range, action type, and user
* Pagination and sorting options
* Clear metadata for each event (timestamp, action, user, notes, company)

<figure><img src="/files/J7hVwb3R3LD6aAGkZAS8" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
**Data Retention** Logs are **stored for 30 days** and automatically purged afterward.
{% endhint %}

Audit events are now automatically generated for all major operations, including:

* **Chat:** export, import to Knowledge Base
* **Knowledge Base:** upload, edit, delete documents; create/move/rename folders; manage Q\&A, tags, feedback
* **Bots:** create, edit configuration or filters, duplicate, archive, delete
* **Users & Permissions:** invite, delete, edit user info, role changes, permission changes
* **Groups:** create/edit/delete groups, update permissions, manage users
* **API Keys:** creation, deletion, update
* **Graphic Customization:** save new graphic

#### Quota management

The **Quota Management** feature allows you to define and enforce a maximum number of question that can be assigned within each cluster. This mechanism provides more precise control over available resources and prevents capacity‑related issues, in order to:

* Limit the maximum number of questions manageable per cluster.
* Provide immediate visibility into available and consumed quota.
* Enable alerts or blocking behavior when quota thresholds are reached or exceeded.

<figure><img src="/files/Ei1wnEFcPEnfqHkjATme" alt=""><figcaption></figcaption></figure>

By adding a new cluster you can define how much questions are available for this cluster.

<figure><img src="/files/6NHC4sQqxxdUyTxdhR1F" alt="" width="254"><figcaption></figcaption></figure>

<figure><img src="/files/HM9gfSNIYlgnsVZcZSHR" alt=""><figcaption></figcaption></figure>

Is it possible both to assign a single user to a cluster or import a group of users.

<figure><img src="/files/ocDiRuHWq8QoeFDwNEY6" alt="" width="254"><figcaption></figcaption></figure>

<figure><img src="/files/EqNSvSZNpsoDg1erVzaT" alt="" width="251"><figcaption></figcaption></figure>

This functionality ensures controlled usage of chat resources by enforcing a maximum number of questions per user session. It provides a clear counter of how many questions have been asked.

<figure><img src="/files/kxdlfWiITaiQDJrfRjr2" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="/files/CMjbH8ozoZbrRN3cocD3" alt="" width="375"><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://40factory.gitbook.io/wilson/3.10/wilson-academy/usage-analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.