This page is machine-translated from French. Read the French original.
Journals and supervision
Event log
Settings → Security → Event Logs (administrator).
It records the structuring actions of the instance, along with their author and timestamp.
What is recorded
| Domain | Events |
|---|---|
| Authentication | Successful logins, failures, suspended accounts, SSO and Active Directory logins, automatic provisioning, two-factor authentication |
| Accounts | Creations, modifications, deletions, invitations issued and accepted, suspensions via directory synchronization |
| Workspaces | Creating, deleting, changing system prompts, adding and removing documents, resetting indexes |
| Documents | File imports, link imports, indexing |
| Conversations | Sent messages, duplicate threads, exports |
| Web widget | Creating, modifying, and deleting widgets |
| API | Creating and deleting keys, actions performed via the API |
| Configuration | Switching to multi-user mode, enabling beta features, clearing the log |
| Security | Policy changes (PII shield, sovereign mode, approved templates, walls, per-document rights), denial of access by a wall, license |
| Guest sessions | Logins |
The screen displays events page by page, without filters, and the log can be cleared in bulk. The clearing process itself is logged. It does not affect the audit log.
What it does not contain
The content of the messages and documents is not included. The log records that a message was sent, not what it said. For the content, you need to consult the conversation history.
Audit log
Wiven Console → Audit Log (Administrator).
Each event from the event log is also written here, outside the database. Each line is linked by SHA-256 to the previous one, and signed checkpoints fix the length of each file: the screen indicates whether the log is intact, and a modified or deleted line is visible.
- Filter and export. Per month, with a filter on the event, person or value; export CSV or JSONL.
- Conservation. No limit by default.
AUDIT_RETENTION_MONTHSThe app removes the overdue months, and this removal is itself recorded. The application offers no other way to delete an entry. - Sending to a SIEM.
AUDIT_SYSLOG_URL, via UDP or TCP.
To keep a copy out of reach of any machine administrator, send the log to an external system (SIEM).
Conversation History
Settings → Security → Workspace Chat (administrator or manager) provides an overview of all exchanges within the instance: space, author, date, content. Export is possible.
Legitimate uses: quality analysis, identification of documentation gaps, response to an access request, investigation of an incident.
Obligation of transparency. Users should be informed that their conversations are accessible to an administrator or manager.
An installation setting allows you to remove this screen and the export. It doesn't delete anything, and it doesn't prevent users from accessing their own threads.
There is no automatic purging for conversations or the event log.
Execution of planned tasks
Each task retains a history of its executions: date, duration, status, and detailed result. Scheduled tasks only exist in single-user mode.
Check regularly. A planned task can silently fail for weeks: it simply stops producing anything, and no one notices until the result is explicitly expected. → Planned tasks
System status
Several screens display the status of the instance:
- Facility health (Wiven Console) — the entire installation is checked at once: boot time and antivirus, speed and suitability of the local model, memory and disk, documents and indexes, links, administrators without two-factor authentication. Each point explains what it means and what to do.
- Hardware diagnostics — machine resources and suitability of local models.
- Vector base — number of indexed vectors, per workspace.
- Business agents — each person's availability status.
- MCP Servers — status of declared servers.
- Response check (Wiven console) — control questions replayed by space, regressions and history of results.
- Sovereign Mode (Wiven console) — network outages blocked and allowed, hosts contacted, signed report of the month.
- Update — installed version and availability of a new version, in the desktop application.
Things to monitor during operation
| Point | Frequency | For what |
|---|---|---|
| Facility health | Weekly | A single screen for startup, model, disk, and connections. |
| Execution of planned tasks | Weekly | A failed task is silent |
| Storage directory disk space | Monthly | Documents, indexes, and models are piling up |
| Backups | Continue, with restoration test | An untested backup is not a backup. |
| Authentication log | Monthly | Identifying repeated failures |
| Audit log | Monthly | Verify that it is intact and that sending to the SIEM is working |
| Active API keys | Quarterly | Revoke what is no longer useful |
| Active accounts | Quarterly | Suspend departures |
| Installed version | With each publication | Security patches |
Diagnosis of common incidents
| Symptom | To be checked |
|---|---|
| No further response | The template provider: expired key, quota reached, service unreachable. Sovereign mode in strict mode, if it blocks this host |
| A user is blocked after a few messages | His daily message limit, over 24 hours |
| Suddenly wrong answers | A recent change in model or search parameters |
| Documents not found | Indexing complete? Document added to the space? Similarity threshold? Embedding engine or vector database changed (documents must then be re-added)? Document restricted by document-specific rights? |
| General slowness | Machine resources; local model too large; very large corpus; antivirus at startup |
| An agent consistently fails | Skill activated? External service reachable? Agent model sufficiently capable? |
| A user does not see a space | He is not a member, or a wall blocks his access. |
