This page is machine-translated from French. Read the French original.

Instance configuration

A server instance is partially configured at deployment, via a configuration file and environment variables. This complements the interface: most settings are configured within the application, and the configuration is used for automated deployment, structural parameters, and locking certain choices.

This page describes the settings categories and variables specific to Wiven. A complete list of variables is provided with the installation.


Mandatory secrets

Three secrets must be long, random, and unique to your installation: they sign sessions and encrypt secrets saved by the application. Never reuse example values.

  • Changing the session secret disconnects all users.
  • Changing signature secrets makes already encrypted secrets unreadable: SSO connectors, email and calendar tokens, two-factor authentication.

Storage

A single directory contains the database, documents, indexes, models, audit log, and security policies. This is the most critical setting during operation: it must point to a persistent volume, backed up with the configuration file. If the storage is not persistent, everything is lost upon reboot.


Network and service

  • The listening ports for the application and the document extraction service are configurable.
  • TLS can be enabled directly in the application, using your certificate and key. If a reverse proxy handles TLS, leave application-level TLS disabled.
  • Behind a reverse proxy, tell the application: otherwise, bandwidth limits do not see the real address of visitors.

Authentication

  • unique password In single-user mode. In multi-user mode, accounts are managed within the application and this password no longer has any effect.
  • Session duration : 30 days by default.
  • Password complexity rules : length, lowercase letters, uppercase letters, numbers, symbols.
  • Guest sessions : new sessions per hour, 5 per address and 100 for the default instance.
Variable Role
WIVEN_LICENSE The WivenLLM Business license itself, as an alternative to the file installed from the Wiven Console
WIVEN_MFA_REQUIRED_ROLES Roles for which two-factor authentication is mandatory. The screen can no longer change them.

AI Providers

Each provider is configured according to a consistent pattern: an API key or service address, a template preference, and sometimes a context boundary when it cannot be automatically discovered. Three choices designate the active selection: the language template provider, the embedding engine, and the vector base.

The language model configuration is saved only once in the database, on the first startup; thereafter, the value stored in the application is the determining factor. The embedding engine and the vector database remain defined by the configuration. Configure each setting only once.


Security and sovereignty

When they are filled in, the variables WIVEN_ The settings below lock: the corresponding screen on the Wiven Console can no longer change it.

Variable Role
WIVEN_EGRESS_MODE Sovereign mode: off, monitor (by default, logs without blocking) or strict
WIVEN_PII_SHIELD Personal Data Shield: off (by default), external Or always
WIVEN_GROUNDING Unsourced claims: off (by default), note Or verify
WIVEN_MODEL_APPROVAL enforce Requires approved templates. Disabled by default
AUDIT_RETENTION_MONTHS Month of audit log to be retained. Unlimited if not specified.
AUDIT_SYSLOG_URL Sending the audit log to a SIEM, via UDP or TCP

Operating options

Other installation settings allow you to:

  • remove the central consultation of the conversation history and its export;
  • prohibit the deletion of workspaces, both from the interface and via the API;
  • hide the interactive API documentation;
  • require a list of authorized domains for any web widget;
  • allow, or not, the import of pages and web reading from agents to internal addresses, and restrict these readings to a list of hosts;
  • set the maximum number of tool calls per agent response (10 by default) and the skills approved in advance — never sending, replying to or deleting messages;
  • set scheduled tasks: simultaneous executions (1 by default) and maximum duration (5 minutes by default);
  • choose the languages for character recognition (English by default);
  • set the resynchronization time for monitored documents (7 days by default);
  • Enable anonymous telemetry, which is disabled by default.

On a sovereignty-required installation, leave telemetry disabled and document it.


Best practices

Treat the configuration file like a secret. It contains all your keys. Restrict its access rights, do not version it, and back it up separately and in encrypted form.

Generate real secrets. A long random string, produced by a generator, for each of the three required values.

Check storage persistence Before commissioning: restart the instance and confirm that the settings and documents are still there.

Document your choices. Which supplier, which embeddings engine, which database: this information will be necessary for your processing register and for any subsequent intervention.