Skip to content
Sign inOpen LouvainBook a demo

Changelog

What’s new in Louvain

What changed in hosted Louvain, newest first. Each entry describes what you will notice; the documentation has the detail.

28 September 2026

New

  • A document that mentions prompt injection is no longer held back. A file in a space or a connected store that only talks about the subject is read, searched and cited as usual, and its details say it mentions prompt injection. Text that tries to instruct an AI is still held, and so is a message or email with the same words. Uploaded files (opens in a new tab).
  • Release a file Louvain set aside. A file whose text reads like instructions to an AI is held back from search and answers, and a document that only discusses the subject can be held too. An admin of the space can now choose Release… on the file; the confirmation says why it was held, and Louvain then reads it like the rest of the space. Uploaded files (opens in a new tab).

Fixed

  • A document held back as a possible prompt injection no longer shows in Search. Louvain quarantines a record whose text reads like instructions to an AI, and never reads it; Search still listed such a record with an excerpt, and then couldn't open it. It is now absent from Search, lists and the viewer, the same as everywhere else. How memory works (opens in a new tab).

27 September 2026

New

  • All files, in one view (preview). A Unified view switch at the top of Spaces shows every file you can open, whichever source holds it: what changed most recently, what was shared with you, and a search by file name with a count per source. A Google Drive file you can reach through more than one connection is one row showing each source. Folders stay in their own source, and nobody sees anything they couldn't already open there. It is off until you turn it on. All files, in one view (opens in a new tab).

Fixed

  • Connecting an agent when you weren't signed in. After signing in, the approval page could say the agent had sent an incomplete request, because the request was lost on the way through sign-in. It now comes back whole. Connecting an agent (opens in a new tab).

26 September 2026

New

  • An agent can confirm who approved it, if it asks. An agent may ask for your Louvain id in the workspace (its short name and the part of your email address before the @) and, separately, your sign-in email address. The approval screen then says so ("Know it's you", "See your email address"). Neither reaches anything, and neither is granted unless asked for. ChatGPT, for example, uses them to let a company allow only accounts on its own domain. Connecting an agent (opens in a new tab).

Improved

  • A support page. louvain.ai/support says how to reach us, where to check whether the service is up, and where to report a security issue. The footer's Support link opens it.
  • The privacy policy says exactly who sees a question's words. Administrators see how answering is going across the workspace (counts, refusal reasons, response times and feedback). The words of a question are shown only to the person who asked it, whether it was asked on the Ask page, through the API or by an agent. The policy previously said administrators could see the words of questions asked through the API and agent tools, which was never how Louvain behaved. Privacy Policy, Connecting an agent (opens in a new tab).

25 September 2026

New

  • Upload files works like a shared drive. Spaces are folders in a rail, with shared spaces first and your own under Just you. Making a space is now three short steps: name it, choose who can read it, review. A shared space has a Share button that opens the same who-can-read step. Uploaded files (opens in a new tab).

  • Meeting notetakers, in preview. Fireflies, Gong, Zoom, Fathom, Granola, Otter and tl;dv can be connected from Connections. Their summaries, action items and speaker-by-speaker transcripts become searchable and citable. Each meeting is readable by whoever that tool lets see it, never simply whoever was invited. They are marked coming soon until each has been checked against a live account. Meetings and notetakers (opens in a new tab).

  • Teams meeting transcripts. An Outlook Calendar app registration can also read the transcripts of Teams meetings the listed people organised. By default only organisers and co-organisers can read them, and invitees can be turned on. Microsoft 365 (opens in a new tab).

  • Connect with your own key. For a tool that gives each person their own API key, you can connect it for yourself by pasting your key. It is checked with the tool before it is saved, never shown again, and what it imports is readable only by you. Connecting with your own key (opens in a new tab).

  • Groups from your company sign-in. If Google Workspace, Okta or Microsoft Entra ID sends a groups attribute when people sign in, those groups can now be picked as who reads an upload space, labelled with where they came from. This gives Okta workspaces groups for the first time. A change at your provider takes effect at each person's next sign-in. Sending groups at sign-in (opens in a new tab).

