Reports

A report is a saved question about your data — “active members by city”, “revenue this quarter”, “events with no registrations”. Reports are for everyone, not just administrators: anyone can build them over the data they’re allowed to see, run them live, and pin them to dashboards.

Three kinds of report

List reports show matching records as a table — you choose the columns, the filter and the sort. Ideal for working lists: “unpaid members”, “this month’s events”.
Aggregate reports summarize: group by a field and count, sum or average another. They render as totals, rankings and charts — “members per profile”, “donations by month”, “average payment per campaign”. Group by two fields and you get a pivot table — say, registrations by event and by profile.
Progression reports chart how things build up over time as a line chart. Pick the date field that places each record on the timeline, a measure (count of records, or the sum of a number field), and optionally a field that splits the chart into one line per value — one line per event, per campaign, per status. Lines are cumulative by default: each grows as records land on their date. Hovering shows, for every line, the running total and how many records it took at that day.

Anchored timelines (“days before the event”)

A progression report’s timeline can be calendar dates, or — when the lines are split by a reference field — days relative to a date on the referenced record. Anchored on the event’s date, payments for three different events plot as three lines over “days before the event”: each starts when its first payment lands (60, 50 or 30 days out), grows payment by payment, and they all meet at day 0 — the event date — at their final totals. That’s how “how do ticket sales ramp up before our events?” becomes one readable chart even when the events themselves are months apart. An optional window caps how far back the lines reach, and the chart keeps the top lines by final total so it stays legible.

Building a report

Open Reports & dashboards from the sidebar and click + New report.
Pick the record type the report is about.
Choose the kind — list, aggregate or progression — then set your filter (the same filter editor as lists, including the ”= me” shortcuts), and the kind’s own settings: columns + sort, group-by + measure, or date field + measure + line-per + timeline.
Preview as you build, then Save.

The report runs live every time it’s opened — it’s a question, not a snapshot.

A report doesn’t have to stay inside one type. In the Related types section, join another record type:

Via a reference field — payments joined to the person they point at, in either direction.
Via a relationship — people joined to the events they attended.

The joined type’s fields then appear in every picker — filter, columns, group-by, measure — labeled with their type. That’s how you build “sum of payments grouped by the member’s city” without touching a spreadsheet. A distinct toggle removes duplicate rows when one record matches several joined ones.

A type joined via a relationship also offers a Relationship type entry in those pickers: the name of the relationship that linked the two records. Join people to campaigns through any relationship, group by campaign name and then by relationship type, measure count — and one report reads “Reacted to: 12, Unsubscribed: 3” per campaign. It filters like any text field (“Relationship type = Reacted to”). In an advanced query it is the relationshipType pseudo-field of the joined alias, for example GROUP BY a.campaignName, p.relationshipType.

Advanced queries

For questions even joins can’t express, power users can switch a report to an Advanced query — a validated, SQL-like text language with the same safety and permissions as everything else. Most people never need it.

Running and drilling

Open any report from Reports & dashboards — it opens in a clean view mode, with editing reserved for those allowed.
On an aggregate report, click a group, bar or pivot cell to drill into the underlying records — the list opens pre-filtered to exactly that bucket, so the numbers always reconcile.
On a list report, sort by clicking column headers, refine the filter, and export the result.

Reports respect your permissions

A report always runs as you: records and fields you can’t see don’t appear in your results, whoever built the report. Two people can open the same report and correctly see different numbers. Columns you can’t see are simply dropped, so the report still renders.

To control who can open a report at all, see Sharing.