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

Users, roles and organizations


Two operating modes

Single user (default). A single person, protected if necessary by a unique password. This is the mode of the desktop application.

Multi-user. Named accounts, roles, shared spaces, invitations, a usable event log. This is the setup required for an organization. It's part of the WivenLLM Business offer: without it, the server refuses activation and the screen prompts you to request a quote.

Toggle: Settings → Security → Security → Enable multi-user mode. Here you create the administrator account (username and password); existing conversations and threads are linked to it. This operation is irreversible from the interface—make a backup first.

License. When a Business license is installed (Wiven Console → License), it sets a number of seats: non-suspended accounts, excluding guests.


The roles

Role Can do
Administrator Everything: instance configuration, providers, users, agents, security, logs. Remains subject to walls and document-based permissions.
Administrator View, create, and delete all workspaces; configure these workspaces and manage their members; create, edit, and invite users (not administrators); view and export all instance conversations. No configuration of providers or security.
User Use the spaces he is a member of, manage his own conversations and personal settings
Guest Limited and temporary access to designated spaces, without a named account. No memories or Second Brain

Good practice: Limit the number of administrators. A Manager role is sufficient for most management needs, and it does not grant access to vendor keys or configuration. Its scope remains global: it sees all spaces and conversations on the instance, regardless of each user's organization.


Create accounts

Direct creation. Settings → Security → Users → Add a user: username, initial password, role.

Invitation. Settings → Security → Invitation generates a one-time link with workspaces that open immediately. The recipient chooses their password upon acceptance—the administrator never sees it. This is the preferred method. Links do not expire automatically: disable any that haven't been used.

Suspension. A suspended account can no longer log in, but its conversations and contributions remain. Prefer suspension to deletion when it's important to preserve history: deleting an account also erases its conversations.


Access to workspaces

In a multi-user environment, a user only sees the spaces of which they are a member, and those linked to an organization of which they are a member. The others do not exist for them.

Members are managed from the space settings, Members tab, or from Settings → Appearance → Workspaces for an overview.

Administrators and managers can see all spaces, except those blocked by a wall.

Walls

Wiven console → Walls. None are defined by default.

  • Exclusion : the people listed never have access to the listed spaces.
  • Conflict : a person only works for one area of the group, the one of which they are a member. Without belonging, or with several, the entire group is closed to them.

The walls apply to everyone, including administrators. Every refusal is logged in the audit trail. API keys, which operate for the instance and not for a person, are not subject to this.

Rights per document

Wiven Console → Per-Document Rights. A restricted document only reaches the listed users: no search, no pinning, no quoting, no listing, and no agent tools for others, including administrators. Widget visitors and Telegram users never receive it. API keys and scheduled tasks act on the instance and see all documents.


Organizations

An organization groups users and spaces under a single entity. It serves to open collective access and to carry common integration identifiers, for example for the services or subsidiaries of the same company.

What an organization stands for:

  • its members, with the role of Member or Administrator of the organization;
  • its linked workspaces, visible to all its members;
  • automatic membership rules by email address domain, applied to SSO connections whose address is verified;
  • The registration of their email and calendar applications (Outlook, Gmail, Google Calendar). Each member connects their own mailbox from «My connections», and the agent only uses the mailbox of the person requesting their assistance.

The Organization Administrator role manages the organization's members, domains, and applications. It can also link any space within the instance to its organization: only entrust this role to a trusted individual.

An organization does not isolate companies from each other. An instance has only one database, one storage directory, and one provider configuration. Administrators and managers see all spaces and conversations, regardless of the organization, and one API key is valid for the entire instance. To separate different customers or companies, deploy one instance per company.

Management in Settings → Security → Organizations (instance administrators).


Single Sign-On (SSO)

Rather than WivenLLM-specific passwords, users can log in with their company account.

Supported connectors: Google, Microsoft, Facebook, and any OpenID Connect-compliant provider. SAML and SCIM are not supported.

