Licensed to be used in conjunction with basebox, only.
// admin
Exports
Overview
Getting data out of basebox: the audit log as CSV, usage data from the dashboard and users' chat backups. This page summarises which exports exist, what they contain, where they go – and which data protection obligations come with them.
What it is for
- Evidence for audits – internal audit, data protection review, certification.
- Analysis outside basebox – e.g. Excel evaluations of logins or failed actions.
- Forwarding to a SIEM – monitoring security-relevant events centrally.
- Cost control – tracing consumption per app and period.
Where to find exports
| Export | Location | Format |
|---|---|---|
| Audit log | Administration → Audit log → CSV export at the top right | CSV |
| Usage data | Administration → Dashboard (daily consumption, app usage, total consumption) | Display; no file export |
| Chat backups | By the users themselves | see Creating a chat backup |
| Original documents of a knowledge base | Via the download in an answer's citations | Original file |
Step by step
Export the audit log as CSV:
- Open Administration → Audit log.
- Set the filters: From date, To date, optionally Action (comma-separated, exact action names such as
graphql:deleteGroup), Resource type, Result (SUCCESS/FAILURE). - Click Apply filters – the export follows the current view.
- Click CSV export. The file is saved locally on your device.
The export itself is recorded in the audit log as action rest:exportAuditLogs – so you can see later who exported when.
What the CSV contains: per entry timestamp (to the millisecond), user identifier, action, resource type, resource ID, result and details. Audit events also include the client address. Whether conversation content is included depends on the configured detail level – see Policies.
Recording usage data:
The dashboard shows cost in euros and tokens per day (week / month / all), the app usage table with name, tokens, users and amount, and total consumption relative to the limit. Usage of the OpenAI-compatible API is reported separately from the web interface. To keep records outside basebox, note the values as of a reference date.
Notes
Exports are personal data
An audit CSV contains user identifiers, timestamps, client addresses and – depending on detail level – conversation content. Treat the file like any other document with personal data: store it encrypted, restrict access, delete it once its purpose is fulfilled. Agree retention and recipients with your data protection officer.
Note
- The export follows the filters. Without filters you export the whole view. Narrow the period to obtain manageable files.
- Retention period of the audit log is configurable. Anything older than the configured period can no longer be exported – export regularly if you need longer evidence.
- Web search queries are not in the log: organisation, user, tool, provider, result and timestamp are recorded, deliberately not the text of the query.
- SIEM integration: for continuous forwarding instead of manual exports see SIEM.
- Only administrators can export.
Frequently asked questions
Can I export the audit log automatically? The interface offers the manual CSV export. For forwarding to a SIEM see SIEM.
Does the export contain my users' chats? Only if the audit log's detail level is set to record questions or answers. In that case users see a notice in the chat.
Can I export individual chats? Users back up their own chats; administrators have no access to other people's conversations. See Creating a chat backup.
How do I export the documents of a knowledge base? Via the download in an expanded source of an answer you get the original document. There is no bulk export of an entire knowledge base in the interface.
Need help? Contact support