If you run a large organization, work is likely split across several portfolios - by division, product line, or region. The moment leadership asks how the whole company is doing, someone has to stitch the numbers together by hand.

Enterprise Portfolio removes that step: a space above your portfolios that aggregates them into one live view for reporting, comparing, and editing across the whole organization.

You will need:

Enterprise Portfolio is a new top level above Portfolio: Enterprise Portfolio → Portfolio → Workspace. It aggregates data rather than duplicating it - what you see here are the same records that live in their source portfolio and workspace.

A Portfolio connects to only one Enterprise Portfolio, Enterprise Portfolios cannot nest, and Workspaces connect through their Portfolio rather than directly. It appears in the same switcher you already use between workspaces and portfolios - select it to step up a level.

Enterprise Portfolio uses the same table and roadmap views you already know - only the scope changes, since every view now spans every portfolio underneath it.

The actions you can take:

Rolling out the same change across divisions used to mean opening each portfolio separately and repeating the same edit multiple times.

In Enterprise Portfolio, you can select items from multiple portfolios at once - a handful of initiatives from Portfolio A alongside a few from Portfolio B, for example - and bulk-edit them together in a single action, the same way you'd bulk-edit within one portfolio.

There's one limitation worth knowing before you rely on it: when a selection spans more than one portfolio, status, importance, and any custom field that exists in only one of those portfolios get grayed out in the bulk-edit dialog.

The Initiative used to be the highest work item level, scoped to a single portfolio - too small for a strategic bet that several divisions contribute to, usually tracked instead in a disconnected slide deck.

Super Initiatives fix that: a new work item type (5-dot) one level above Initiative (4-dot), tracing a strategic bet down to the epics delivering it - Super Initiative → Initiative → Epic.

Follow these steps:

Super Initiatives get their own icon, terminology, and view controls, and support bulk actions - available only at the Enterprise Portfolio level.

Every portfolio in your organization defines its own custom fields independently. As a result, two portfolios might both have fields named Quarter, Segment, or Team, but Enterprise Portfolio treated them as completely separate because they were created independently.

This made it impossible to consistently group or filter data across portfolios. Building an enterprise-wide roadmap required every portfolio owner to align on the same field definitions - a level of standardization that was rarely achievable.

Now, fields with the same name and type are automatically recognized as the same field across portfolios. There’s nothing to configure.

All joined fields appear under the Joint portfolio fields section in your view controls.

The payoff: You can now group, filter, and analyze work across every portfolio using a shared set of fields - without requiring every portfolio owner to standardize their configuration first.

Splitting the organization into portfolios keeps each division's work organized, but the work itself does not respect those lines. A platform team in one division can easily be blocking a product team in a completely different portfolio, and until now, that dependency was invisible unless someone happened to mention it in a meeting - there was no way to see it, let alone plan around it.

Enterprise Portfolio uses the exact same dependency types you already use everywhere in Craft.io - Related, Blocked by, and Blocks. What's new is that these relationships can now be created between any two work items in the account, regardless of which portfolio or workspace they belong to, and they show up in the Enterprise Portfolio view the same way in-portfolio dependencies already do.

To create one, open any work item, go to its Dependencies section, and search for the item you want to link - items from every portfolio in the account are available, not just your own. You will need editor access in both workspaces involved to create the link.