Skip to main content
As your org grows past one app, the wiring between apps stops fitting in anyone’s head. Which app calls which? What reads the shared customer table? Is that cross-app grant you set up months ago still used? Answering these by reading code is slow, and the code only shows what’s allowed — not what’s actually happening. The System Map answers them at a glance. It’s a live, org-wide picture of your apps, your data stores, your connected services, and every connection between them — built from what the platform observes, not from a diagram someone has to keep up to date.
Find it in your org dashboard’s sidebar under System Map. It’s read-only — nothing here changes your apps; it reflects their current state.

​
What it shows

The map has two kinds of thing: nodes (the boxes) and edges (the lines between them).

​
Nodes

  • Apps — every app in your org. Apps published as Blueprints are marked as such.
  • Data stores — your org’s data stores, shared or per-app.
  • Integrations — connected services like LINE, Slack, and Google Calendar.

​
Edges

Each line is one kind of relationship, and the legend names them:
EdgeWhat it means
Observed callsReal cross-app traffic seen in the selected window — one app actually called another. The line carries how many calls, when the last one was, and the error rate.
Declared grantsA cross-app permission you granted — app A is allowed to call app B. Shown whether or not any traffic has flowed across it.
Data store accessAn app is connected to a data store, labelled with its access level (read, write, admin).
Integration grantsAn app is wired to a connected service.
The distinction between observed calls and declared grants is the useful part. A declared grant with no observed traffic is a permission nothing is using — a candidate to revoke. Observed traffic you didn’t expect is wiring worth understanding. Seeing both on one canvas is what makes the map an audit tool, not just a picture.
Hover any line for its details — call counts and last-seen time for observed calls, the allowed HTTP methods for a declared grant, the access level for data-store access.

​
Reading traffic over time

Observed-call edges are drawn from your apps’ real cross-app call logs. A time-window control switches the lens between 24h, 7 days, and 30 days — the map recounts calls, error rates, and last-seen within that window. A few things to keep in mind:
  • Thicker lines mean more calls. Line weight scales with call volume, so the busiest paths stand out.
  • Errors are highlighted. A call edge with a meaningful error rate is drawn in the destructive colour, so a failing integration is visible without opening logs.
  • Observed edges need traffic to appear. A brand-new grant with no calls yet shows only as a declared grant until the first call flows.

​
When to reach for it

  • Onboarding. Hand a new teammate the map instead of a walkthrough — they can see the whole system’s shape in one screen.
  • Before a change. About to modify an app’s endpoint? The map shows who calls it right now, so you know what you might break.
  • Auditing access. Find data-store connections and cross-app grants that exist but carry no traffic, and clean them up.
  • Debugging. A spike in a call edge’s error rate points you straight at the failing hop.

​
Next steps

Cross-App Communication

How apps call each other — the calls the map observes

Cross-App Permissions

Grant and revoke the permissions shown as declared grants

Data Stores

How apps connect to data stores

Connected Services

Wire LINE, Slack, and Google Calendar into your apps