> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/app/modules/portfolios.md).

# Portfolios

## Overview

Portfolios help you create dedicated programmes to track and manage your security testing. Want to know how your internal systems compare with your external systems? Or want to track the security posture of your applications? Portfolios make this easy.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FHyhNQ7n5qIzohDu2pwpu%2Fportfolio-diagram-01.svg?alt=media&amp;token=9c543088-375b-44e9-bfc7-edbb5c952630" alt=""><figcaption></figcaption></figure>

Every portfolio comes with streams. Streams bring together all the related testing for part of a portfolio, such as a region, a business unit or a product line. Projects are linked to streams, so a portfolio is made of streams, and streams are made of projects.

Each portfolio and stream has its own dashboard, and people with view access only see data from the projects they can access.

## Example

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FG5ewjW3v0hi8k5Ek2h6m%2Fportfolios-at-a-glance.svg?alt=media&amp;token=f9bf6855-fbd3-4e8f-a299-79804064bad8" alt=""><figcaption></figcaption></figure>

This example portfolio, *Externally Facing Applications*, has two streams:

| Stream                     | Projects                                                      |
| -------------------------- | ------------------------------------------------------------- |
| **US External Apps**       | USA Commerce Portal, USA Mobile App, Main Integration Gateway |
| **European External Apps** | Main Integration Gateway, EU Mobile App                       |

Projects can be linked to many streams and portfolios. This helps make sure you're tracking the right vulnerabilities across your enterprise. In the example, vulnerabilities in the `Main Integration Gateway` project might be relevant to both `US External Apps` and `European External Apps`, so the project is linked to both streams.

## Why it matters

* **Track business-as-usual (BAU) testing.** Portfolios and streams show how each area is tracking over time, not just one test at a time.
* **Focus your time and resources.** Compare areas, such as internal and external systems, to see where to focus.
* **Make better decisions.** Every portfolio and stream has its own dashboard, with details on vulnerabilities, projects and assets, to help you make more informed decisions about tracking and remediation.
* **Share the right view.** Give people view access to a portfolio or stream, so they see only what's relevant to them.

## Who uses it

| Who                                      | To                                                                       |
| ---------------------------------------- | ------------------------------------------------------------------------ |
| **Administrators**                       | Create and manage portfolios and streams, link projects, and give access |
| **Security and programme managers**      | Track security posture across a programme, and decide where to focus     |
| **Executives and business unit leaders** | See how their area is tracking, from the portfolio or stream dashboard   |
| **Application and product owners**       | Follow the testing and vulnerabilities for their applications            |

Portfolios are created and managed by Administrators. Other users can be given view access. See **Manage access**, below.

## Use the portfolio dashboard

Every portfolio and stream has its own dashboard, with details on vulnerabilities, projects and assets. Use it to see how a programme, or one part of it, is tracking, and where remediation is needed.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FlaBn1fFbwpwcCZ0R2l3d%2FScreenshot%202026-11-10%20at%2011.19.58%E2%80%AFam.png?alt=media&amp;token=6eb4dc97-b7df-44dd-81d2-09b067e902a3" alt=""><figcaption></figcaption></figure>

## Create a portfolio

You must be an Administrator.

1. Select **Portfolios** in the main menu.
2. Click `New`.
3. Complete the details for your portfolio, including any custom fields.
4. To add a stream, click `Streams`.
5. Enter a name for the stream, and optionally link existing projects to it.

You can create as many streams as you need.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F3aP5rdQPUVsD4yKI04Cx%2FScreenshot%202026-11-10%20at%2011.21.05%E2%80%AFam.png?alt=media&amp;token=24711c12-8f81-43a3-96e2-12faed5bfbb1" alt=""><figcaption></figcaption></figure>

## Link projects to streams

You can add projects to portfolios and streams in two ways.

### From the portfolio

1. On the portfolio page, click the `cog` to edit the portfolio.
2. Select **Access and Streams**.
3. Create new streams and link projects to them, or update the projects on existing streams.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F4cEcubzKj26T1T8EHh5u%2FScreenshot%202026-11-10%20at%2011.22.11%E2%80%AFam.png?alt=media&amp;token=08de8e7b-9939-4891-ac54-5a51122eaf71" alt=""><figcaption></figcaption></figure>

### From the project

You can link a project to one or more portfolios and streams:

* when you create the project
* when you approve a project request
* when you edit the project

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FJkuZYyRmejlZ0tKT7eSm%2FScreenshot%202026-11-10%20at%2011.24.39%E2%80%AFam.png?alt=media&amp;token=224ee83e-9e4b-4089-93e4-c18dee930398" alt=""><figcaption></figcaption></figure>

## Manage access

Administrators can give non-admin users view access to individual portfolios, or to their streams.

* Access can be given to **groups** or **users**.

{% hint style="info" %}
People with access only see data from the projects they have access to on that portfolio or stream. Giving someone access to a portfolio doesn't give them access to its projects.
{% endhint %}

### Give access to a whole portfolio

Use the option at the top of the portfolio's **Access and Streams** settings page. This gives access to the portfolio and all its streams.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FTmtd926pPr3qfgISryY1%2FScreenshot%202026-11-10%20at%2011.26.30%E2%80%AFam.png?alt=media&amp;token=ed9d7282-8b25-4521-8320-1fbcaa6c7ff5" alt=""><figcaption></figcaption></figure>

### Give access to one stream

On the **Access and Streams** settings page, click a stream and set the access on that stream.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2Fy6pfcA7S8wySeUb0Zpth%2FScreenshot%202026-11-10%20at%2011.26.57%E2%80%AFam.png?alt=media&amp;token=e01d283e-95f0-4a45-8934-fa3d20df57d4" alt=""><figcaption></figcaption></figure>

## Tips

* **Build portfolios around the questions you need to answer**, such as internal against external, or one portfolio per business unit.
* **Use streams for the next level down**, such as regions, products or teams.
* **Link a project to every stream it's relevant to.** Shared systems, like an integration gateway, often belong in more than one.
* **Link projects when you create them**, or when you approve a request, so portfolios stay up to date without extra work.
* **Give access through groups**, so it's easy to keep up to date as people change roles.
* **Remember that portfolio access is view-only, and limited by project access.** People only see data from projects they can already access.

## FAQ

**Who can create a portfolio?** Administrators. Portfolios are created and managed by Administrators.

**What's the difference between a portfolio and a stream?** A portfolio is a programme, such as Externally Facing Applications. Streams group related testing within it, such as US External Apps. Every portfolio comes with streams.

**How many streams can a portfolio have?** As many as you need.

**Can a project be in more than one stream or portfolio?** Yes. Projects can be linked to many streams and portfolios.

**Can non-admin users see a portfolio?** Yes, if they're given view access to the portfolio or one of its streams. Access can be given to groups or users.

**Why can't someone see all the data in a portfolio?** They only see data from the projects they have access to on that portfolio or stream.

**Where can I link a project to a portfolio?** From the portfolio's **Access and Streams** settings, or when you create a project, approve a project request, or edit a project.

## Related pages

* [Projects](https://support.attackforge.com/app/modules/projects)
* [Creating and managing projects](https://support.attackforge.com/app/getting-started/creating-and-managing-projects)
* [Requesting a project](https://support.attackforge.com/app/getting-started/requesting-a-project)
* [Groups](https://support.attackforge.com/app/modules/groups)
* [Analytics](https://support.attackforge.com/app/modules/analytics)
* [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access)


---

# 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://support.attackforge.com/app/modules/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.
