> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognite.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Cognite Data Fusion (CDF) is an industrial DataOps platform. Prefer English docs unless the user asks for another locale.
> Follow /_llms/ index links recursively until you reach page URLs ending in .md. Fetch those Markdown twins instead of HTML.
> For REST APIs, default to calendar version 20230101 (stable). Use 20230101-beta or 20230101-alpha only if the user is on a preview API. Cite paths under /api-reference/concepts/<version>/ and the Cdf-Version header. Prefer the Python SDK (cognite-sdk) unless the user is in JavaScript/TypeScript.
> Start here by task: platform overview /cdf/index.md; data modeling /cdf/dm/index.md; data integration /cdf/integration/index.md; access /cdf/access/index.md; CDF Toolkit /cdf/deploy/cdf_toolkit/index.md; REST quickstart /dev/quickstart.md; Python SDK /dev/sdks/python/index.md; Atlas AI /cdf/atlas_ai/concepts/index.md; Flows apps /cdf/flows/index.md; Aura UI /cdf/aura/index.md; MCP and IDE setup /dev/guides/ide_ai_integration.md.
> For implementation work, also load /skill.md.

# Tree view

> A Tree view primitive displays hierarchical data in a nested structure. Each row in the Tree view can be expanded to reveal child elements or collapsed to hide them. Rows can also be selected, dragged, etc., depending on the primitive’s configuration.

<Badge color="orange">In progress</Badge> | *Storybook link coming soon*

## When to use

* When you need to show a large structure of items with multiple levels of nested information. This primitive is ideal for presenting complex relationships and hierarchies in a clear, navigable format. For example:
  * Folders, files and related items can use the Tree primitive to illustrate their structure and relationships.
  * The primitive can be used for geographic or organizational locations or sites.
  * When you need progressive disclosure and want to minimize initial UI clutter, Tree view hierarchies can be collapsed by default, allowing the user to expand and explore only what they need.

## When to use something else

* Flat lists without nested rows: use a simple list or [Data grid](/cdf/aura/primitives/data-grid) if you need columns.
* Tabular, sortable, many attributes per row: prefer [Data grid](/cdf/aura/primitives/data-grid).
* Non-hierarchical filters for the page: use [Tabs](/cdf/aura/primitives/tabs) (including vertical tabs) or [Segmented control](/cdf/aura/primitives/segmented-control).
* Location in site hierarchy: use [Breadcrumbs](/cdf/aura/primitives/breadcrumbs); primary app nav stays in the shell pattern.

## Behavior

* Expand/collapse per node; keyboard navigation should follow tree semantics (arrows, Home/End per implementation).
* Selection may be single or multi; drag-and-drop reorder is optional and must not break accessibility when enabled.

## Often used with

Row [Checkbox](/cdf/aura/primitives/checkbox), row [Menu](/cdf/aura/primitives/dropdown-menu), [Badge](/cdf/aura/primitives/badge) for type/status; drag handles when reorder is enabled; selection highlights paired with side detail or [Data grid](/cdf/aura/primitives/data-grid) elsewhere if used in split view.

*This document is maintained by the Aura team. For questions or to propose updates, post in `#topic-aura`.*