Everything one key can reach. Sample data: the refunds-legacy key, write access to the refunds API (issues refunds ≤ $500) and payments, read access to orders.
Installation
- 1
Set up the registry once
Your token in .env and @chartory in components.json. Skip this when another chart is already installed.
Installation guide - 2
Add the chart
One command adds the Reach tree component to your project.
npx shadcn add @chartory/reach-tree - 3
Use it
Pass your rows. The props are the Figma properties.
usage.tsximport { ReachTree } from "@/components/chartory/reach-tree"<ReachTree data={keyReach} size="m" legend/>
Props
<ReachTree>
Every prop but data is a Figma property with the same name and values.
ReachTreeData
The data prop: one object for the whole chart.
ReachTreeRoot
The root object.
ReachTreeScope
One object per entry in scopes.
ReachTreeSystem
One object per entry in scopes.systems.
The data as a JSON Schema: schemas/reach-tree.json
Reach tree: a React and Figma chart in four sizes
What does a reach tree show?
A reach tree starts from one key or account and branches to every system it can touch, marking write and read access with what each lets it do. Use it for API key reviews, service accounts and access audits.
Chartory ships it as a Figma component and a React component with the same name. The code installs from the shadcn registry with one command and lands in your project as a file you own.
What is the Reach tree component?
It is one <ReachTree> component. Its props are the Figma properties with the same names and values, and the props table above lists them. The data is a root, systems and access per link.
Sizes XS, S, M and L re-lay the chart out from the data instead of scaling it, so labels stay readable at every size.
When should I use it?
- Is it one key? Yes means the reach tree fits.
- Do access levels matter? Yes means the reach tree fits.
- Is it reach, not health? Yes means the reach tree fits.
When does another type fit better?
- Roles across actions. Use Permission matrix instead.
- A plain hierarchy. Use Tree instead.
- Healthy and failing links. Use Dependency map instead.
Reach tree questions
Installing, data, Figma and plans.
Yes. It installs through the shadcn registry with the shadcn CLI, and the file lands in your project.
Add your token and the @chartory registry once, then run npx shadcn add @chartory/reach-tree. The Installation guide has the steps.
Yes. Connect the Chartory MCP server and ask for the reach tree chart; the agent runs the same command and you review the diff.
A root, systems and access per link. The sample data comes with the component, and the props table lists every field.
XS, S, M and L, in Figma and in code. Each size is laid out again from the data, so text and lines keep their size.
Yes. chart/121-reach-tree has the same properties as the component.
Yes. Every paint is a token, so the chart follows light and dark mode and the collection you pick.
Code and Complete. Figma has the Figma file only.