This page is machine-translated from French. Read the French original.
Use Cases
The scenarios below describe typical implementations: what is installed, how it is organized, and what needs to be monitored. They can be combined.
Multiple roles, organizations, and access levels require multi-user mode, which is included in the WivenLLM Business license. The protections mentioned are disabled by default; each must be enabled and configured.
Trust and accounting expertise
The problem. Thousands of documents per client — invoices, statements, contracts, correspondence — and recurring questions whose answers are buried in a file.
The setup.
- Each client has their own workspace, which isolates their documents: a question asked in one workspace cannot access another client's documents. However, global memories, Second Brain, and the agent's conversation search function can be accessed across a single person's workspaces: disable these features if complete separation is required.
- Query mode activated, so that the assistant refuses to answer when no passage in the file corresponds to the question, rather than making things up.
- Prompt system specifying the applicable reference framework and the expected level of detail.
- Reference documents (internal accounting plan, procedures) pinned in each space.
- PII shield, if an external model is used: AVS, IBAN and IDE numbers, in particular, are replaced by pseudonyms before sending.
This is what it looks like. «What charges were recharged to customer X in Q3?», with extracts of supporting documents — verifiable with one click.
Something to keep an eye on. The Query mode reduces the number of false entries but does not eliminate them: the amounts must be cross-checked with the cited document. The citation provides the document title and excerpt, not the page number.
Law firm and legal services
The problem. Searching a document collection (standard contracts, case law, previous briefs) costs billable time, and confidentiality excludes online AI services.
The setup.
- Fully local installation — template, index and documents on the firm's infrastructure.
- Spaces by area (labor law, commercial contracts, litigation) or by case depending on the size of the firm.
- Roles and members of the space distinguishing associates, collaborators and administrative staff.
- Walls (Wiven Console) between conflicting mandates: they apply to everyone, including administrators.
- Content control to block the entry of identifiers or data that have no place in a conversation, according to the rules you define.
This is what it looks like. Comparison of clauses between several contracts, preparation of summary notes, research in previous reports.
Something to keep an eye on. All production intended for a client goes through human review: it is a preparation tool, not a final draft.
industrial SME
The problem. The technical documentation — plans, instructions, quality procedures, intervention histories — is scattered and known to only a few people.
The setup.
- A technical documentation area, a quality area, a support area.
- Import from internal wikis and existing repositories (Confluence, DrupalWiki, GitHub, GitLab, Gitea). Automatic resynchronization of monitored documents is an experimental feature; you can enable it.
- The agent's SQL skills are connected to the ERP database, if it's MySQL, PostgreSQL, or SQL Server, to cross-reference a document query with production data. Use a read-only database account: this ensures that nothing will be modified.
- Scheduled tasks producing a weekly summary of incidents, on a single-user instance: they are not available in multi-user mode.
This is what it looks like. A technician asks a question in natural language and obtains the procedure, with the document reference.
Something to keep an eye on. Obsolete documents perform just as well as others — document governance remains necessary.
Real estate agency
The problem. Mandates, leases, property condition reports and diagnostics are piling up, and the repetitive questions from visitors are consuming considerable time.
The setup.
- A portfolio space for assets, a legal space for deed templates.
- A web widget on the public website, connected to a space containing only publishable information, with a limit on the number of conversations per day. It requires a server instance accessible from the internet.
This is what it looks like. Answering common visitor questions without requiring staff time, and accelerating file preparation.
Something to keep an eye on. The widget is public: the space to which it is linked must only contain information that can be shared, and the list of authorized domains must be provided.
Public administration
The problem. Sovereignty and data protection requirements that exclude online services, and a significant regulatory volume.
The setup.
- Instance on internal infrastructure or national datacenter, with a local model and sovereign mode set to Strict, which blocks network outbound traffic not listed.
- Organizations to group services and their spaces, with single sign-on connected to the existing directory. Administrators and managers can see all spaces: put up barriers if this isn't suitable.
- Event log and audit log kept for traceability.
- Content is controlled according to internal policy.
This is what it looks like. Research in the regulatory corpus, assistance in drafting responses, summarization of files — without your data leaving the scope, as long as this configuration is respected.
Something to keep an eye on. The event log records structuring actions; the entity's specific archiving obligations must be checked separately.
A cross-cutting scenario: internal support
Applicable to all the above structures.
- A space fueled by internal procedures, HR FAQs, and memos.
- The web widget published on the intranet, or guest access for employees without an account. Guest access is disabled by default and, once enabled, opens a session for anyone who requests it, with a daily message limit (20 by default).
- The Response Control (Wiven Console), which replays control questions on the space and explains each failure, to identify documentary gaps.
Choose your starting configuration
| Priority | Recommended configuration |
|---|---|
| Absolute confidentiality | Local model + native embeddings + local vector base + strict sovereign mode |
| Maximum quality of responses | External supplier, selected and documented |
| Balance | Local model for everyday use, model router to a more powerful model for complex cases |
| Large volume of documentation | Enterprise vector database rather than local one |
| Many simultaneous users | Server deployment with a model server that responds in parallel, sized hardware, or an external vendor. The integrated local engine is sized for individual use or a pilot program. |
