Catalog graph

The org catalog answers what is in this unit? as a table. The graph answers the neighbouring question: if I change this team, what moves?

Open Graph in the sidebar, or use the Graph button on any unit’s detail page. Arriving from a unit makes that unit the root; otherwise Camper opens on a top-level imported unit so the canvas is never blank.

Drag to pan; use zoom controls, wheel, or trackpad scroll.

Reading the graph

The drawing goes left to right:

Element	Meaning
Cards	An entity — org unit, linked resource, person, connection, or metadata value
Chips	A labelled relationship with a count (Slack Channel 2, People 41)

Cards show the one fact worth knowing at a glance: suggested, managed / attached, or n to fix when membership drifts. Names are links into the rest of the product.

Moving around

+ on a card expands one hop; − collapses
A chip toggles just that group (hide a long people list while you inspect resources)
Expand a level deeper opens every card that still has children
Show hides whole classes of card (untick People to focus on resources)
Root entries draws more than one unit; Catalog type picks the axis

If a card shows ⟳ instead of +, that entity already appears higher on the branch — the graph stops rather than looping.

What connects to what

From	Leads to
Org unit	Parent, units below, linked resources by type, metadata, people
Resource	Owning connection, every org unit linked to it
Person	Every org unit they sit on, across axes
Connection	Every linked resource on that connection

A resource linked from two units appears under both — how you find a Google group that a department and a team both drive.

Large groups

Very large fan-outs draw a slice at a time (first twelve, then Show n more). The chip always reports the real size. Above a few dozen members Camper may sample; open the unit itself for the full list. The header notes large groups sampled when this applies.

What the graph does not do