Improved

  • Company mail is read only for people in Louvain. A selected mailbox is fetched and read only once its owner, or one of their Gmail delegates, is a member of the workspace. Mailboxes nobody here can read no longer use up your allowance. When someone joins, their mailbox is read from the start of its history window. Company calendars and drives work the same way: each selected person is read only once they're a member. Company mailboxes (opens in a new tab).
  • What was said in a meeting counts as what was said. A recorded meeting is now read in full, and each commitment or decision is attributed to the person who said it, not to the organiser. When someone in a meeting you were in asks you for something, or promises you something, it can open a row on your plate, quoted from their own words. Your plate (opens in a new tab).
  • Answers check dates written without a year. "Last time (19 September)…" is now checked against the date the source gives, as a full date always was. Asking (opens in a new tab).
  • An answer cannot swap one company for another with a similar name. When a question names a company, a sentence about it must come from a source about that company. Previously a source about a similarly named company could slip through. Asking (opens in a new tab).
  • Your own key must be yours. Where a tool can say whose API key it is (Fireflies, Otter), Louvain now refuses a key that belongs to someone else. Connecting with your own key (opens in a new tab).
  • Meeting briefs remember the last meeting. A brief for an upcoming meeting now reads up to three recorded earlier meetings you can read: the same recurring series first, then the same people, then the same company. Meeting briefs (opens in a new tab).
  • Zoom and Gong can be connected by signing in. An administrator can sign in instead of creating an app or an API key. A Zoom sign-in brings meeting summaries; transcripts still need a Server-to-Server app. Structured sources (opens in a new tab).
  • A Google Calendar meeting names its transcript. When Google Meet attaches a transcript or Gemini notes to an event, the event now names them. The files themselves arrive through Google Drive, readable by whoever the file is shared with.
  • Google groups are visible to whoever Google shows them to. A group only its members can see, Google's default, used to be hidden from everyone in Louvain, including its own members. Now its members can see it and pick it as who reads a space, and nobody else learns it exists. Sharing with directory groups (opens in a new tab).
  • A members-only Google group shows its name. Such a group could appear in the picker under Google's internal id instead of its name. It now shows its name, and groups already listed under an id are renamed.
  • Groups appear only when there are groups. When sharing a space, the Groups option shows once your directory or company sign-in has sent some, instead of a picker that says "No groups yet".

Fixed

  • Company Google Workspace now includes your directory. One setup creates mailboxes, calendars, drives and the Google Workspace Directory, so your groups stay in sync and can be picked as who reads a space. If you set up Company Google Workspace before today, add Google Workspace Directory once from Connections.
  • Groups and directory offboarding now work with the hosted Google setup. A Google Directory connected through the company Google Workspace setup was not recognised as a directory, so its groups never appeared and its suspensions removed nobody.
  • The group picker has its padding back.

24 September 2026

New

  • Your directory can remove people who leave. Turn on Remove people your directory suspends under Settings → Single sign-on → Policy. When Google Directory, Okta or Microsoft Entra ID suspends someone, the next sync removes them from the workspace and signs them out everywhere at once, instead of their session running on for up to a week. It is off by default. Each directory connection removes at most five people, or a tenth of the workspace, in a day; anything past that waits for you in the audit log. Removing someone at your identity provider (opens in a new tab).

  • Share an upload space with directory groups. An upload space can now be shared with groups from Google Directory or Microsoft Entra ID, such as Finance or Engineering. Someone who joins or leaves the group in your directory gains or loses access after the next sync. Sharing with directory groups (opens in a new tab).

  • Single sign-on with Okta and Microsoft Entra ID. The single sign-on setup now starts by asking which identity provider your company uses. Okta and Entra get the same guided steps as Google Workspace, in their own consoles' words, and take the metadata URL each publishes instead of a file. Single sign-on (opens in a new tab).

  • Single sign-on with Google Workspace. On the Business plan, an admin sets up SAML single sign-on themselves under Settings → Single sign-on. The setup walks through each step in Google Admin, tests it by signing the admin in before anything is turned on, and can then require it for your domains. People at your verified domains join the workspace the first time they sign in. The Louvain tile in Google's app launcher signs them straight in, and if your company mail is connected they can read their own mailbox with no second Google step. Single sign-on (opens in a new tab).

  • Confirm it's you, in place. Actions that need a recent sign-in, such as changing ownership or setting up single sign-on, now ask you to confirm it's you in a small window and then carry on. You no longer sign out and back in.

