Portfolio
Every project on one screen, the ones that need you first.
The Portfolio page answers the question a delivery lead starts the week with: which of my projects is in trouble? It puts one row per project side by side, using the numbers the modules already calculate: delivery confidence and the next milestone from Promise, scope health and drift from ScopeGuard, and blocked and open work from FlowLens. Nothing on it is new data, just the whole picture in one place.
One row per project
Each project gets a row, and the projects that most need attention sort to the top: low confidence, poor scope health and blocked work pull a project up. Columns only appear for the modules your plan includes, so the table never shows an empty column for a module you don't use.
Reading the columns
Confidence is Promise's chance of hitting the next milestone, with the forecast date and milestone name next to it. Scope health is ScopeGuard's score for the project's newest locked baseline, with how much was added, removed and changed since. Blocked counts the project's blocked tickets in FlowLens, and the item counts show open against done. A dash means that module has nothing for the project yet, for example no locked baseline.
Who sees which projects
Admins and members with access to every project see them all. A member who is limited to some projects sees only those rows, and the same applies to the CSV export and to anything Ask Firebeam says about the portfolio.
Exporting to CSV
Export CSV downloads the table as it is, ready for a steering deck or a board pack. It opens directly in Excel, Numbers and Google Sheets, with names in any language intact.
Asking about the portfolio
The toolbox on the Portfolio page has the Ask Firebeam box, so you can go straight from the table to a question such as "which project needs my attention first?" and get an answer written from the same numbers.