Asana Portfolios is a good way to see many Asana projects on one screen, and a weak way to decide which projects should exist. It rolls up status, progress, owners and custom fields across projects, and with Workload it shows who is overbooked. It does not score proposals, rank them against a budget or tell you what to cut. Portfolios is only available on the Advanced and Enterprise plans.
That split is the whole buying question. If your problem is visibility, Portfolios probably solves it. If your problem is that the leadership meeting approves everything and the teams drown, it will show you the drowning in better detail, and that is all.
Key takeaways
- Asana Portfolios, Goals and Workload come with the Advanced plan, $24.99 per user a month billed yearly or $30.49 monthly, per Asana's pricing page in October 2026. Starter does not include them.
- Portfolios groups projects (and other portfolios) into one list with status updates, progress, custom fields, a timeline and a workload view.
- It is strong at reporting a portfolio. Weighted scoring, a funding line against a budget and capacity by role are things you build yourself or add elsewhere.
- Upgrading a 60 person Asana team from Starter to Advanced adds roughly $10,000 a year at list price, so price the gap you are actually trying to close first.
- Many PMOs keep Asana for delivery and run the funding decision in a separate portfolio layer above it.
What is a portfolio in Asana?
A portfolio in Asana is a container that holds a set of projects, and other portfolios, so you can monitor them together. Each row is a live project showing its owner, latest status update, progress, dates and any custom fields you add. From the portfolio you can switch to a timeline, a workload view of the people on those projects, and a dashboard of charts across the set.
Most PMOs build one portfolio per business unit or program, then a top-level portfolio that nests them. A project can sit in several portfolios at once, which is useful when a CIO and a product VP both want to watch the same work through different lenses.
The thing to understand early is that a portfolio only holds work that already exists as an Asana project. A proposal that has not been approved has no project yet, so it is either missing from the portfolio or created as a placeholder project, which then shows up in workload and reports as if it were real.
Which Asana plan has portfolios?
Portfolios is included in Asana Advanced and Asana Enterprise. The Personal and Starter plans do not have it. Advanced costs $24.99 per user a month billed annually or $30.49 billed monthly, according to Asana's pricing page in October 2026, while Enterprise is quoted by sales and adds features such as universal workload across the organization.
| Plan | Price per user | Portfolios | Goals | Workload |
|---|---|---|---|---|
| Personal | Free, small teams only | No | No | No |
| Starter | $10.99 a month billed yearly, $13.49 monthly | No | No | No |
| Advanced | $24.99 a month billed yearly, $30.49 monthly | Yes | Yes | Yes |
| Enterprise | Quoted | Yes | Yes | Yes, including universal workload |
Swipe to see more →
Time tracking against budgets is sold separately as the Timesheets and Budgets add-on on Advanced and Enterprise, so if your portfolio reporting depends on hours, add that to the quote. Prices change, so check the pricing page on the day you build the business case.
What the Asana Portfolios upgrade costs on a real team
The per-user price is misleading on its own, because Asana bills the team on one plan. You rarely get to upgrade only the six people in the PMO who want Portfolios; the developers, designers and marketers in the same workspace move with them. Here is the arithmetic for three team sizes at list price, billed yearly.
| Members | Starter per year | Advanced per year | Extra cost for Portfolios |
|---|---|---|---|
| 25 | $3,297 | $7,497 | $4,200 |
| 60 | $7,913 | $17,993 | $10,080 |
| 150 | $19,782 | $44,982 | $25,200 |
Swipe to see more →
That is not a reason to say no. Advanced also brings Goals, Workload, approvals and more automation, and for many teams those pay for themselves. It is a reason to name the problem before signing. If the problem is "we cannot see our projects in one place", the $10,080 buys exactly that. If the problem is "we approve too much", it buys a clearer view of the consequences.
Is Asana good for portfolio management?
Asana is good for portfolio monitoring and weak for portfolio decisions. Portfolios, Goals and Workload give a PMO a reliable, always current view of active projects, their status and who is overloaded. Asana does not ship a prioritization model, scenario planning or a funding line, so choosing which projects to start, and proving the plan is deliverable by role, still happens outside it.
Here is how the usual portfolio jobs map onto Asana.
| Portfolio job | In Asana Advanced | How well it works |
|---|---|---|
| Intake of project requests | Forms feeding a request project, with rules to route them | Good |
| Status reporting across projects | Portfolio status updates, progress and dashboards | Strong, the core of the feature |
| Linking work to objectives | Goals connected to projects and portfolios | Good |
| Who is overloaded this week | Workload view by task effort | Good for people, weaker for roles |
| Weighted scoring and ranking | Custom fields and formulas you design | Possible, fragile, no audit of weights |
| Funding line against a budget | Not built in | Spreadsheet or another tool |
| Capacity by role, twelve months ahead | Not built in; Workload is task-based and near term | Spreadsheet or another tool |
Swipe to see more →
The capacity row deserves a second look. Workload sums effort on assigned tasks, so it is excellent at spotting that Priya has 52 hours next week. It cannot tell you that next spring the plan needs four data engineers and you have two, because next spring's work is not yet broken into tasks or assigned. That forward, role-level question is the one that decides whether a portfolio is deliverable, and the resource capacity planning tool page shows how it is usually modeled.
What is the difference between a project and a portfolio in Asana?
A project in Asana holds tasks: the actual work, assignees and due dates. A portfolio holds projects: it shows their status, progress and fields side by side without containing any tasks itself. You manage work inside projects and monitor many projects from a portfolio. A portfolio can also hold other portfolios, so a PMO can nest program portfolios under one executive view.
Where Asana Portfolios starts to strain
These are the signals PMOs report, roughly in the order they meet them. Each one tells you what to add, which is not always "leave Asana".
| Signal | What is really happening | What fixes it |
|---|---|---|
| Status colors are green until the week before launch | Updates are self-reported with no agreed rules | Written status criteria, enforced in the review |
| The priority field says "High" on 70% of projects | Priority is typed in, not calculated from criteria | A weighted scoring model with weights set before scoring |
| Placeholder projects distort the workload view | Proposals were created as projects to get them on the list | Keep unapproved work in a register outside delivery |
| Everything gets approved | There is no visible cut-off | A funding line drawn down the ranked list |
| Projects are approved and then stall for months | Capacity was checked per person this week, not per role this year | A capacity plan by role and month |
Swipe to see more →
The second and fourth rows are the expensive ones. A priority field anyone can edit is a popularity contest, and a list without a cut-off turns the portfolio review into a status meeting. The project prioritization tool page walks through the scoring model and the funding line that replace them.
Asana alone, Asana with a decision layer, or a PPM suite
Three options cover nearly every team in this position.
| Option | Best when | Watch out for |
|---|---|---|
| Asana Advanced with Portfolios, Goals and Workload | Teams already live in Asana and the pain is visibility and status | You still build prioritization yourself, and the upgrade covers every member |
| Asana for delivery plus a portfolio workspace for decisions | Delivery works; leadership cannot agree what to fund, cut or delay | Two places to look, so keep the portfolio register as the one record of approvals |
| A dedicated PPM suite | You need financials, timesheets, scenarios and formal governance in one system | A larger contract and implementation, and teams may resist leaving Asana |
Swipe to see more →
The middle option is the one teams overlook because it does not feel like a purchase decision. Funded projects get created in Asana exactly as they are today; only the ranking, the funding line and the forward capacity plan live elsewhere. It is the same pattern we describe for Smartsheet project portfolio management and for Jira portfolio management, because the gap is the same in every work management tool. Once the list is agreed, keeping a fixed monthly review on sponsors' calendars is half the battle, and scheduling software for business teams takes the back and forth out of finding that slot.
How to decide before you upgrade
Test it on your own portfolio rather than in a demo. Take the last twenty requests your leadership group saw and check four things.
- Can you rank them in one sitting? Score each on the same five criteria and sort. If that needs a week of formula fields in Asana, the ranking is your missing piece.
- Can you show what falls below the budget? Add cost down the ranked list and mark where the money runs out.
- Can you see next year's shortfall by role? Not who is busy next week, but whether the approved list needs more of any role than you have.
- What does the upgrade cost in year two? Price every member you expect in twelve months on Advanced, plus Timesheets and Budgets if you need hours.
If Asana Advanced answers all four at a price you can defend, upgrade and use it fully. If it answers the visibility questions but not the ranking and capacity ones, you have found the gap. Our comparison of the best PPM software covers the suites, the PMO software guide covers lighter tools, and the Portfolio Hub workspace plans are published per workspace rather than per Asana seat, so you can price that option before the renewal call.