Back to Updates

Memory Administration and Conversation Exports

ibl.ai Engineering
Application

Administrators can now manage every user's memories and every agent's memories from one organization-level tab, including the switches that decide whether anything is captured at all — and every user can review and export their own conversations from their profile.

Memory on the platform now has an administrative view, and conversation history now has a user-facing one. The two shipped together because they answer the same question from opposite ends: who can see what the platform has retained, and who can take it back.

Managing anyone's memories

The organization's Memory settings on the Global tab, showing a user search above a table of users with Name, Username, and Email columns and a per-row view action

The organization's settings gained a Memory tab — "Manage user global memories and agent memories" for the whole workspace. It opens on Global, a searchable table of the organization's users.

The Global Memories popup for one user, showing the memory-capture and personalization toggles above that user's saved memories

Opening a user shows everything the platform remembers about them across all agents, and — above the list — the two switches that decide whether there is anything to remember at all:

  • "Allow AI to learn from our conversations" governs capture. Off means nothing new is recorded.
  • "Use my saved information in responses" governs use. Off leaves existing memories stored but stops them shaping replies.

Turning off capture alone leaves earlier memories in play, which is a distinction worth having: one suspends the effect, the other stops the accumulation.

Each memory carries its text, its date, and an edit-and-delete menu. Memories the platform captured automatically from chat show a robot icon and an auto badge, so a reviewer can always tell an inference from something a person entered deliberately. Both are equally editable here.

Managing what an agent has learned

The Memory settings on the Agent tab, showing an agent filter above a table of agents with Agent and Description columns

The Agent tab works the other way round — start from an agent and see what it has retained about the people who talk to it.

The Agent Memories popup, showing the user filter, date range, category tabs, and memory cards for a single agent

Opening an agent loads the same memory manager its own settings render: a user filter, a date range, category tabs — Knowledge Gaps, Learning Goals, Personal Context, Preferences, and any you add — a category manager, and one card per memory showing when it was recorded and whose it is.

There is one memory store behind all of this, reachable from three surfaces with different authority: a user's own profile, an agent's settings, and now the organization tab for someone with the standing to act on another person's behalf.

Your own conversations, and a way out

Profile History on the Conversations tab, showing agent, date-range, sentiment, and topic filters above a conversation list and a transcript preview

Every user now has a History page on their profile — "Review and export your conversations with AI agents." It gathers every chat with every agent into one filterable place: by agent, by date range, by sentiment, or by topic.

A selected conversation showing the alternating You and agent messages with a Download button above the transcript

Selecting a conversation opens the full transcript beside the list, formatting and both avatars intact, with a Download that saves that one conversation as a CSV built in the browser — no queue, no waiting.

The Exports tab, listing generated reports with status, creation time, the filters used, expiry, and a download action

For anything larger, Export generates a report of everything matching the current filters on the server, and it lands under the Exports tab with its status, the filters that produced it, and its expiry. Because each row records its own filters, a report downloaded weeks later can still be read for what it actually covers.

This page reads endpoints scoped to the signed-in account, so it shows a person their own conversations and nothing else — it is hidden entirely when someone else views their profile. Administrators reviewing a whole agent's conversations use the agent's own Chat History panel instead.

Documentation

Both surfaces ship in the ibl.ai SDK, so a product built on the platform can offer its own users the same review and export path.