Audit log¶
Requires the "Audit log" permission.
The Audit log is the log of events relevant to personal data protection: who exported data, who edited, imported or deleted contacts, who created or edited users, who changed the API keys, who unblocked a "Not authorized" contact, who anonymized contacts. You need it to answer questions such as "who edited this contact?" or "who exported that report?", and as documentation in case of GDPR checks.
You find it in the side menu, in the LOGS group, under Audit log. In addition to the permission, you need the Administrator role.
It is not a log of everything
The Audit log does not record every operation made in Thelgo, only the events listed in What is logged. In particular it does not record the mere viewing of data: opening a contact's page, looking at their personal data or scrolling through a report without exporting it leaves no trace here.
User logins and logouts are not in the Audit log: you find them in the Access report.
The screen¶
Each row of the list is an event, with date and time, user, entity, details, IP address and device. At the top right is the Download button.
Filters¶
| Filter | What it does |
|---|---|
| Period | Today (default), Yesterday, This week or Set date, which shows the From and To fields for a range of your choice |
| User | Only the events performed by one user. All users to see them all. Deleted users appear with "(deleted)", system users (such as Public API and VoiceAI) with "(system)" |
| Action | Only one type of event. All actions to see them all |
After setting the filters press Filter: the list does not update by itself.
At most 500 rows
Each search returns at most the 500 most recent rows that match the filters. If you are looking for an event in a very busy period, narrow the period or filter by user or action.
The Action menu offers all the types of event that are recorded (see the table further below).
Columns¶
| Column | Content |
|---|---|
| Date and time | When the event happened |
| User | Who performed it |
| Action | The type of event |
| Entity | What it concerns: the type of object followed by its identification number (for example "Nominativo #1234" (Contact #1234), "Utente #12" (User #12)). For report exports that go through Operations it is "Report #" followed by the operation number; for other exports it is the name of the exported file |
| Details | Additional information, when available (for example the roles and permissions changed, the number of rows exported) |
| IP address | Address the operation came from |
| Device | Browser and operating system used |
Text that is too long is truncated: hover over the cell to read it in full. Click the Date and time, User, Action or Entity headers to sort the list. On narrow screens each event is shown as a card.
Export the list¶
With Download you choose CSV or XLSX to download the displayed rows, in the current order. This export is also recorded in the Audit log.
What is logged¶
| Action | How it appears in the Action column | When it is logged |
|---|---|---|
| Export | Report exported | A user exports a report. For Access report, Operator report and for the Audit log itself: when they download the CSV or XLSX (format and number of rows in the details). For Call report, Campaign report and Predictive/Voice AI report: when they start the export (Entity "Report #n", Details "Report chiamate", "Report campagne" or "Report predictive" (Call report, Campaign report or Predictive report)) |
| Contact creation | Contact created | An administrator or an operator enters a new contact by hand (a creation through the public API also leaves this row, under the system user's name) |
| Contact edit | Contact edited | An administrator edits a contact, or an operator corrects its data while handling it |
| Contact deletion | Contact deleted | A contact is deleted |
| Import | Contacts imported | An import of contacts into a database ends. In the details: imported, discarded, errors |
| Database deletion | Contact database deleted | A database is deleted, with the number of contacts and campaigns deleted |
| Not authorized | Contact set to 'do not authorize' | An operator saves the Not authorized outcome |
| Anonymization | Contact anonymized, Contacts anonymized from list | An administrator anonymizes a contact from the detail (Entity "Nominativo #" (Contact #)), or finishes the anonymization from a list of numbers (in the details: contacts anonymized, not found, errors). No personal data in the details. At the moment these two actions have no translated text and are not in the Action filter: the technical code appears in the column |
| Unblock Not authorized | Contact unblocked from 'do not authorize' | An administrator presses Unblock "Not authorized" in the contact detail |
| Campaign deletion | Campaign deleted | A campaign is deleted. In the details: name and number of contacts removed |
| Campaign cleanup | Campaign cleaned up | A Clean up campaign ends. In the details: campaign name and number of contacts that became callable again |
| Database correction | Contacts corrected | A bulk correction of a database's contacts ends (see Correct database) |
| RPO extraction | RPO list extraction performed | You extract a campaign's list of numbers for the Opposition Register (see RPO) |
| RPO import | RPO list import performed | The import of the Register's response ends. In the details: contacts updated, not found, errors |
| RPO check | RPO check disabled for a campaign, RPO check re-enabled for a campaign | The bypass of the RPO check on a campaign is turned on or off |
| Outcome by administrator | Outcome set by administrator, Outcome removed by administrator | An administrator sets or removes a contact's outcome in a campaign from the contact search (see Campaign contacts). Entity "Nominativo #" (Contact #) |
| User creation | User created | A user is created. In the details: username and roles |
| User edit | User edited | An administrator edits a user (in the details: roles, permissions or status before and after), or a user updates their own profile or changes their own password |
| User deletion | User deleted | A user is deleted |
| Permission profiles | Permission profile created, Permission profile changed, Permission profile deleted | An administrator manages the permission profiles. Entity "ProfiloPermessi #". In the details: name, role and number of permissions when created; the permissions added and removed when changed; the number of users to whom the permissions were applied when deleted. The assignment of a profile to a user appears instead in the User edited row (in the details, the profile identifiers before and after) |
| Surveys | Survey created, Survey edited, Survey deleted, Survey scores recalculated, Survey answers changed after completion | An administrator manages the surveys (entity "Sondaggio #"; in the details of the recalculation, the points before and after). Survey answers changed after completion is recorded when an already completed survey is corrected from the contact card or from the working screen (entity "Nominativo #") |
| x-bees device revocation | User's x-bees devices revoked | A user's trusted x-bees devices are revoked |
| Forced disconnection | User forcibly disconnected | An administrator disconnects a user from Connected users |
| Appointment booked by the agent | Outcome set by agent | An agent books an appointment for a contact (from the New appointment popup): the contact automatically receives the Positive outcome. Entity "Appuntamento #" (Appointment #) |
| Appointment outcome | Appointment outcome set | An agent records an appointment's outcome (in the details: the outcome) |
| Appointment postponement | Appointment rescheduled | An agent postpones an appointment |
| Appointment outcome removal | Appointment outcome removed | An administrator removes an appointment's outcome from the Calendar |
| Appointment edit | Appointment edited | An administrator edits or reassigns an appointment from the Calendar (there are no details: open the appointment to see its current state) |
| API keys | API key created, API key revoked, API key reactivated, API key deleted | Management of keys in External API |
| Webhooks | Webhook created, Webhook revoked, Webhook reactivated, Webhook deleted | Management of webhooks in External API |
| Operations via API | Contact created (public API), Contact edited (public API), Outcome set (public API), Outcome edited (public API), Outcome deleted (public API) | An external system creates or edits contacts or outcomes through the public APIs. The details show the API key used |
Who appears as the user for the API
Operations made through the public APIs are logged under the system user Public API ("Public API (system)"): to know which integration performed them, look at the Details column, which shows the API key.
What is not logged¶
- The viewing of data (opening a contact, a report, the calendar) without editing or exporting it.
- The download of an export's file from the Operations page: the start of the export is logged, not every download.
- The deletion of an appointment from the Calendar and the creation of appointments (the edit/reassignment, the outcome removal and the agents' outcomes are logged).
Retention¶
Thelgo can delete every night the Audit log rows older than a certain number of days. This number is not set from the General settings: it is decided by whoever manages the platform, with a single value for all accounts. If the cleanup is active, under the page title you read "Rows older than N days are automatically deleted every night."; if you do not see this line, rows stay available with no expiry. If the user who performed the action is deleted, their rows remain, with "(deleted)" next to the name. For system users, that is the automatic actors who are not people (Public API, Appuntamento Agente, VoiceAI), "(system)" appears next to the name instead.
If your privacy policy requires keeping the log outside Thelgo as well, export the list periodically with Download, taking into account the limit of 500 rows per search and before any automatic cleanup kicks in.