> 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/command/the-portal/content-types.md).

# Content Types

Reference for every content type you can create in Command, with what each one is, when to use it and how to work with it.

Everything you create in the portal is a piece of content of a given type, such as a Table, a Roadmap or a SWOT. This page is the reference for every type: what it is, when to reach for it, and how to use it. Content reads live records, so it always shows your instance as it is now.

{% hint style="info" %}
**Your instance may differ.** The types available, their names, their categories and their order in the create menu are configuration. An administrator can rename a type, move it, reorder it or switch it off, and your [persona](https://docs.ins-pi.com/command/the-portal/personas.md) decides which ones you see. This page describes a default installation.
{% endhint %}

## At a glance

| Group                                | Types                                                                               | Use them to                                     |
| ------------------------------------ | ----------------------------------------------------------------------------------- | ----------------------------------------------- |
| [Answer & analyze](#answer--analyze) | Guided use-case, Dashboard, TIME Analysis, R-Analysis, Radar, Idea Assessment, SWOT | Answer a question about your portfolio.         |
| [Browse & edit](#browse--edit)       | Table, Form, Static List, Relationship Editor                                       | Work with records directly.                     |
| [Plan & compare](#plan--compare)     | Roadmap, Scenario, Scenario Comparison, Journey Map                                 | Lay out intent over time and compare options.   |
| [Map & visualize](#map--visualize)   | Hierarchy Map, Dependency Map, Orbit, Gravity Map, Models Board                     | Show structure, relationships and position.     |
| [Write & share](#write--share)       | Note, Advisory Report, Attachment, Hyperlink                                        | Keep and share the material around an analysis. |
| [Organize](#organize)                | Folder                                                                              | Organize My Space.                              |

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-8bb441ffd171cd8ad64cd12d0250b78514f8e0ef%2Fportal-create-menu.png?alt=media" alt="The create menu, grouped into categories, showing the Analyze types"><figcaption><p>The create menu names the persona it is showing and lists only the types that persona carries.</p></figcaption></figure>

## What every type shares

### Content reads live records

A piece of content stores what it points at and how to show it, not a copy of the data. Reopening it re-reads the records. Deleting content never deletes the records behind it, and the same record can appear in as many pieces of content as you need.

### Create content

1. Click **Create** (the **+**) at the top of the activity rail, or press **⌥N** (**Alt+N**). You can also use **Add** on a folder's **⋯** menu.
2. Type in **Search content** and press **Enter** for the best match, or browse the groups. Each type has a one-line description; a type you cannot use is shown grayed out with the reason.
3. Click the type. The new item appears in My Space with its name ready to edit, and opens in a tab.

You can also ask the [Command Dialog](https://docs.ins-pi.com/command/features/command-dialog.md), for example `create a hierarchy map`. Items the assistant creates are highlighted in My Space, not put into rename, so your next keystroke does not rename them.

New content is saved to My Space automatically.

### Add records

Most types are filled by dragging records from the [Data Hub](https://docs.ins-pi.com/command/the-portal/data-hub.md), or by dragging other content from [My Space](https://docs.ins-pi.com/command/the-portal/my-space.md). What arrives is a pointer to the record.

A record row's menu offers **Open record** (opens it as a [Form](#form)), **Edit relationships**, **Load dependencies**, **Add to…** and **Remove**. **Add to…** puts the record into other content without dragging: search for the place, or pick a recent one.

### Header, panels and downloads

Every item has the content header and, on most visual types, the **View**, **Metric** and **Timeline** panels. Both are described in [The Portal](https://docs.ins-pi.com/command/the-portal/portal.md#content-header).

Most visual types offer **Copy image** and PNG, JPG or PDF downloads from the arrow next to **Share**. Tables and lists also export to Excel and CSV.

***

## Answer & analyze

### Guided use-case

**What it is.** A guided workspace that walks you through an analysis step by step: choose the records, check their data quality, and see the results. Start from a ready-made use case, or click **Start from scratch** to pick your own tables, fields, scores and relationships.

**When to use it.** When you want an answer, not a blank canvas, for example which applications to rationalize.

**How to**

1. Create a **Guided use-case**. It opens as *Explore what's possible*.
2. Pick a use case from the catalog, or click **Start from scratch**.
3. Follow the steps. Your progress is kept, so you can leave and continue later.
4. Use **Copy summary** or **Download dashboard snapshot** to share the result, and **⋮ > Start over** to begin again.

See [Guided use-cases](https://docs.ins-pi.com/command/features/guided-use-cases.md) for every step.

### Dashboard

**What it is.** A page of live widgets: counts, totals, charts, measures, lists, content and your own work.

**When to use it.** For the figures you check regularly, or a page that answers one question for one audience.

See [Dashboards](https://docs.ins-pi.com/command/features/dashboards.md) for building, filtering and sharing a dashboard.

### TIME Analysis

**What it is.** The TIME quadrant. Each application is placed by **Business Fit** against **Technical Fit**:

| Quadrant      | Business fit | Technical fit |
| ------------- | ------------ | ------------- |
| **Invest**    | High         | High          |
| **Tolerate**  | Lower        | High          |
| **Migrate**   | High         | Lower         |
| **Eliminate** | Lower        | Lower         |

**When to use it.** To decide what to do with each application in a portfolio, on one consistent standard.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-e9e3e9d2646586ae6aa5ed5f759a1ff346162e9f%2Fcommand-content-time-analysis.png?alt=media" alt="A TIME Analysis plotting applications by business and technical fit into the Tolerate, Invest, Migrate and Eliminate quadrants, with the records table below."><figcaption><p>A TIME Analysis</p></figcaption></figure>

**How to**

1. Create a **TIME Analysis** and drag applications onto it.
2. In the table under the chart, check **Show on chart** for the records to plot, or click **Show all … on chart**.
3. Use **Size bubbles by** to size each bubble by a measure, such as cost.
4. Click a TIME category pill to filter to that quadrant. Where bubbles overlap, they are nudged apart with a thin line to their true position; bubbles that still overlap become one bubble with their count, which you click to fan them out.
5. Expand a row to see its **Score inputs**: each input, its value, weight and contribution. Try a change to see a live preview, then **Save** or **Discard**.
6. Click a bubble to decide what happens to that application: the drawer suggests the computed quadrant, and you choose **Tolerate**, **Invest**, **Migrate** or **Eliminate** with a reason. Decided bubbles wear a check mark. See [Decisions](https://docs.ins-pi.com/command/features/decisions.md).
7. Click **Send to governance** to put the proposed decisions to a governance body.

**Good to know**

* Records appear only once they have business and technical scores.
* A retired application keeps its position but is drawn as a hollow, dashed bubble, marked **Retired** in the table, and counted in no TIME category or total. You can still decide about it, with a reason.
* The **Metric** cards total every measure by its **Aggregate** setting (sum, average, count, lowest or highest), show how many records have data, and filter to those records when clicked.
* **⋮ > Clear** asks before it removes every record from the analysis. The records themselves stay in ServiceNow.
* A record whose position is fixed by a manual override says so.
* An administrator sets the inputs and weights in **Global Settings > Scoring**. See [Scoring](https://docs.ins-pi.com/command/features/scoring.md).

### R-Analysis

**What it is.** Application rationalization: each record is rated on every choice of an R framework, such as retain, replace or retire, and shown in one lane per choice.

| Framework              | Choices                                                  |
| ---------------------- | -------------------------------------------------------- |
| **Basic 4R** (default) | Retain, Remove, Replace, Replatform                      |
| **Standard 5R**        | Rehost, Refactor, Revise, Rebuild, Replace               |
| **Advanced 6R**        | Retire, Retain, Rehost, Replatform, Repurchase, Refactor |
| **Extended 7R**        | The 6R choices plus Relocate                             |

**When to use it.** To decide, record by record, which way each application should go, with the scores behind the suggestion.

**How to**

1. Create an **R-Analysis** and drag records onto it from the Data Hub or My Space.
2. Choose a **Framework**, and **Lanes** or **Matrix** under **Chart**.
3. Read each record's ratings in the table. Expand a row to see how each rating is made up.
4. Click a record, or **Decide…** in its row, choose a choice, give a **Reason**, and optionally a **Due** date and a **Successor**. Click **Record decision**. See [Decisions](https://docs.ins-pi.com/command/features/decisions.md).
5. Click **Send to governance** to put the proposed decisions to a governance body.

**Good to know**

* A missing score is left out, never counted as zero. A record with too little data shows under **Not enough data**, with no suggestion.
* When two choices rate within 6 points of each other, the record is a *close call*: a person decides.
* The ratings come from scores your administrator sets up in **Global Settings > Scoring**. With none, the chart says which scores are missing.
* An R-Analysis holds up to 500 records.

### Radar

**What it is.** A spider chart. Each axis is a measure, and each record is a shape across those axes.

**When to use it.** To compare several options or applications on the same set of criteria.

**How to**

1. Create a **Radar** and drag records onto it.
2. Pick the measures to profile in the **Metric** panel, which is on by default.
3. Use the **Timeline** to watch the shapes change between quarters, or click **Today** for the current values.

**Good to know.** A cost booked per period, such as OPEX, counts only in its own quarter; **Today** reads the current quarter so far. If no measures exist yet, the Radar says so. An administrator creates them in **Global Settings > Measures**. See [Measures](https://docs.ins-pi.com/command/features/measures.md).

### Idea Assessment

**What it is.** A scoring view for ideas from the [Ideation Portal](https://docs.ins-pi.com/command/features/ideation-portal.md), with a **Value vs Feasibility** quadrant and a comparison table.

**When to use it.** To decide which ideas to take forward.

**How to**

1. Create an **Idea Assessment** and filter by category and state.
2. Select an idea to see its scores.
3. Drag records from the Data Hub into **Impacted Enterprise Assets**.
4. Use **Add note** or **Request clarification** to discuss it, and **Approve** or **Reject** to decide.

### SWOT

**What it is.** A strengths, weaknesses, opportunities and threats matrix. Each quadrant holds cards of rich text, and records or content dropped onto a card become clickable chips.

**When to use it.** To frame a strategy discussion about an application, a capability or the whole portfolio.

**How to**

1. Create a **SWOT**, or ask the assistant `create a SWOT for <name>` for a drafted one.
2. Click **Edit**. Use **＋ Add Card** in a quadrant and type.
3. Drag records from the Data Hub, or content from My Space, onto a card to link them.
4. Drag cards to reorder them, or use **Remove card**.
5. Use **Columns** in the **View** row to show up to that many cards side by side. A quadrant too narrow for them shows fewer, so every record name stays readable.

**Good to know**

* A SWOT opens in view mode. Click **Edit** to change it.
* Each SWOT the assistant drafts gets a unique title. A repeated title gets the date, and a second one on the same day gets a number, for example "Enterprise SWOT Analysis · 8 Oct 2026 (2)".
* Ask `refresh this SWOT` to get an updated copy dated today.
* Point at a record chip on a card to see how trustworthy, fresh and complete that record's data is.
* **⋮ > Clear** asks before it removes every card.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-451f6605589052dae6fcb12146073a2c36d60a5a%2Fcommand-content-swot.png?alt=media" alt="A SWOT analysis in view mode with cards in all four quadrants and record chips on the cards."><figcaption><p>A SWOT with record chips on its cards</p></figcaption></figure>

***

## Browse & edit

### Table

**What it is.** A live table of records you can filter, sort and edit inline.

**When to use it.** For any list you work from: your applications, the capabilities in a domain, the records missing an owner.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-3edb7f367c0df64c9ff0969cb0b231fd87b17bd2%2Fcommand-content-table.png?alt=media" alt="A saved Table of AI agents with its State filter, column chooser, filters and record search."><figcaption><p>A Table</p></figcaption></figure>

**How to**

1. Create a **Table**. It says **This table is empty**.
2. Drag records from the Data Hub: rows, a filtered set or a whole table.
3. Use **Fields** to choose columns. The **Advanced** group adds columns that are not fields of the record:

   | Advanced column  | Shows                                                                                                                 |
   | ---------------- | --------------------------------------------------------------------------------------------------------------------- |
   | **Lifecycles**   | The current phase, phase start or end, or next milestone.                                                             |
   | **Measures**     | The latest value for a reference such as actual, planned or baseline. Add two columns to compare actual with planned. |
   | **Data Quality** | A data-quality score per governance scope.                                                                            |
   | **Scoring**      | A composed score.                                                                                                     |
4. Use the **Filters** funnel to build conditions, then **Apply**. Use **Search records** for a quick search. Conditions can use measures, such as cost over a value today, and lifecycles, with their scope and property.
5. Click a column header to sort.
6. Click a cell to edit it, if you have permission. The cell shows **Saving…** and then the saved value.
7. Use **State** to switch between current and future records, and **Show** to switch between a tree and a flat list when records nest.

**Good to know**

* A Table sorts and filters but does not group. Use a [Static List](#static-list) for **Group by**.
* Until you choose columns, a Table whose records come from several tables opens on the fields that say what each record is: its number, name or short description, and state.
* Advanced conditions combine freely, with one limit: when they read from different places, each but the largest must match at most 5,000 records. The filter says so when a combination is too large.
* While you drag records over a Table, a preview shows the rows the drop would add, and where.

### Form

**What it is.** A live editor for a single record. Saving writes straight back to the record in ServiceNow.

**When to use it.** To update a record's fields, lifecycle, measures or relationships in one place.

**How to**

1. Open any record with **Open record** from a row menu or the Data Hub, or create a **Form** and drag one record onto it.
2. Click **Edit** and change fields. The **Save** button shows how many changes are waiting.
3. Use **⋮ > Review N changes** to check and undo individual changes, then **Save all changes**.

**Good to know**

| Part of the form        | What you can do                                                                                                                                          |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Lifecycle** widget    | Add, move or remove phases and milestones.                                                                                                               |
| **Measures** grid       | Enter values by month, quarter or year, like a spreadsheet. The Form's **Save** saves them.                                                              |
| **Relationships**       | Edit the record's relationships. Records dropped here are added only while **Edit** is on; otherwise the card says "Turn on Edit to add relationships."  |
| **Data quality** card   | See the record's quality score and **Verify** fields due for review. See [Data Governance](https://docs.ins-pi.com/command/features/data-governance.md). |
| **Show N empty fields** | Reveal blank fields.                                                                                                                                     |
| **Draft**               | Draft a description from the record's properties and relationships.                                                                                      |
| **Decisions**           | See and record decisions about the record, such as retain or retire. See [Decisions](https://docs.ins-pi.com/command/features/decisions.md).             |
| **Extended view**       | On a section that holds a widget, such as **Lifecycle** or **Relationships**, show it full screen with the Data Hub beside it. Press **Esc** to leave.   |

To show a different record in a Form that already has one, drop the record on the Form's header, where it reads **Open in this form**. A drop anywhere else on the Form does not replace its record.

A Form is the one type with its own **Save** button, because it writes to the real record.

The form behaves like the ServiceNow form: your instance's client scripts and UI policies run, so fields can be set, cleared, hidden or given a message as you edit, and a script can stop a save with a message on the form.

**Edit** is unavailable, with the reason, when you cannot change the record. Editing lifecycle and measures needs the Command editor role.

### Static List

**What it is.** A fixed, hand-picked set of records. It does not re-query.

**When to use it.** When the membership is the point, for example "the 12 applications in the consolidation program."

**How to**

1. Create a **Static List**. Add records from the Data Hub, drag rows from another view, or add a TIME Analysis selection.
2. Use **Group by** (None or Table), **Sort** and **Search records**.

### Relationship Editor

**What it is.** A focused editor for one record's direct relationships, with upstream and downstream sides.

**When to use it.** To add, remove or retype a record's relationships in one reviewed batch.

**How to**

1. Create a **Relationship Editor** and drag one record onto it from the Data Hub.
2. Drag other records onto the **Upstream** or **Downstream** side to relate them.
3. Nothing is written yet. Click **Commit N**, review the additions, removals and changes, then click **Commit**.

See [Relationship Editor](https://docs.ins-pi.com/command/features/relationship-editor.md) for every task.

***

## Plan & compare

### Roadmap

**What it is.** A time-phased plan. Each record is a row, its lifecycle phases are drawn as bars colored by stage, and milestones are marked on it. The dates are read live from the records.

**When to use it.** To show when things happen: when an application retires, when its replacement goes live, when a project reaches each phase.

**How to**

1. Create a **Roadmap**. It says **Your roadmap is empty**.
2. Drag records onto it from the Data Hub.
3. In the **View** row, set the **Date range**, a **Window preset** and the **Axis** (from month up to decade). **From** must come before **To**.
4. Choose which **Lifecycle** drives the bars, and **Group by** table or by your own collections. Click **Add a collection** to create one.
5. To change dates, click **Edit**. Drag phase bars, or use a record's **⋮** menu for **Add phase…**, **Add scope…** or **Add milestone…**.
6. Click **Save** to write the new dates to ServiceNow. Scope added with **Add scope…** is also kept only when you save, and can be undone until then.

**Good to know**

* The axis labels every year in the range, including the first one.
* A phase name that does not fit its bar is shortened or hidden. Hover the bar to read it in full.
* A long record name is cut in the middle, so its end, such as a scope, stays readable. Hover it to read it in full.
* The footer and the **Legend** report what is shown. With **Show no-lifecycle records** off, the footer reads, for example, *4 of 6 records* and says how many decisions are hidden with them.
* Command stops phases from overlapping and tells you why.
* Milestones carry a status: Proposed, Approved, In progress, Completed or Canceled. Removing a milestone deletes it.
* The at-risk count in the header counts two things separately: records in a phase-out or obsolete phase, and records whose phases run past a retirement.
* **Load dependencies** lists the related records by name, so you can pick them one by one, and marks those already on the roadmap. A loaded record sits under the row it came from, with the relationship beside its name.
* A PDF download is a set of A4 landscape pages, cut between rows, with readable record names.
* **⋮ > Clear** asks before it removes every record.
* If your organization has an approval policy for lifecycle changes, a phase change waits for approval. See [Approvals](https://docs.ins-pi.com/command/the-portal/tasks-and-notifications.md#approvals).
* Measures appear through the **Metric** and **Timeline** panels. See [Lifecycle](https://docs.ins-pi.com/command/features/lifecycle.md) for phases and stages.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-9691bdb6ab52ad85452c50674c3beb23d1564e62%2Fcommand-content-roadmap.png?alt=media" alt="A Roadmap with records on a year axis, their lifecycle phase bars colored by stage, the today marker and the at-risk count in the header."><figcaption><p>A Roadmap with lifecycle phase bars colored by stage</p></figcaption></figure>

### Scenario

**What it is.** A what-if version of the future. You add records and mark each as **Added** (new in this scenario), **Modified** (kept but changed), **Removed** (decommissioned or excluded) or **Present** (shown for context). Nothing in a scenario changes the live records.

**When to use it.** To model an option before committing to it: a consolidation, a migration, a budget cut.

**How to**

1. Create a **Scenario** and drag records in from the Data Hub.
2. Set each record's membership state and its target date: a decommission date for removed records, an introduction date for added ones.
3. To try different numbers, type a value into a measure cell. Click **↺** to return to the baseline value. To type cost values in another currency, choose it in **What-if currency** first; each value is converted into its measure's currency when you enter it.
4. Use **Compare** to switch between **Baseline**, **Scenario** and **Scenario vs Baseline**.
5. Set the **Status** as the option matures: Draft, Under review, Approved, Active or Archived.

**Good to know**

* The overview band shows cost, benefit, risk and rating for the baseline against the scenario.
* The **Metric** panel is on by default.
* See [Scenarios](https://docs.ins-pi.com/command/prior-v26.0/features/scenarios.md) for scenario planning in depth.

### Scenario Comparison

**What it is.** Two or more scenarios side by side.

**When to use it.** When you have built several options and need to pick one.

**How to**

1. Create a **Scenario Comparison**. It says **Compare scenarios side by side**.
2. Click **Add scenario** and pick from **Scenarios in My Space**, or drag saved **Scenario** items onto it from My Space. Other content types are not accepted.
3. Read the rows: Cost (TCO), Risk, Benefit, Rating, Records, and the records unique to each scenario or shared.
4. Reorder, open or remove columns as needed.

**Good to know**

* The best value in each row is highlighted, and one scenario gets a **Recommended** badge.
* A scenario still in **Draft** must be set to **Active** before it is scored.
* An **Archived** scenario is read-only and is never **Recommended**.

### Journey Map

**What it is.** A canvas of stages across the top and rows down the side, for customer, employee or other journeys.

**When to use it.** To map an experience step by step and tie each step to real records and measures.

**How to**

1. Create a **Journey Map**. It asks you to **Choose a journey type**, such as Customer Journey, User Journey or Employee Journey.
2. Click **Edit**. Use **Add to the journey** to add a **Stage** or a **Section**, and **Add row** for new rows.
3. Choose what each row holds: bullets, quotes, sentiment, scores, a heatmap, records from the Data Hub, or a measure summed per stage.
4. To fill a **Data Hub records** row, drag records into one of its cells. The Data Hub's **Add** cannot choose a stage, so it tells you to drag instead.

**Good to know**

* Changes save automatically.
* A **Percentage Donut** shows its number and % together inside the ring. When you edit a donut cell, you can change or clear its caption beside the number; each cell keeps its own caption, saved with the map.
* Downloads always show the map as it looks outside Edit mode.

***

## Map & visualize

### Hierarchy Map

**What it is.** A map of records nested by their parent field and their relationships, such as capabilities and the applications under them, colored by top-level branch or by an Indicator.

**When to use it.** To show structure from live data, see what records depend on, and fix that structure by dragging.

**How to**

1. Create a **Hierarchy Map**. It says **Build a hierarchy map**.
2. Drag records, a Data Hub section, or a saved Scenario onto it.
3. In **Configuration**, which opens after the first drop, choose what loads around each table: **Load children**, **Relationships** and their types, and a filter. Click **Apply**.
4. In the **View** row, set **Layout**, **Color** and **Show**, or search the map.
5. Click **Edit**, drag a card under another, and choose **Move** or **Add**.
6. Click **Commit** to review the changes and save them.

**Good to know.** The map re-reads ServiceNow every time you open it or click **Refresh**. See [Hierarchy Map](https://docs.ins-pi.com/command/features/hierarchy-map.md) for every option.

### Dependency Map

**What it is.** A map of everything connected to one or more starting records, following CI relationships, many-to-many links and reference fields. It can simulate an outage or a retirement.

**When to use it.** Before you switch something off, migrate it or change it.

**How to**

1. Create a **Dependency Map** and drag in the starting records, or ask the assistant `what depends on <name>?`.
2. Increase the hop depth, or click a level label to load one more hop.
3. Set **Direction**: **Both directions**, **Downstream impact** or **Upstream providers**.
4. Choose which **Edges** to follow: CI relationships, M2M links, reference fields.
5. Set **Simulate** to **Outage** or **Retirement**. With the **Timeline** on, a retirement is shown in waves by quarter.
6. Use a node's **⋮ > Make center** to re-center the map.

**Good to know.** The **View**, **Metric** and **Timeline** panels all start off on this type.

### Orbit

**What it is.** A technology-radar view. Rings show a stage, sectors show a category, and each record is a blip placed by its data, not by hand.

**When to use it.** To publish a technology radar, or to see where a category of applications sits in its lifecycle.

**How to**

1. Create an **Orbit** and drag records onto it.
2. In the **View** row, set **Sectors** (a source table and field, grouped at the top level or as linked) and **Rings** (TIME disposition, Lifecycle or Score).
3. Optionally set **Size by** (uniform or a measure) and **Color by** (ring stage, sector, lifecycle or TIME).
4. Click a ring stage to hide it, or **Re-balance** to re-scatter the blips.

**Good to know**

* When ring stages are switched off or the **State** filter hides records, the chart says so and how many records are hidden. Click **Show all stages** to bring the stages back.
* Rings banded by a measure or score show their exact edges, and every value reads in full, such as *$2,500*.
* A cost booked per period, such as OPEX, places a record only in its own quarter on the **Timeline**. A record with nothing booked at that stop has no value there.
* **⋮ > Clear** asks before it removes every record. The records themselves stay in ServiceNow.

### Gravity Map

**What it is.** A canvas where records are bubbles pulled or pushed by **magnets**. Each magnet is a measure, and clusters emerge from the numbers.

**When to use it.** To see which applications group together on cost, value or risk in a way a table hides.

**How to**

1. Create a **Gravity Map** and drag records onto it.
2. In the **Metric** panel (on by default), select the measures to use as magnets.
3. For each magnet, set **Force** (**Pull**, **Push** or off) and **Target** (**High** or **Low**).
4. Or choose a **Preset**: **Invest** (pull KPI, push cost) or **Rationalize** (pull cost, push KPI). A preset sets **Force** and **Target** only; the magnets stay where you placed them.
5. Drag a magnet to move it. With the keyboard, pick a magnet with **\[** and **]** and move it with the arrow keys; **Enter** turns it on or off.
6. Click a record to see the forces acting on it. Each magnet's row says **Pulls** or **Pushes**.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-a1f9ac0bdaed66babea9daada1c9d324263cff2f%2Fcommand-content-gravity-map.png?alt=media" alt="A Gravity Map with numbered record bubbles drawn toward and away from measure magnets, a tip saying which magnets pull or push one record, and the records table below."><figcaption><p>A Gravity Map with pull and push magnets</p></figcaption></figure>

**Good to know**

* Every bubble shows its record's number, the same number as in the legend, the hover tip and the records table's **Chart number** column.
* The records table's **Strongest force** column says *Pulled to* or *Pushed away by* the measure that acts most on each record.
* The layout is saved once the bubbles settle, and **Position** shows where each bubble settled.
* The **Metric** cards total the values the bubbles show at the current **Timeline** stop, with each measure's **Aggregate** setting.
* PNG, JPG and PDF downloads carry the map's name as a title and leave out the magnet controls. CSV and Excel hold the plain numbers, with units in the column headers and an **On** or **Off** column per magnet.
* **⋮ > Clear** asks before it removes every record. The records themselves stay in ServiceNow.

### Models Board

**What it is.** A board from YouDesign Models shown inside Command. Available only where YouDesign Models is installed and you have access to it.

**How to**

1. Create a **Models Board** and click **Choose a board**.
2. Browse teamspaces and folders, select the board and click **Add board**.

**Good to know.** The picker closes only with **Cancel** or **Esc**, so a stray click outside it keeps your search and selection. If the board cannot be shown inside Command, click **Open in a new tab**. Dragging the board onto a Table, Roadmap, Hierarchy Map or similar type imports its shapes as records.

***

## Write & share

### Note

**What it is.** Free-form rich text. Records dragged into it become clickable chips.

**When to use it.** For meeting notes, decisions and context around an analysis.

**How to**

1. Create a **Note** and start typing.
2. Use the formatting bar for headings, lists and checklists.
3. Drag records or content into the text to link them.
4. Download as text or PDF. **Download text (.txt)** keeps one line per paragraph, heading and list item, with *\[x]* or *\[ ]* before each task.

**Good to know.** Deleting a record's chip removes the Note's link to that record. The assistant can save an executive summary as a Note: ask `executive summary for <name>` and accept the offer to save it.

### Advisory Report

**What it is.** A board-ready recommendation produced by the Command Dialog. Only the question and its evidence plan are saved, so every time you open the report it re-reads the data rather than showing a stale conclusion.

**When to use it.** When you need a recommendation you can defend, such as "should we retire this application?"

**How to**

1. Ask the assistant a recommendation question, for example `should we retire PayGate?`, or `create an advisory report for <name>`.
2. Read the verdict at the top: **Ready to decide**, **Needs approval** or **Not ready**.
3. Read **Why: the factors behind it**, heaviest first. Open a factor to see its reading, how reliable it is, its weight and its source.
4. Read **Data quality behind this call** to see how far the record's data can be relied on, with **Open record to review**.
5. Under **Decisions on** , record the decision, or use **Notify owner** to tell the record's owner or steward. **Decision on the record** at the top says whether the decision matches the recommendation.
6. Click **Re-run after fixes** after the data has been fixed.
7. Click **Download PDF** to share it outside Command.

**Good to know.** The report is advice: it changes nothing on the record. A question such as `shall we keep AssetMan?` opens a keep report. Plans accepted on older reports still show.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-d2eba544be81ead7b63c30cc37988273da1c3cee%2Fcommand-copilot-advisory-report.png?alt=media" alt="An Advisory Report with its verdict, the decision on the record, the factors behind the call and the data quality behind it."><figcaption><p>An Advisory Report for one record</p></figcaption></figure>

### Attachment

**What it is.** One uploaded file, held with the item.

**How to**

1. Create an **Attachment** and click **Choose file**, or drop a file on it. You can also drop a file directly onto My Space.
2. Use **Replace file** to swap it.

### Hyperlink

**What it is.** An external web address, shown embedded in Command or opened in a new browser tab.

**How to**

1. Create a **Hyperlink**, type the **Link URL**, choose **Opens in**, and click **Embed**.
2. To change the address later, use **⋮ > Edit link** in the item's header.

**Good to know.** Some sites refuse to be embedded. Command then offers **Open in new browser tab**.

***

## Organize

### Folder

**What it is.** Organizes My Space. Sharing a folder shares everything inside it.

**How to.** Click **Create** and choose **Folder** under **Organize**. It appears at the top of My Space with its name ready to edit.

To put one item in a second place without copying it, use **Add shortcut to Personal** on the item's **⋯** menu. See [My Space and sharing](https://docs.ins-pi.com/command/the-portal/my-space.md).

## Related

* [The Portal](https://docs.ins-pi.com/command/the-portal/portal.md) for the content header and panels.
* [Personas](https://docs.ins-pi.com/command/the-portal/personas.md) for which types appear in the create menu.
* [Data Hub](https://docs.ins-pi.com/command/the-portal/data-hub.md) for finding records to add.
* [Use cases](https://docs.ins-pi.com/command/getting-started/use-cases.md) for walkthroughs that combine several types.


---

# 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/command/the-portal/content-types.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.
