Setting Up Asana Reporting Dashboards Without the Fluff

Setting up reporting dashboards in Asana takes two paths. For a single project, open the project and click the Dashboard tab, then Add chart. For metrics across many projects, click Reporting in the sidebar, create a Dashboard, and add charts there. Both need a paid plan, starting at Starter.

That two-path split is the thing most guides skip, and it is exactly where people get stuck. A project dashboard and a Reporting dashboard look similar but answer different questions. Get the distinction right first, then the setup is quick.

Two kinds of dashboards, and which one you actually want

A project dashboard lives inside one project. It only charts tasks in that project, and it is the fastest way to get a status pulse: how many tasks are open, who is overloaded, what is slipping past its due date.

The Reporting hub in the left sidebar is the cross-project layer. Here a single dashboard can pull tasks from an entire organization, from specific teams, from portfolios, or from projects owned by a particular person. This is where you build the view a director or a PMO lead wants, the one that spans twenty projects at once.

If you only manage one project, stay in the project’s Dashboard tab. The moment you need to compare projects or roll several up into one number, move to Reporting. Do not try to force a project dashboard to do cross-project work. It cannot see past its own project walls.

The plan gating that trips people up

The free Personal plan has no dashboards at all. Personal is capped at two users and built for individual to-do lists, so charts and reporting are simply absent. If you are on free Asana and hunting for a Dashboard tab that is not there, that is why, not a bug.

From Starter up you get project dashboards and the Reporting hub, but with an important catch: on Starter you can only chart task data. Charting project-level, portfolio-level, or goal-level metadata requires Advanced or higher. Portfolio dashboards sit behind the same Advanced wall. Here is the short version, all confirmed against Asana’s help pages:

Starter runs $10.99 per user per month billed annually, or $13.49 month to month. Advanced is $24.99 annually, $30.49 monthly. If your reporting plan leans on portfolio roll-ups or project-health charts, you are budgeting for Advanced, not Starter, and that gap is real money per seat. Work through the full breakdown in our guide to Asana pricing before you commit a team.

Build a project dashboard

This is the five-minute version, good for a weekly team check-in.

1. Open the project and click the Dashboard tab. Asana auto-populates a few starter charts the first time you land here.
2. Click + Add chart.
3. Choose your chart style from the picker.
4. Toggle data labels on if you want the raw numbers printed on the chart, off if you want a cleaner look.
5. Set your X-axis (the grouping, for example assignee or due date) and your Y-axis (the measure, usually task count or a numeric custom field).
6. Add any filters to narrow the data, then click Add.

The charts here read only from this project, so the quality of your dashboard is capped by the quality of your task data. If assignees are blank or due dates are missing, the chart shows that honestly. A dashboard is a mirror, not a fix. Tightening up assignment and date hygiene, ideally with Asana rules that auto-assign and set dates, does more for your reporting than any chart style ever will.

Build a cross-project dashboard in the Reporting hub

When you need to see across projects, this is the setup.

1. Click Reporting in the left sidebar.
2. Click + Create, then Dashboard.
3. Click Add chart and choose what to report on: tasks, projects, portfolios, or goals. Remember that anything beyond tasks needs Advanced.
4. Pick your source scope. For task charts you can include tasks from an entire organization, specific teams, portfolios, projects owned by chosen people, or individual projects.
5. Set the X-axis grouping. Options include assignee, creator, a custom field, completion status, project, or time period.
6. Set the Y-axis measure: task count, time, actual versus estimated time entry, or the sum or average of a global numeric custom field.
7. Apply filters, then save. Repeat to stack several charts into one dashboard.

One quiet limitation worth knowing up front: you can only group by global custom fields, the ones defined in your organization’s field library. A custom field created inside a single project will not appear as a grouping option here. If you want to slice reporting by a field, promote it to a global field first.

The nine chart types, and what each is actually for

Asana gives you nine chart styles. You do not need all of them. Most useful dashboards use three or four.

• Bar chart and stacked bar chart: the workhorses. Stacked bars are best when you want a total and its breakdown at once, for example tasks per assignee split by status.
• Grouped bar charts: compare a primary field broken out by a secondary field along one metric. Good for cross-team comparisons.
• Line chart: trends over time. You can add a manual benchmark line to mark a target or threshold, which is handy for velocity or budget tracking.
• Burnup and burndown charts: scope and completion over a sprint or a release window.
• Donut chart: a single categorical split, like open versus complete. Readable at a glance, weak once you have more than four or five slices.
• Number chart: one big figure. Underrated. A count of overdue tasks in 48-point type communicates faster than any bar ever will.
• Lollipop chart: a lighter alternative to a bar chart when you have many categories and the bars would get visually heavy.

Dashboards refresh on their own. Charts recalculate every time you open the tab or reload the page, so there is no manual refresh button to hunt for and no stale-data warning to worry about. What you see is current as of the page load.

Where Asana dashboards fall short

Be honest with yourself about the ceiling here. Asana dashboards report on Asana data and nothing else. There is no connector to blend in spend from your finance system, pipeline from your CRM, or hours from a separate time tool. The moment your report needs to combine Asana with an outside source, you are exporting to a spreadsheet or piping data into a BI tool like Looker or Power BI, and the built-in dashboards stop being enough.

Two more rough edges. Numeric measures beyond task count depend on you having disciplined numeric custom fields, so a dashboard that tracks budget or effort is only as good as the fields your team fills in. And sharing has a sharp corner: a dashboard is private to its owner by default, collaborators get read-only access, and there is exactly one admin per dashboard. Promote someone else to admin and you lose your own edit access, because the role does not split. Plan owner handoffs deliberately.

For a recurring executive deck where layout and polish matter, or for any board-level number that mixes Asana with financials, a spreadsheet or a proper BI layer is still the better call. Asana dashboards are excellent for the operational week-to-week; they are not a replacement for a data warehouse. If your team is weighing whether Asana is even the right home for this kind of reporting, our ClickUp versus Asana comparison digs into how the two handle dashboards differently.

None of this shows up until your task data is clean, which starts with individuals keeping their own queue in order. If My Tasks is a mess across the team, every roll-up inherits that mess, so it is worth getting My Tasks set up properly before you invest in dashboards.

Frequently asked questions

Does the free Asana plan include reporting dashboards?

No. The free Personal plan is limited to two users and does not include any dashboards or the Reporting hub. You need at least the Starter plan for project dashboards and task-based reporting, and Advanced for charts that report on project, portfolio, or goal data.

How often do Asana dashboards refresh?

Automatically. Both project dashboards and Reporting hub charts recalculate every time you open the tab or reload the page, so the numbers reflect the current state of your tasks. There is no manual refresh step and no scheduled sync to configure, and no stale data between visits.

What is the difference between a project dashboard and the Reporting hub?

A project dashboard lives inside one project and only charts that project’s tasks. The Reporting hub in the sidebar builds dashboards that span many projects, teams, portfolios, or an entire organization. Use the project tab for a single-project pulse and Reporting for anything cross-project.

Who can see a dashboard I create in the Reporting hub?

Only you, until you share it. Every dashboard is private to its owner by default. When you invite people they get read-only access, and clicking into a chart only reveals underlying data they already have permission to see. Each dashboard has a single admin.

Verify the current chart options and plan gating on Asana’s official pages: how to set up reporting, the chart styles reference, and the Asana pricing page.

Sponsored