---
{
  "id": "platform.mindmap.overview",
  "topic": "mindmap",
  "title": "Mindmap forest and workflow overview",
  "locale": "en",
  "version": "2026-08-25",
  "summary": "Mindmap is a forest document with zero or more trees, node-level editing, outline-first batch workflows, and read projections.",
  "content": "A Mindmap is a forest containing zero or more trees. Every node has at most one parent; each node whose `parentId` is null is one tree root. Without `outline`, `create_mindmap` creates an initial node automatically and uses the Mindmap title as its label. That node may later be attached below another tree, promoted away, or deleted, and additional independent roots are valid. With `outline`, every top-level item becomes a root through the same atomic forest validation as `create_mindmap_from_outline`.\n\nChoose among four workflows. Node actions add, update, move, detach, attach, soft-delete, promote-delete, or restore branches and roots. Outline actions create a complete forest, attach a subtree, replace every tree, or read the forest as Markdown outline. Read actions list or fetch documents. Lifecycle, import, export, and sharing actions archive, unarchive, convert a supported File Center source into a new mindmap, save JSON/PDF to personal File Center, or mint/revoke a public link. For a conversation, meeting record, brainstorm, or other multi-node structure, prefer `create_mindmap_from_outline` or `add_subtree` instead of looping over `add_node`.\n\n`list_mindmaps` returns resources visible through owner or Agent grants and excludes archived maps unless `includeArchived` is true. `delete_mindmap`, `replace_outline`, `create_public_share`, and `revoke_public_share` require user confirmation; reversible `delete_node` and the other actions do not. The three `mindmap:read` Actions are available on public surfaces; mutations and `export_mindmap` are private-only.\n\nAction names, schemas, permissions, confirmation, public-surface policy, and deprecation come from the live registry. Current action results, persisted state, and typed errors override this reviewed guidance.\n",
  "aliases": [
    "mind map",
    "mindmap",
    "brainstorm",
    "outline",
    "tree of ideas",
    "branching diagram"
  ],
  "tags": [
    "mindmap",
    "overview",
    "forest"
  ],
  "relatedActions": [
    "arinova.mindmap.list_mindmaps",
    "arinova.mindmap.get_mindmap",
    "arinova.mindmap.create_mindmap",
    "arinova.mindmap.import_mindmap",
    "arinova.mindmap.add_node",
    "arinova.mindmap.update_node",
    "arinova.mindmap.move_node",
    "arinova.mindmap.delete_node",
    "arinova.mindmap.restore_node",
    "arinova.mindmap.create_mindmap_from_outline",
    "arinova.mindmap.get_mindmap_as_outline",
    "arinova.mindmap.add_subtree",
    "arinova.mindmap.replace_outline",
    "arinova.mindmap.archive_mindmap",
    "arinova.mindmap.unarchive_mindmap",
    "arinova.mindmap.export_mindmap",
    "arinova.mindmap.create_public_share",
    "arinova.mindmap.revoke_public_share"
  ],
  "relatedActionPrefixes": [],
  "url": "https://docs.arinova.ai/en/kb/mindmap/overview/"
}
---

A Mindmap is a forest containing zero or more trees. Every node has at most one parent; each node whose `parentId` is null is one tree root. Without `outline`, `create_mindmap` creates an initial node automatically and uses the Mindmap title as its label. That node may later be attached below another tree, promoted away, or deleted, and additional independent roots are valid. With `outline`, every top-level item becomes a root through the same atomic forest validation as `create_mindmap_from_outline`.

Choose among four workflows. Node actions add, update, move, detach, attach, soft-delete, promote-delete, or restore branches and roots. Outline actions create a complete forest, attach a subtree, replace every tree, or read the forest as Markdown outline. Read actions list or fetch documents. Lifecycle, import, export, and sharing actions archive, unarchive, convert a supported File Center source into a new mindmap, save JSON/PDF to personal File Center, or mint/revoke a public link. For a conversation, meeting record, brainstorm, or other multi-node structure, prefer `create_mindmap_from_outline` or `add_subtree` instead of looping over `add_node`.

`list_mindmaps` returns resources visible through owner or Agent grants and excludes archived maps unless `includeArchived` is true. `delete_mindmap`, `replace_outline`, `create_public_share`, and `revoke_public_share` require user confirmation; reversible `delete_node` and the other actions do not. The three `mindmap:read` Actions are available on public surfaces; mutations and `export_mindmap` are private-only.

Action names, schemas, permissions, confirmation, public-surface policy, and deprecation come from the live registry. Current action results, persisted state, and typed errors override this reviewed guidance.