> 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/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/retire-dashboards.md).

# Retire Dashboards

Retire the legacy dashboards after upgrading to YouDesign Command v26.1, once every other legacy feature is retired.

Retires the legacy dashboard layer: 27 legacy PA dashboards with their permissions, tab links and menu modules, the tabs and canvases beneath them, and every tile that pointed at a report the feature cleanups deleted. It also removes 15 legacy Platform Analytics dashboards with their tabs, canvases, permissions and widgets, and the content of the legacy UPM·X portal pages, such as their headers and the landing page. It deletes the remaining 108 legacy reports, with who they were shared with. Follow [Upgrade from v26.0 to v26.1](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261.md) first.

Retire the dashboards only after every other legacy feature is retired: the set deletes all of them, whatever you keep.

<details>

<summary><strong>The 15 Platform Analytics dashboards</strong></summary>

* AiPM
* APM
* Architecture Governance
* Business Planning
* Command License Dashboard
* Executive Landing Page
* Idea Management
* Information Architecture
* Risk & Compliance
* Scenario Comparison
* Scenario View
* Strategic Planning
* TPM
* Transformation & Change
* UPM-X Data Quality

</details>

## Steps

### 1. Commit the update set

**First, check Logic Preservation.** In **Retrieved Update Sets**, look for **YCM V26.1 Legacy Logic Preservation** with the state **Committed**.

If it is already committed, for example because you retired another feature first, do not commit it again. Committing it again turns the shared Lifecycles and Measures calculation jobs back on, even ones you deleted by hand. If it is not there, or not yet committed, commit it now:

{% file src="/files/r5th8lgCHZ3rAU8Ldbom" %}

The cleanup set deletes the legacy `x_inpgh_upmx.report_reader` role. Before you commit it, give everyone who holds that role **Command Reader** (`x_inpgh_upmx.reader`). See [Roles the cleanup removes](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261.md#roles-the-cleanup-removes).

Then commit **YCM V26.1 Legacy Dashboards Cleanup**. Skip this set if you are using **Full Cleanup**.

{% file src="/files/8Pgm3uu646fRdy3iRTYJ" %}

The preview reports one error, on `analytics_category_m2m_3552b41071a93ed9ffc4943a3e2baecf`. Skip that entry and commit the rest: the record belongs to the global scope, which this set cannot change. One harmless category link stays behind. If you already skipped it in the Data Governance cleanup, it is the same record.

There are no other manual steps for this feature.

## Related

* [Upgrade from v26.0 to v26.1](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261.md)
* [Path C: Retire some features](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features.md)


---

# 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/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/retire-dashboards.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.
