Maps within maps (modules)

A “module” node stands for another one of your maps: it shows its aggregated status and, if you want, its inner nodes, without leaving the current map.

The typical use: a “root” map with one module per project, customer or environment. It needs several maps, included in the pro plan: the free plan has just one. At a glance you see the state of everything; you open a project’s map only when needed.

How to create one

1. Press + Add (bottom right) and choose Module.
2. The “Add a module” panel opens, listing your other maps (not the current one, not the demos). On the free plan you have a single map, so the list is empty: multiple maps are included in the pro plan.
3. Press Add next to the map you want to link. The node takes the map’s name and keeps a reference to it.

A module has no check, reach or provider, and doesn’t use your plan’s nodes. You can only link maps you’re a member of. The demo is read-only and can’t create modules.

The module card

• “Module” type, aggregated status, name, linked map name and node count.
• An expand/collapse button shows or hides the inner nodes.
• The aggregated status is the worst of the inner nodes, in this order: offline, unknown, degraded, online, tracked. An empty map is tracked.
• Modules nested inside the linked map are excluded from the calculation: aggregation is one level deep.

Expanded: inner nodes and edges

Expanding the module shows, below the card, a box with the inner nodes in compact form and the edges between them. It is read-only and shows live data: the checks stay in the source map.

• You can connect a node of the current map directly to an inner node of the expanded module: drag from the connector onto the inner node.
• An edge from one inner node to another inner node of the same module is not saved.
• If the inner node is later deleted in the source map, the edge becomes “orphaned”: it is not drawn and the card shows “N broken link(s): remove”.

The module inspector

It only has Label and Group, the Open map button and Remove node. “Open map” switches to the linked map; there is no breadcrumb or “back”: to return, use the map switcher in the top bar.

Unavailable map

If the linked map was deleted or is no longer accessible, the card shows “unavailable · map deleted or no access” and the offline status.

Loops and depth

If map B already contains A, then in A’s picker B is disabled (“would create a loop”). Depth is checked up to 8 levels. The check is client-side only.

Via MCP and manifest

• add_node rejects the module type: a module is created from the app or with import_manifest, using kind: module and moduleRef: { wsId }.
• add_edge accepts fromInner and toInner to point at an inner node of a module.

Nodes · Import / export · Guide: maps within maps