> 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/prior-v26.0/features/stakeholders.md).

# Stakeholders

{% hint style="warning" %}
**Previous release**

This page describes the release before v26.0, which used the classic ServiceNow forms and lists. It is kept for reference. The current documentation has no separate page for this topic yet. See [The Portal](/command/the-portal/portal.md) for how the current version works.
{% endhint %}

A Stakeholder represents an individual or group of people who are engaged and have an interest in a specific Portfolio Element.

The Stakeholder Portfolio Feature enables stakeholders to prioritize various Portfolio Elements from their specific view and priority.

The Stakeholder Rating is calculated based on the total prioritization performed by various stakeholders and the upstream influence of each stakeholder. This rating represents the average interest rating of a Portfolio Element.

{% hint style="info" %}
**Stakeholder Visibility**

By default, any user with at least the YouDesign Command Reader role can see the list of Stakeholders, including influence levels. To ensure sensitive data is not accessible to all users, modify the access control lists (ACLs).
{% endhint %}

## Stakeholders Overview

Open the YouDesign Command Settings -> Stakeholders table from the Application Menu.

**A** – Click the New button to add a new Stakeholder.

**B** – Shows the list of all available Stakeholders.

![](https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-f7313c6cdfdec2bc6d43583e14d8f4e974d83d8a%2F2d7a43d-stakeholder_table.png?alt=media)

## Create a new Stakeholder

To create a new Stakeholder, click the New button on the Stakeholder table.

**A** – Specify the name of the Stakeholder. You can use a person name, role name, or group name based on your requirements.

**B** – A brief description of the Stakeholder.

**C** – The upstream influence of the Stakeholder represents their decision-making power within the enterprise.

![](https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-a97e0609e732da72cc8292d79dc771f103d2836d%2Faec70ea-stakeholder_defintion.png?alt=media)

## Rating of Portfolio Elements

You can prioritize each Portfolio Element by one or more Stakeholders within the Stakeholder Tab.

**A** – Click the Edit button to add additional Stakeholders to the list to allow them to prioritize the Portfolio Elements.

**B** – List of the Stakeholders and the prioritizations.

**C** – Double-click the Priority to select one of the following choices:

* Extreme
* High
* Medium
* Low

![](https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-6c12ed7c3b8f4fc3203b0805d349c614bfead3b5%2F88cc911-stakeholder_tab.png?alt=media)


---

# 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/prior-v26.0/features/stakeholders.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.