Related projects, finally grouped under one owner and one budget

A portfolio carries its own owner, status, budget and objective, and sits above its projects rather than beside them. Add a manager who can edit it, or a member who only gets read access to its projects, without touching what either of them can do anywhere else in the workspace.

Included from Pro upwards

Start free See pricing

Why this exists

Ten related projects look like ten unrelated projects the moment anyone needs to report on them together.
A programme’s budget and owner end up living in a slide deck instead of on the projects they are supposed to cover.
Giving someone visibility across a whole group of projects usually means adding them to every single one by hand.

What it does

Group projects the way the business is organised

Every portfolio belongs to one company, and carries an owner, a status, a start and end date, a budget and an objective, so "Q3 Growth Initiatives" is a real record rather than a label typed onto a handful of projects.

Roll projects up automatically

Its project count, how many are active, and the average progress across all of them are computed live the moment you open a portfolio, not maintained by hand in a second document.

Give access without handing over the company

A company manager can create and edit portfolios under the companies they manage, without being an org admin. Add a portfolio member as manager for edit access or member for read-only access to its projects, and neither reaches anything outside that one portfolio.

Edit it inline, same as everything else

Rename a portfolio or change its description right on the list or its own detail page, in cards or list view, with the same click-to-edit pattern the rest of WorkBOS uses.

What it does not do

The part you would otherwise find out in week three. If one of these is central to how you work, raise it before you buy rather than after.

Portfolios are the top level. There is no cross-company programme above them and no group-of-portfolios view; each one sits under exactly one company.
The budget field is a single number you set, not a tracked budget. It does not total actual spend from invoices, bills or the ledger against it, and there is no variance or burn-down.
Every portfolio must belong to a company. There is no way to group projects that do not sit under one, and Portfolios itself is on Pro and above, so it is not part of the Free plan.
Portfolio-level roles (manager, member) are separate from company and organisation roles. They control access to this portfolio’s projects specifically and do not change what someone can do anywhere else.

Questions, answered

What sits above a portfolio?+

Nothing. Portfolios are the top level in WorkBOS’s hierarchy, above Project, under Company. There is no cross-company programme view or a group of portfolios above this one.

Does the budget field track actual spend?+

No, not yet. It is a number you set on the portfolio; invoices, bills and the ledger do not total against it automatically, so treat it as a target you compare by hand rather than a live burn-down.

Can I give someone access to a group of projects without making them a company manager?+

Yes. Add them to the portfolio as a member for read access to its projects, or a manager if they should also edit it. Neither widens what they can do anywhere outside that portfolio.

Which plan includes portfolios?+

Pro and above. On the Free plan a project can still link to a company; there is simply no portfolio layer to group several of them under until you upgrade.

The full product documentation for this module is at /docs/hierarchy.

Try it on your own data

Free for up to 5 seats, no card required. Every module is in the same workspace, so nothing needs connecting to anything.

Start free Compare with others