> 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](/command/the-portal/personas.md) decides which ones you see. This page describes a default installation.
{% endhint %}

## At a glance

| Category                      | Types                                                           | Use them to                                       |
| ----------------------------- | --------------------------------------------------------------- | ------------------------------------------------- |
| [Plan](#plan)                 | Roadmap, Scenario, Scenario Comparison, Journey Map, Use Case   | Lay out intent over time and compare options.     |
| [Analyze](#analyze)           | TIME Analysis, Radar, Orbit, SWOT, Gravity Map, Idea Assessment | Position records against each other.              |
| [Visualize](#visualize)       | Dashboard, Hierarchy Map, Dependency Map                        | Show structure, relationships and standing views. |
| [Record views](#record-views) | Table, Static List, Form, Relationship Editor                   | Work with records directly.                       |
| [Content](#content)           | Note, Attachment, Hyperlink, Models Board                       | Keep the material around an analysis.             |
| [Inventory](#inventory)       | Advisory Report, Folder, Shortcut                               | Organise My Space and keep generated answers.     |

<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. You can also use **Add content** in the My Space header, or **Add** on a folder's **⋯** menu.
2. Type in **Search content**, or browse the categories.
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](/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](/command/the-portal/data-hub.md), or by dragging other content from [My Space](/command/the-portal/my-space.md). What arrives is a pointer to the record.

A record row's menu offers **Edit** (opens it as a [Form](#form)), **Edit relationships**, **Load dependencies** and **Remove**.

### 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](/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.

***

## Plan

### Roadmap

**What it is.** A time-phased plan. Each record is a row, its lifecycle phases are drawn as bars coloured 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).
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 changes** to write the new dates to ServiceNow.

**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.
* Command stops phases from overlapping and tells you why.
* Milestones carry a status: Proposed, Approved, In progress, Completed or Cancelled.
* If your organisation has an approval policy for lifecycle changes, a phase change waits for approval. See [Approvals](/command/the-portal/tasks-and-notifications.md#approvals).
* Measures appear through the **Metric** and **Timeline** panels. See [Lifecycle](/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 coloured by stage, the today marker and the at-risk count in the header."><figcaption><p>A Roadmap with lifecycle phase bars coloured 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.
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](/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. 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.

### 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.

**Good to know.** Changes save automatically.

### Use Case

**What it is.** A landing page that frames a piece of analysis. It lists the data requirements and business inputs the analysis needs and offers **Open guided canvas**, which continues in the Command Dialog.

**When to use it.** When your organisation has published use cases for you to start from.

**How to**

1. Create or open a **Use Case**.
2. Click **Open guided canvas**. The assistant walks you through choosing sources, fields and scope before anything runs.

{% hint style="warning" %}
The catalogue behind the guided canvas is empty in this release, so a new Use Case has no guided steps yet. The button is also disabled when the assistant is switched off.
{% endhint %}

***

## Analyze

### 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, tick **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.
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**.

**Good to know**

* Records appear only once they have business and technical scores.
* 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](/command/features/scoring.md).

### 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 periods.

**Good to know.** If no measures exist yet, the Radar says so. An administrator creates them in **Global Settings > Measures**. See [Measures](/command/features/measures.md).

### 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.

### 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 cards side by side.

**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.

<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>

### 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).
5. Click a record to see the forces acting on it.

### Idea Assessment

**What it is.** A scoring view for ideas from the [Ideation Portal](/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.

***

## Visualize

### Dashboard

**What it is.** A grid of widgets you assemble. Only the layout and settings are stored; every widget loads live data each time the dashboard opens.

**When to use it.** For a standing view that leadership or a team checks regularly.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-086d90291bebe9a8fe8db714b9ecf98808e6a3a7%2Fcommand-content-dashboard.png?alt=media" alt="A saved Dashboard with a KPI tile, donut breakdowns and a records widget for business applications."><figcaption><p>A Dashboard of business applications</p></figcaption></figure>

**How to**

1. Create a **Dashboard**. It says **Design your board**. Click **Add your first widget**.
2. Click **Edit**, then **Add widget**. Search, or browse the **KPIs**, **Charts**, **Measures**, **Records** and **Content** tabs.
3. Drag a widget by its header to move it, and drag its corner to resize it. With the keyboard, arrow keys move, Shift plus arrow keys resize, Enter opens **Configure widget**, and Delete removes.
4. Click **Configure widget** to set it up, then **Save widget**.
5. Select a widget to change its look in the **Widget formatting** panel: border, header, logo, title and caption colours, alignment, and for a Button its preset, style, shape, size, shadow, icon and colours.
6. To take back a removal, click **Undo** on the message that appears.

You can also drag content from My Space onto the canvas, where it becomes a **My Space content** widget, or records from the Data Hub, which become **Record measures** widgets. A dropped widget lands where you drop it.

On a phone, or in a narrow panel, the widgets stack in one column. You can still rename, configure and remove them there; moving and resizing need the wider grid.

| Widget                                  | Shows                                                       | You set                                                                                                                                                                                                               |
| --------------------------------------- | ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **KPI tile**                            | A count of records                                          | Source table, filter, caption                                                                                                                                                                                         |
| **Score tile**                          | One record's score                                          | Score, record                                                                                                                                                                                                         |
| **Score summary**                       | A score across a population                                 | Score, population table                                                                                                                                                                                               |
| **Data quality**                        | Complete, Correct and Current percentages                   | Governed table, scope (picked from the table's scopes)                                                                                                                                                                |
| **Lifecycle summary**                   | Records by lifecycle phase                                  | Population table, lifecycle (picked by name)                                                                                                                                                                          |
| **Measure gauge**                       | A measure's latest quarter, against a target if you set one | Records to add up, measure, values, target                                                                                                                                                                            |
| **Measure trend**                       | A measure by quarter, actual and planned                    | Records to add up, measure, values                                                                                                                                                                                    |
| **Record measures**                     | One record's measures                                       | Record (or drop one from the Data Hub)                                                                                                                                                                                |
| **Bar breakdown** / **Donut breakdown** | Records grouped by a field                                  | Group-by field, number of groups (3 to 12; a donut shows up to 6 slices)                                                                                                                                              |
| **Records table**                       | A list of records                                           | Source, rows to show                                                                                                                                                                                                  |
| **My Space content**                    | Any saved item, live or as a compact summary                | The item                                                                                                                                                                                                              |
| **Text**                                | Rich text                                                   | Headings, body, lists, colour                                                                                                                                                                                         |
| **Image**                               | An uploaded image                                           | The file, contain or cover                                                                                                                                                                                            |
| **iFrame**                              | An external web page                                        | An http or https address                                                                                                                                                                                              |
| **HTML**                                | Your own markup, style and script                           | Up to 8,000 characters. It runs in a sandboxed frame and cannot read Command or your ServiceNow session. Only a Command admin can add, change or remove one. See [HTML widget data bridge](#html-widget-data-bridge). |
| **Button**                              | A link to content, a record or an address                   | Target, label, caption, style                                                                                                                                                                                         |

**Good to know**

* The assistant can assemble a dashboard for a role or topic, for example `build a CFO dashboard`. It shows a preview and waits for **Yes, create it**. Generated dashboards contain only widgets that are fully set up and whose source has data on your instance. A **Data gaps** note on the dashboard lists the widgets it left out and how to add them.
* A widget that adds up every record of its source (a measure, a Score summary, a lifecycle summary) is slower on a large source. Generated dashboards leave those out above 1,000 records; a filter that narrows the source brings them back.
* Every widget ends with its data, a note saying what is missing, or an error with **Retry**. A widget that gets no answer stops after 30 seconds (two minutes for one that adds up a whole source).

#### HTML widget data bridge

An HTML widget can read and change records through `window.command`, a small set of calls Command adds to the widget's frame.

* **Only a Command admin can add, change or remove an HTML widget.** Anyone else can view and use it, and can move, resize or rename it. Command checks this on the server, not only in the screen.
* **The bridge is on only for code a Command admin saved.** Code from anyone else, code imported from a package, a copy made by someone who is not an admin, and an admin's unsaved edit all run without it. In **Edit** mode such a widget says **Data bridge off**. After an admin saves new code, open the dashboard again to turn the bridge on. For code saved before the bridge existed, an admin opens **Configure widget** and ticks **Turn on the data bridge for this code**.
* **Reads and writes run as the person viewing the dashboard.** They go through Command's permission-checked doors with that person's table, record and field permissions. Nobody gets more access through a widget than they already have. The script never sees the ServiceNow session, cookies or token.
* **Limits.** `query` returns up to 200 rows. System tables (`sys_*`) cannot be used, and `sys_*` fields cannot be written. A query cannot contain `javascript:`. A widget can have four requests running at once and make 30 requests in 10 seconds. A request that gets no answer fails after 20 seconds.

| Call                                                      | Does                                                                                                                                                                                             |
| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `command.query(table, { query, fields, limit, orderBy })` | Lists records. `query` is an encoded query, `orderBy` is a field name (start it with `-` for descending), `limit` defaults to 20. Each row has `sys_id`, and each field as `{ value, display }`. |
| `command.get(table, sysId, fields)`                       | Reads one record: `{ sysId, displayValue, canWrite, fields }`, each field as `{ value, display, canWrite }`. `fields` is optional.                                                               |
| `command.update(table, sysId, values)`                    | Changes fields. Answers the saved values, and in `rejected` any field you are not allowed to change.                                                                                             |
| `command.create(table, values)`                           | Creates a record the same way.                                                                                                                                                                   |
| `command.openRecord(table, sysId)`                        | Opens the record's form in a Command tab.                                                                                                                                                        |
| `command.user()`                                          | The person viewing: `{ sysId, name }`.                                                                                                                                                           |

Every call returns a promise. A failed call rejects with an error whose `code` is, for example, `forbidden`, `not_found`, `table_not_allowed` or `rate_limited`.

```html
<ul id="apps"></ul>
<script>
  command.query("cmdb_ci_business_app", {
    query: "operational_status=1",
    fields: ["name", "owned_by"],
    orderBy: "name",
    limit: 10,
  }).then(function (rows) {
    var list = document.getElementById("apps");
    rows.forEach(function (row) {
      var item = document.createElement("li");
      item.textContent = row.name.display + " (" + (row.owned_by.display || "no owner") + ")";
      var button = document.createElement("button");
      button.textContent = "Mark reviewed";
      button.onclick = function () {
        command.update("cmdb_ci_business_app", row.sys_id, { short_description: "Reviewed from the dashboard" })
          .then(function (result) { button.textContent = result.rejected.length ? "Not allowed" : "Done"; })
          .catch(function (error) { button.textContent = error.message; });
      };
      item.appendChild(button);
      list.appendChild(item);
    });
  });
</script>
```

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-dd7cc9da8a9ef90cbab176f1fc98f018f74553ac%2Fcommand-dashboard-add-widget.png?alt=media" alt="A Dashboard in Edit mode with the Add a widget catalogue open, listing KPI, score, data quality, lifecycle and measure widgets."><figcaption><p>The Add a widget catalogue in Edit mode</p></figcaption></figure>

### Hierarchy Map

**What it is.** A map of parent and child records: a capability map, a landscape, an org chart, a treemap and more.

**When to use it.** To show structure, for example business capabilities and the applications that support them.

**How to**

1. Create a **Hierarchy Map**. It says **Build a hierarchy map**.
2. Drag records, or a saved Scenario, onto it.
3. In the **View** row choose a **Layout**: Nested boxes, Landscape, Org Chart, Treemap, Circle packing, Icicle or Indented tree. Adjust **Size by**, **Level**, **Columns**, **Color** and **Show counts**.
4. Click **Edit** to rearrange. Drag a node onto another to make it a child, or onto the background to make it top level. Use **×** to remove a node and **⊕** to load its connections.
5. Download it from the arrow next to **Share**.

**Good to know.** Your manual placements are saved and take priority over the structure Command works out from the data. See [Hierarchy Map](/command/prior-v26.0/visualizations/hierarchy-map.md) for more.

### 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-centre the map.

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

***

## Record views

### 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.
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**.

### 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 programme".

**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**.

### 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 **Edit** 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 or quarter, then **Save measures**.                                                                         |
| **Relationships**       | Edit the record's relationships.                                                                                                  |
| **Data quality** card   | See the record's quality score and **Verify** fields due for review. See [Data Governance](/command/features/data-governance.md). |
| **Show N empty fields** | Reveal blank fields.                                                                                                              |
| **Draft**               | Draft a description from the record's properties and relationships.                                                               |

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

### 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](/command/features/relationship-editor.md) for every task.

***

## Content

### 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.

**Good to know.** The assistant can save an executive summary as a Note: ask `executive summary for <name>` and accept the offer to save it.

### 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 URL** on the item's **⋯** menu in My Space.

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

### 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.** Dragging the board onto a Table, Roadmap, Hierarchy Map or similar type imports its shapes as records.

***

## Inventory

### 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 factor ledger** for the evidence, and **To raise confidence** for what would make the answer stronger.
4. Use **Notify owner** to tell the record's owner or steward.
5. Click **Re-run assessment** after the data has been fixed.
6. Click **Accept plan** to record your decision.
7. Click **Download PDF** to share it outside Command.

**Good to know.** Accepting a plan records a decision. It changes no records.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-2d6b41c257959c7872feba7e8767d72a1c106e01%2Fcommand-copilot-advisory-report.png?alt=media" alt="An Advisory Report with the Ready to decide chip, the confidence score, the recommendation and the factor ledger."><figcaption><p>An Advisory Report with its verdict, confidence and factor ledger</p></figcaption></figure>

### Folder and Shortcut

| Type         | What it does                                                                                                                                      |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Folder**   | Organises My Space. Sharing a folder shares everything inside it.                                                                                 |
| **Shortcut** | Puts one item in a second place without copying it. Use **Add shortcut to Personal** on an item's **⋯** menu. The original stays the single copy. |

See [My Space and sharing](/command/the-portal/my-space.md).

## Related

* [The Portal](/command/the-portal/portal.md) for the content header and panels.
* [Personas](/command/the-portal/personas.md) for which types appear in the create menu.
* [Data Hub](/command/the-portal/data-hub.md) for finding records to add.
* [Use cases](/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.