Dashboard
The Dashboard is the org owner's view of the whole account. Open it from your account menu, or from Settings → Dashboard.
It answers three different questions, and it's laid out that way: what is the work producing, what is it producing on each project, and who is doing it.
The Dashboard is for org owners. Every member has their own equivalent - see My Performance.
Ask for a chart
The panel owners land on first is Custom Graph - a chat that builds analytics for you. Ask in plain language:
"Issues per discipline over the last quarter, by office."
"Which projects have the most open fire-protection findings?"
The Custom Graph panel answering a plain-language question
It's the fastest way to get a number nobody built a report for, and it's usually quicker than working the filters by hand.
The numbers
Across the organization:
- Headline stats for the current period.
- A twelve-week trend for any metric, so you can see direction rather than a single figure.
- Breakdowns by discipline, by project, by team, and by person.
- A filter bar to narrow all of it - by team, discipline, project, or date.
A project belonging to two teams is counted in both, so the team breakdown and the team drill-down agree with each other.
Per project
The projects tab lists every project in the organization. Open one and you get the same treatment at project scale: stats, a twelve-week trend, and breakdowns - so you can tell a job that's throwing findings from one that's quiet because nobody's touched it.
What keeps coming back
The recurring issues panel summarises the patterns across your reviews: the mistake types that keep coming back, ranked, with a severity indicator.
This is the panel worth reading before a kickoff. If the same detail-reference error is the top finding across four jobs, that's a standards or template problem, not four coincidences.
The recurring issues panel
Reviewer performance
A per-person rollup of findings, as a ranked list.
It starts collapsed, deliberately. The numbers are attributed by who created the project, not by who did the reviewing - so a project manager who sets up every job carries every finding raised on it. Read as a ranking of people, it's misleading. Read as "where is the work concentrated", it's useful. Open it knowing which one you're looking at.
The roster
The members table lives here too - roles, teams, team leads, per-person grants, invites, and bulk changes. See Organization members & invites.
Pending share requests
When someone asks to share a checklist, workflow, code book or resource with the whole organization, the request lands here. It opens an evidence panel with the item, accept / decline controls, and the conversation thread; a decline needs a note. See How access works.
Two things worth knowing:
- It's a pool, not just you. Org owners and any team lead can act on these, so a request never waits on one inbox. It's the same queue that appears on the team page - one group of requests shown in two places, not two lists to keep straight.
- Team-level requests don't come here. Those go to that team's leads on the team's page.
If a panel is empty
Panels load independently and fail independently, on purpose: one panel that can't load its numbers won't take the members table down with it. An empty panel with a message is telling you that specific fetch failed - the rest of the page is still accurate.