> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/models/work-in-the-app/editor/visualizations/context-map.md).

# Context Map

A Context Map is an interactive visualization that fans out from a single element across configurable levels of related data. Each level is color-coded, and the map loads its contents live from ServiceNow — so what you see is always the current state of your records.

Use a Context Map when you want to visualize:

* Everything that touches a business capability (applications, services, owners)
* A data flow expanded by hops
* Related records around a single source element, categorized by level

## Creating a Context Map

1. Add the **Context Map** visualization to your board from the shapes library.
2. Drop a **committed** element from the [Data Hub](/models/work-in-the-app/editor/data-hub.md) onto the Context Map shape — this sets the source element the map fans out from.
3. The **Configure Levels** dialog opens automatically.

<figure><img src="https://2110136944-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOS5XKTz5WlrX4s5rESlH%2Fuploads%2FFC6IMj396yt4PWzNOfTE%2Fcontext%20map.gif?alt=media&amp;token=7641a0ea-45a4-4ff5-a677-e755cef7f4ad" alt=""><figcaption></figcaption></figure>

## Configuring Levels

For each level in the dialog:

* **Table / Element** — pick the related table or specific element to include at this level.
* **Color** — pick a color for this level (the last level has no color picker; it uses its source color).

You can add and remove levels to control how deep the map fans out. **Level 1** is closest to the source; each subsequent level extends outward through related records.

Click **Load** to fetch the related records and populate the map.

## What You See After Loading

The Context Map renders as a radial or layered layout with the source element at the center and each level extending outward, color-coded per your configuration. You can:

* Select individual nodes to inspect them in the [Data Panel](/models/work-in-the-app/editor/data-inspector.md)
* Traverse relationships by hovering
* Add more levels by re-opening **Configure Levels** (pencil icon on the visualization's toolbar)

## Editing & Resetting

The Context Map toolbar includes:

* **Edit** (pencil icon) — re-opens the Configure Levels dialog
* **Reset** — clears the current configuration so you can start over

Both buttons are **hidden when the visualization is locked** or when the board is opened in read-only / presenter mode.

## Notifications

You'll see in-app toasts as the map loads:

* *"Loading Context Map"* (in progress)
* *"Context Map loaded successfully"*
* *"Error loading Context Map"* (with error details)

See [Notifications](/models/work-in-the-app/editor/notifications.md) for how these toasts behave.

## Limits & Gotchas

* **Only committed elements can be dropped on a Context Map.** Dropping an uncommitted element produces an error — commit the element first via the [Commit](/models/work-in-the-app/editor/commit.md) workflow.
* **You cannot drop multiple elements.** The error *"It is impossible to add multiple elements"* appears if you try — a Context Map has exactly one source.
* **Parent tables are not supported as a drop target** for a level. Drop individual tables instead.
* **The map loads asynchronously.** Expect a brief loading state for large related sets.
* **Configure Levels is modal.** You cannot edit the canvas while the dialog is open.

## Related

* [Data Hub](/models/work-in-the-app/editor/data-hub.md) — source of the committed element you drop onto the map
* [Hierarchy Map](/models/work-in-the-app/editor/visualizations/hierarchy-map.md) — a related visualization for parent/child trees
* [Commit](/models/work-in-the-app/editor/commit.md) — required before an element can be dropped on the Context Map


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ins-pi.com/models/work-in-the-app/editor/visualizations/context-map.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.