Finding your way around Reporting
Every report in one place, all sharing a header, a period and a team scope. How to navigate the set and share a view without describing it.
Product walkthrough
See it in RevTech
See how to move through the reporting library, open the right operating view, and follow a number into its underlying records.
An index, not a report
Reporting is the entry point to every report in one place — programs, forecast, performance, pipeline, planning, team, customer and marketing — each card opening a report on its own route. It is deliberately an index: the hub itself shows you nothing about your business.
The grid has a reading order rather than an alphabetical one, and RevPlay Impact leads it because RevPlays are the motion the rest of the reports are downstream of. Search it rather than scrolling. Once you know the two or three reports your role actually uses, the hub becomes a place you pass through, and the reports themselves become bookmarks.
Not every report has every dimension
Some reports carry a team filter and some do not, and the difference is a property of the underlying data rather than an inconsistency in the interface. A report without a team dimension does not show a team control, instead of showing one that quietly does nothing.
Same for the period controls. A report that is a now-state snapshot — Customer Health, for example — has no fiscal quarter to scope to, so it does not offer one. Renewals goes the other way: it reads tenant-wide, so it shows no team control.
Sharing a view
Report scope, period and filters travel in the URL. That makes a configured report a link, and it removes the most common source of confusion in a recurring meeting: two people applying filters from memory and getting them slightly different.
Paste the URL of the report you are presenting into the calendar invite. It is a small habit that reliably saves the first three minutes of a review.
When a report is not there
The cards on the hub are gated by role. A report a colleague can open and you cannot is an access question, not a missing feature, the same way an agent card missing from the AI Agents hub is.
Access is defined in Roles & Permissions, where section access and record scope are set together. See the administration guide for how that model works.
What to take away
- Reporting is an index, not a report. Search it rather than scrolling it.
- Every report shares the same header: scope, period, and when the data was last updated.
- Filters live in the URL. Send the link instead of describing which filters to apply.
- The cards you can see are the ones your role grants. A missing report is a permission question.
Try the demo.
See agents carry the repeatable work of GTM across sales, marketing, customer success, and RevOps. Every action prepared, reviewed, and recorded. Fictional data, real product.
Explore the demo