> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-cloud/managing-portfolios.md).

# Managing portfolios

A portfolio's Overview page is the central place for managers and tech leads to monitor the releasability of projects under their supervision.

This feature is only available in the [Enterprise plan](https://www.sonarsource.com/plans-and-pricing/).

Releasability is based on the projects’ quality gates included in your portfolio. Each portfolio's Overview page offers an aggregate view of the releasability status of all projects in the portfolio. See [Viewing portfolios](https://docs.sonarsource.com/sonarqube-cloud/managing-portfolios/viewing-portfolios.md) for more information.

## Permissions <a href="#permissions" id="permissions"></a>

To manage a portfolio, you need the **Edit** permission, granted by the portfolio’s administrator. See [Administering portfolios](https://docs.sonarsource.com/sonarqube-cloud/managing-portfolios/administering-portfolios.md) for more details.

{% hint style="info" %}
When you create or edit a portfolio, you might see the names of private organizations in your enterprise that you are not a member of.
{% endhint %}

## Creating a portfolio <a href="#creating-portfolio" id="creating-portfolio"></a>

To create a portfolio and select its projects, see [Creating portfolios](https://docs.sonarsource.com/sonarqube-cloud/managing-portfolios/creating-portfolios.md).

## Editing a portfolio <a href="#editing-portfolio" id="editing-portfolio"></a>

To add or remove projects in a portfolio, or to delete a portfolio, see [Editing portfolios](https://docs.sonarsource.com/sonarqube-cloud/managing-portfolios/editing-portfolios.md).

## Portfolio dashboards

You can monitor key metrics of your portfolio, identify risks and communicate progress using configurable dashboards. See [Portfolio dashboards](https://docs.sonarsource.com/sonarqube-cloud/managing-portfolios/portfolio-dashboards.md) for more information.

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Introduction](https://docs.sonarsource.com/sonarqube-cloud/getting-started-with-enterprise/introduction.md) to Getting started with Enterprise
* [Viewing portfolios](https://docs.sonarsource.com/sonarqube-cloud/managing-portfolios/viewing-portfolios.md)
* [Creating portfolios](https://docs.sonarsource.com/sonarqube-cloud/managing-portfolios/creating-portfolios.md)
* [Editing portfolios](https://docs.sonarsource.com/sonarqube-cloud/managing-portfolios/editing-portfolios.md)
* [Portfolio dashboards](https://docs.sonarsource.com/sonarqube-cloud/managing-portfolios/portfolio-dashboards.md)
* [Administering portfolios](https://docs.sonarsource.com/sonarqube-cloud/managing-portfolios/administering-portfolios.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.sonarsource.com/sonarqube-cloud/managing-portfolios.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.