23 September 2026

Improved

  • Plate, on the site. The home page now shows Plate: the asks, promises and dates your sources put on you, closed by the message that settles them. How Plate works (opens in a new tab).
  • Microsoft 365, Dropbox and Box are listed as available. Outlook mail and calendars, OneDrive, SharePoint, Teams, Dropbox and Box are on the integrations page with how each connects; their files are read, not just named.
  • Pricing says what each plan includes. Business is described by its larger monthly allowance, the trial's 90-day history and smaller allowance are stated, and what happens when a workspace reaches its allowance is described as it works.
  • Legal pages updated. After a subscription ends its data is kept for 30 days, so it can be exported or reactivated, and then deleted; the Acceptable Use Policy describes the monthly allowance; Subprocessors lists TypeSafe for the optional entity classifier, which is off unless an administrator turns it on.

15 September 2026

Fixed

  • A limit never keeps a removed person reading. When a workspace had used its monthly events, or its plan had lapsed, Louvain refused a source's permission changes and deletions along with new content — so someone removed from a channel, or a message deleted at the source, stayed readable until the month reset. Permission changes and deletions are now always accepted and never counted toward the monthly events; only new content waits for the limit. Limits (opens in a new tab) has the detail.

14 September 2026

New

  • Terms, privacy and data processing, published. The Terms of Service, Privacy Policy, Data Processing Addendum, Subprocessors, Acceptable Use Policy and Cookie Notice are now on the site, and every page links to them.
  • A status page. Status shows whether the service is up and ready, live from the service itself, with any incident notes.
  • Connect an agent by pasting one address. Claude, ChatGPT, Cursor and VS Code can add Louvain as a remote MCP server and ask your company memory questions with your own permissions. Find it under Connections → Agents.
  • Eighteen structured sources. Linear, Jira, GitHub, Notion, Confluence, HubSpot, Salesforce, Pipedrive, Attio, Zendesk, Intercom, BambooHR, HiBob, Rippling, Workday, Okta, Microsoft Entra ID and Google Workspace Directory connect with an admin key or a sign-in. Their records arrive as facts with their own history, so you can ask what was true at a date.
  • Files are read, not just named. PDFs, Word, Excel, PowerPoint, OpenDocument and text files from Google Drive and Gmail attachments can be searched, cited and answered from.
  • Deleted at the source, deleted here. When a connected source reports that an item was deleted, Louvain removes it from search, answers, facts and the keyword index. The connections documentation (opens in a new tab) says which sources report deletions.
  • Remove a connection with everything it imported. Removing a connection now revokes everything it granted at once, and Also delete everything it imported removes the data too, with progress shown while it runs.

Improved

  • Removing someone ends everything at once. Removing a member ends their sessions, API tokens, agent connections and personal connections together. Administrators can see and end members’ agent connections under People, and can turn agent connections off for the whole workspace.
  • The integrations page shows what works today. Sources you can connect on hosted Louvain are listed with how they connect and who can read them; connectors that are not available yet are marked as coming soon.
  • Clearer security page. It describes the controls that exist, where your data is processed, and what is not in place yet.
  • Choose who can read a workspace connection. Admins can share a connection with everyone, with chosen people, or — for sources that report it — with whoever has access at the source.

Changed

  • Third-party calendar loads only when you ask. If the demo page falls back to HubSpot’s scheduling widget, it now waits for you to choose to load it.