This page is machine-translated from French. Read the French original.
Clients and connections
Beyond the web interface, there are several ways to access your instance.
Desktop application
A native application for Windows 10/11, Red Hat 9 / Rocky 9, and NVIDIA DGX Spark (the macOS version is not yet available), which includes the entire platform. It operates independently, without a server, and is suitable for individual use. Its service is only accessible from the machine.
A «thin client» variant, which does not include the platform, connects to a server instance: you then retain the native interface while working on the organization's shared spaces. The standalone application does not connect to a server.
Mobile application
A mobile app connects to your instance to synchronize spaces, conversations and documents, and to chat on the go.
Pairing: The Connected Mobile Devices screen displays a QR code, valid for 3 minutes, which must be scanned from the application. The device must then be approved. Authorized devices are listed and can be revoked individually. This screen is reserved for administrators.
Your instance must be reachable from the network used by the device.
A user's daily message quota does not apply to the mobile application.
Browser extension
An extension allows you to feed WivenLLM without leaving the page being viewed: send text or the content of a page to your documents or into a workspace.
Connection: Settings → Appearance → Browser extension generates a key and its connection string, which must be entered into the extension. Established connections are listed and can be revoked. Reserved for administrators and managers.
Telegram
A Telegram channel allows you to communicate with a workspace from within the messaging system. It only exists in single-user mode: Switching to multi-user mode stops the robot and deletes its configuration.
Set up : Create a bot with @BotFather, then enter its token and default space in the Telegram Bot screen.
Access control: Access is not open to anyone who knows the bot. Access requests are subject to approval, and each authorization can be revoked. Approvals, denials, and revocations are logged. People who write to the bot are warned that they are communicating with an AI and do not see documents reserved for named individuals. When an agent requests approval, it appears as buttons in Telegram.
Telegram is a third-party service. Messages pass through its infrastructure. On a sovereignty-required installation, this channel must not be open to sensitive areas.
Application connections
Some agent skills require access to your professional applications: email, calendar, directory.
Outlook, Gmail, and Google Calendar connect personally. On an instance with multiple organizations, each member connects their own accounts via their profile menu., My connections. The agent only uses the inbox of the person asking the question, never that of a colleague or another organization. An account that is not a member of any organization does not have access to these skills. In single-user mode, login is done in Settings → Agent → Agent Skills.
- Outlook: An administrator prepares the integration once, then everyone clicks on «Sign in with Microsoft». The connection is read-only, unless an administrator ticks «Also allow drafts and sending emails»; then you have to log in again.
- Gmail and Google Calendar: Each person publishes a Google Apps Script to their own account, then enters their deployment ID and key.
If your company manages access through directory groups, these groups can remove a member's email or calendar access, or leave them with drafts without sending.
Microsoft Teams is configured only once by an administrator, for the entire instance, with a Microsoft Entra application registration.
What is available depending on the deployment
| Workstation | Server / hosted | |
| Web interface | ✓ (local) | ✓ |
| Desktop application | ✓ | ✓ (thin client) |
| Mobile application | — | ✓ |
| Browser extension | ✓ (on the machine) | ✓ |
| Telegram | ✓ | Single-user mode only |
| Web widget | — | ✓ |
| API developer | ✓ (on the machine) | ✓ |
| Planned tasks | ✓ | Single-user mode only |
| Business agents | ✓ | — |
