How report exports work
This page explains the report export that admins can use today, how list exports differ, and how permissions protect member details.
The short version
Section titled “The short version”An authorized admin can download a rendered report as CSV when it has at most 1,000 rows. A larger report is refused rather than queued. Members and Payments lists have separate export jobs whose status shows in the app (Members: Export history on the Export members page; Payments: the Transactions page). A Members export sends no email; a Payments export emails you when it is ready, with a pointer to its status on the Transactions page (the email doesn’t contain the file). Members list-file delivery has known gaps (below). Board members can view aggregate pages but cannot export from the Board portal.
How it works
Section titled “How it works”Export a rendered report
Section titled “Export a rendered report”Open a rendered report and select Export. CSV is the currently offered format. Choose the columns to include, leaving at least one exportable column, then confirm. The file downloads immediately for a report of 1,000 rows or fewer. For more than 1,000 rows, the dialog says how many rows the report has and that exports are limited to 1,000 rows, and Export CSV stays disabled; nothing is queued or emailed.
An admin who lacks reports:export does not see the Export action. Current rendered reports use aggregate columns. If a future report offers member-detail columns, an admin without reports:export-pii cannot include them; if a request still names those columns, the result explains the omission.
Export a Members or Payments list
Section titled “Export a Members or Payments list”Members lists list CSV, Excel and XML choices. The current Members worker produces a CSV file regardless of which choice is selected, so use CSV for a reliable format. Payments lists offer CSV and Excel; both produce the same CSV file, which you download from the export’s status on the Transactions page. Check a Members job under Export history on the Export members page and a Payments job on the Transactions page. A Members export sends no email. A Payments export emails the admin who started it when the file is ready, with the number of payments, when the file expires and a pointer to its status on the Transactions page; a failed Payments export sends no email. The Members delivery gaps are with the backend owner.
These list exports use their own permissions, contacts:export and payments:export. They do not use the report’s member-detail checkbox.
Spreadsheet safety
Section titled “Spreadsheet safety”The working Members and rendered-report CSV paths escape cells beginning with =, +, -, or @ so spreadsheet software does not treat them as formulas. The report export response does not provide an escaped-cell count, so the dialog cannot show a reliable count notice today. Excel list delivery and typed-cell behavior are pending correction.
Board access
Section titled “Board access”The Board portal shows aggregate information on screen and offers no export action. Board members lack reports:export. An authorized admin may export a separate, available aggregate report as CSV and share it manually if that report meets the Board’s need. There is no current export of the Board dashboard or financial summary with its exact totals and jurisdiction breakdown. Scheduled delivery to board recipients is planned for M2 and is not available today. Receiving a separate report does not give the Board role an export grant.
Why it works this way
Section titled “Why it works this way”Export permission depends on the source and role. The report column rule protects member details. Escaping spreadsheet-leading characters prevents formulas in exported data from running when opened in spreadsheet software.
Edge cases & boundaries
Section titled “Edge cases & boundaries”- PDF is not currently offered by any of these export surfaces.
- A rendered report over 1,000 rows is refused; its queued email path is a later reporting capability.
- Members and Payments list jobs can fail or expire. Check their status under Members Export history or on the Transactions page; a completed status alone does not guarantee a usable file on the current Payments path.
- The Export action is absent when the role lacks the source’s export permission, including on Board pages.