# Organizing the Canvas (/docs/workflows/organizing-the-canvas)

> For the complete documentation index, see [llms.txt](https://docs.tandemcx.ai/llms.txt). Any page on this site can be fetched as Markdown by appending `.md` to its URL.

**Group** and **Note** are canvas-only nodes. Neither runs, nothing can route into either, and
neither has an exit. They exist to make a large flow readable: a Group draws a labelled box
around a set of nodes, and a Note leaves written text beside them.

## Group

A Group is a container, the same as a Loop Group or a Try / Catch Group, but it changes nothing
about execution. Drag one in from the Node Library and drag nodes inside it, or select two or
more nodes first and click **Group Selection** in the canvas toolbar to wrap a box around the
current selection in one step.

A Group's title is the node's own name, edited in the sidebar like any other node's name. Its
only other fields are a description, shown when the group is selected, and a cosmetic color.

Membership works like any other container: a node has at most one parent, so a Group's contents
are always exactly the nodes inside it. You cannot draw one box around a node that's inside a
Loop Group and a node that isn't — **Group Selection** refuses a selection that doesn't already
share one parent, and names the nodes to leave out. Moving the box moves everything inside it.
Groups nest, and count toward the same nesting limit as Loop Group and Try / Catch Group: 5
levels deep.

## Note

A Note displays markdown text on the canvas. Use one to explain why a branch exists, record a
decision, or leave instructions for whoever opens the flow next. Headings, lists, links, bold
text, and tables all render. Drag one in from the Node Library, resize it by dragging its corner,
and edit its text in the sidebar when it's selected.

A Note is always a leaf: nothing can be dropped inside it. It can sit inside a Group, in which
case it moves with the group.

## When to use which

Reach for a **Group** to name a region of the flow — a sequence of nodes a reader should
recognize as one unit. Reach for a **Note** to write something down that doesn't belong on any
single node: the reasoning behind a branch, a link to a ticket, a warning about an edge case.

## Next steps

<Cards>
    <Card
        title="Best Practices"
        href="/docs/workflows/best-practices"
        description="Keeping flows readable as they grow."
    />
    <Card
        title="Loops"
        href="/docs/workflows/loops"
        description="Loop Group nests the same way a Group does."
    />
    <Card
        title="Node Reference"
        href="/docs/workflows/reference"
        description="Fields and exits for every node."
    />
</Cards>