Set up : Settings → Security → Single Sign-On (SSO). You declare the provider, customer ID, and customer secret, and you save the callback URL displayed on the screen. A connector is enabled or disabled without being deleted.

Provisioning. A user logging in for the first time via SSO is automatically created with the User role; this initial role cannot be configured per connector. A verified email address identical to that of an existing account is associated with this account. Therefore, anyone the provider allows access obtains an account: for Microsoft, specify the tenant and restrict access using the Entra groups.

Good to know:

  • SSO connections and provisioning appear in the event log.
  • Keep at least one local administrator account: if the identity provider becomes unavailable, it's your only way in.

Enter groups and night synchronization

Wiven Console → Entra Groups, for a Microsoft or OIDC connector. The IT department decides in the directory who uses WivenLLM and with what rights:

  • groups allowed to connect, role, organizations, workspaces and messaging and calendar agents;
  • The rules apply to each connection and in both directions: what the groups no longer provide is removed. What no rule names is unaffected;
  • If the groups cannot be read, the connection is refused.

Night synchronization (Microsoft connector only, must be enabled). Every night, an account deleted or disabled in Entra, or removed from authorized groups, is suspended and its sessions are closed; the remaining accounts follow their groups. A manually suspended account is never reactivated. If a synchronization would suspend more than half of the verified accounts, it does not suspend anyone and reports this. Administrators are notified by email when Wiven Console → Outgoing Email is configured.

With a generic OIDC provider, the rules apply to the connection only: a departure only takes effect on the next connection, or by manual suspension.

Active Directory

Wiven Console → Active Directory. Employees log in with their Windows account. WivenLLM verifies the password with the domain controller (TLS only), creates the account on first login, and keeps its role updated according to the groups. Existing local accounts retain their passwords.

Two-factor authentication

Wiven Console → Two-factor authentication. A 6-digit code from an authenticator application, requested after the password, with ten backup codes. It is not required for any role by default: choose the relevant roles, or define them with WIVEN_MFA_REQUIRED_ROLES. Connections via Microsoft or Google rely on two-factor authentication from the provider.


Guest access

Allows access for people without an account, for limited use. Disabled by default, and only available in multi-user mode.

Settings in Settings → Security → Guest Access:

  • Enable guest access : a «Continue as guest» button appears on the login page;
  • Guest fields required, For example name,email (no address verification is done);
  • Guest session duration : 7 days by default;
  • Messages per guest per day : 20 by default, including agent turns;
  • Default guest workspaces.

Automatic limits. Five new sessions per hour per address, one hundred per hour for the entire instance. Behind a reverse proxy, configure the installation to recognize the real address of visitors; otherwise, they will all count as a single address. Upon expiration, the guest account, its conversations, and its threads are deleted.

Uses: a document assistant for visitors, internal support for employees without an account, a demonstration.

Precautions:

  • Only show guests spaces where all the content is broadcastable.
  • Agent skills are set for the entire instance, not by space or role: a guest who invokes @agent has access to those that are activated. Do not open guest access if a sensitive skill is active.
  • Each guest consumes the instance's model. The limits above govern the number of messages, not the cost.
  • Each guest session is logged, and its conversations can be viewed by administrators and managers until they are deleted.

For an assistant intended for a public website, the Web Widget is generally more suitable.


Transverse restrictions

Three settings govern usage independently of roles:

  • Limit messages per day (per account, in the user form): a number of messages per 24 hours, across all spaces. Administrators are exempt. There is no budget in tokens or money.
  • Hide central history (Installation setting): Removes central history access—workspace chat screen, export, widget conversations—and agent search in past conversations. Nothing is deleted, and users can still access their own threads.
  • Protect spaces against deletion (Installation setting): prohibits the deletion of workspaces, from the interface and via the API.

They combine with Content Control and Logs and Monitoring to build a usage policy.