Portfolio admins organize their portfolio fields into categories, and reasonably expect that structure to hold everywhere those fields appear. It did not. Each connected workspace showed the same portfolio fields with none of the organization, so the same structure had to be rebuilt by hand in every workspace.

With this update, every category you create at the portfolio level is also created in each connected workspace, and each portfolio field lands in the same category it has on the portfolio. A portfolio admin who creates a Strategy category and moves the Business Value and Confidence fields into it will find that category, holding those two fields, in every connected workspace.

The same applies when a workspace is connected to an existing portfolio. It picks up the portfolio's categories and the placement of every portfolio field in one step, instead of starting from a flat list.

To get started, open the Portfolio Fields tab in Portfolio Settings and organize your portfolio fields into categories.

Inheritance that could not be overridden would be worse than no inheritance at all. Workspace admins organize fields around how their own team works, so the portfolio's structure is a sensible default rather than a rule.

With this update, workspace admins keep full control over portfolio fields in their own workspace. An inherited category can be renamed, deleted, or left alone, and a portfolio field can be moved into any category the workspace has. Once a workspace makes its own decision, later changes at the portfolio level do not undo it.

A portfolio category called Discovery arrives in two connected workspaces. One of them renames it to Research. When the portfolio later renames the category to Strategy, the workspace that renamed it keeps Research, and the one that did not becomes Strategy.

To place a portfolio field somewhere else, open the Custom Fields tab in Workspace Settings and move it into the category you want.