---
{
  "id": "platform.conversation.overview",
  "topic": "conversation",
  "title": "Conversation access and available actions",
  "locale": "en",
  "version": "2026-08-25",
  "summary": "Conversation actions inspect accessible chats, manage lifecycle and tags, export visible history, and manage Agent membership; creating a conversation remains a UI operation.",
  "content": "A conversation is the container in which users and Agents exchange messages. The live Conversation family covers discovery, member reads and confirmed member changes, history export, Office panel preferences, metadata update, delete, archive/unarchive, tag CRUD and assignment, and self-only Agent withdrawal. There is no live action to create a conversation: `create_conversation` remains deferred, so guide the user to the Arinova UI for that operation. `delete_conversation` requires UserConfirm with Strict drift; archive and unarchive do not.\n\nAn Agent can access a conversation when `conversations.agent_id` names that Agent or `conversation_members` contains its membership row. Outside those cases, runtime returns `resource_not_found`, not permission-denied; that result does not distinguish a missing resource from an inaccessible one.\n\nOne Agent may belong to many conversations, including multiple h2a chats. The current turn's conversation and an action's explicit `conversationId` are separate, so resolve or verify the intended target before reading it. `get_panel_preferences` reads the triggering user's selected `notebookId`, `boardId`, and `workbookId`; a binding is returned as null unless both the triggering user and executing Agent still have access, so it cannot substitute for a resource grant. `list_conversations` orders pinned items first and then by newest `updated_at`; each item includes a `url` deep link that can be given to the user. `export_conversation` writes JSON, text, or PDF history that the Agent is allowed to see into the triggering user's personal File Center; it does not return the full transcript in the action result. Field names, filters, limits, and result shapes remain registry/runtime truth.\n",
  "aliases": [
    "conversation",
    "find a chat",
    "conversation list",
    "chat members",
    "create a conversation",
    "conversation deep link"
  ],
  "tags": [
    "conversation",
    "overview",
    "access"
  ],
  "relatedActions": [
    "arinova.conversation.add_member",
    "arinova.conversation.export_conversation",
    "arinova.conversation.list_conversations",
    "arinova.conversation.get_conversation",
    "arinova.conversation.list_members",
    "arinova.conversation.remove_member",
    "arinova.conversation.get_panel_preferences"
  ],
  "relatedActionPrefixes": [
    "arinova.conversation."
  ],
  "url": "https://docs.arinova.ai/en/kb/conversation/overview/"
}
---

A conversation is the container in which users and Agents exchange messages. The live Conversation family covers discovery, member reads and confirmed member changes, history export, Office panel preferences, metadata update, delete, archive/unarchive, tag CRUD and assignment, and self-only Agent withdrawal. There is no live action to create a conversation: `create_conversation` remains deferred, so guide the user to the Arinova UI for that operation. `delete_conversation` requires UserConfirm with Strict drift; archive and unarchive do not.

An Agent can access a conversation when `conversations.agent_id` names that Agent or `conversation_members` contains its membership row. Outside those cases, runtime returns `resource_not_found`, not permission-denied; that result does not distinguish a missing resource from an inaccessible one.

One Agent may belong to many conversations, including multiple h2a chats. The current turn's conversation and an action's explicit `conversationId` are separate, so resolve or verify the intended target before reading it. `get_panel_preferences` reads the triggering user's selected `notebookId`, `boardId`, and `workbookId`; a binding is returned as null unless both the triggering user and executing Agent still have access, so it cannot substitute for a resource grant. `list_conversations` orders pinned items first and then by newest `updated_at`; each item includes a `url` deep link that can be given to the user. `export_conversation` writes JSON, text, or PDF history that the Agent is allowed to see into the triggering user's personal File Center; it does not return the full transcript in the action result. Field names, filters, limits, and result shapes remain registry/runtime truth.