Module guide
Portfolios
Group projects under a parent and roll up status, progress, and risk.
Overview
Portfolios are containers for projects. They roll up project-level metrics (completion %, on-time rate, and open risk count) into a single dashboard for leadership review. A project can belong to one portfolio at a time.
Highlights
The capabilities worth knowing before you dive in.
- Drag-and-drop project assignment
- Health rollup: ON_TRACK, AT_RISK, or OFF_TRACK, derived from project signals
- Per-portfolio export to PDF or PPTX for status reviews
- Filterable by owner, label, or health
Important to know
Limits, permissions, and sharp edges to keep in mind.
- A project can sit in only one portfolio. Move it to switch.
- Portfolio health is derived, so you can't set it directly. Adjust the underlying project risk and on-time rate to change the rollup.
How to use it
The primary workflow, start to finish.
- Open Portfolios in the sidebar.
- Click New portfolio, then set a name and owner.
- Drag projects in from the right rail, or assign them from the project header.
FAQ
- Can a project belong to multiple portfolios?
- No. Portfolios are a strict tree. Use Labels for many-to-many tagging instead.
- Can I set a portfolio's health directly?
- No. Portfolio health is derived from the projects inside it, so it is changed by improving the underlying project risk and on-time rate rather than by overriding the number.
- How do I move a project between portfolios?
- Move it. A project sits in exactly one portfolio, so adding it to another removes it from the first rather than listing it twice.
Automate this module
Everything on this screen is scriptable. Drive it from the REST API, or let an AI agent run it through the MCP server.
Was this page helpful?