Reports dashboard

GreekManage has a standalone Reports page that generates narrative summaries — quarterly chapter reports, annual org reports, membership/compliance/financial overviews — using your own data plus the org's configured AI provider. It lives at Org → /reports (direct URL — not currently linked from the sidebar in v0.62.1).

Most module-level numbers and tables stay inside the module they belong to. This page is the index of everything reporting-related you can reach as a national admin.

Who can use this

Available to: Org / National Admins. Some surfaces are also available to regional admins and chapter officers within their scope; that's noted per surface below.

AI configuration required

The Reports dashboard generates its summaries using your org's AI provider. If you haven't configured one — see AI Services — provider config — generation will fail with a configuration error. Reports do not work offline or without an active API key.

The standalone Reports dashboard

What you see

When you navigate to Org → /reports, you get two cards:

1. Generate Report. Pick a report type, optionally constrain it to a date range, and click Generate Report.
2. Report History. Every previously requested report, newest first. Each row shows status (Pending, Processing, Completed, Failed), who requested it, when, and a download/view button once it finishes.

org reports page with generate form and history list

Report types

The dropdown offers exactly five report types in v0.62.1:

Type	What it covers
Membership Overview	Member counts; active vs. inactive breakdown by chapter
Quarterly Chapter Report	Chapter-by-chapter performance for a given quarter (date range matters here)
Annual Organization Report	Full-year summary across the org
Compliance Summary	Compliance status across all requirements
Financial Summary	Invoice and payment status overview

There are no other types in the UI. If you need something not in this list, the closest workflow is to export raw data from the relevant module and analyze externally.

Step-by-step: generate a report

1. Choose a report type from the dropdown.
2. (Optional) Set a Start Date and End Date. For Quarterly and Annual reports this is required for meaningful output; for Membership Overview and Compliance Summary it's optional and defaults to "current state."
3. Click Generate Report. The card appears at the top of Report History with status Processing.
4. Wait. Generation runs in the background; the page polls and updates the status automatically. Typical generation time is a few seconds to a minute depending on org size and AI provider latency.
5. When the status changes to Completed, two buttons appear: View Report (expands the report inline) and Download (saves it as a .md Markdown file named <report_type>-<date>.md).

Errors and edge cases

Status	What it means	What to do
Pending	The job is queued but not yet picked up by the worker.	Wait. If it sits for more than a minute or two, see the AI configuration callout above.
Processing	Currently running.	Wait.
Failed	An error occurred — the error message is shown in red on the card.	Common causes: AI key not configured, AI key invalid, AI provider rate-limited, no data in the requested date range. Read the error text and act accordingly.
Completed but empty body	The AI provider returned nothing meaningful (often a date range with no underlying data).	Widen the date range or pick a different report type.

Per-module reporting surfaces

The standalone Reports page is one of several reporting surfaces. Some modules ship their own richer reports tabs; some surface data inline on the module's main page; some only expose CSV/XLSX export.

Module	Where	What's there
Members	Org → Members	Directory listings, search, saved views, custom-field summaries; CSV/XLSX export
Foundation	Org → Foundation → Reports	Campaign performance, donations, donor giving, tax receipts. This is a separate, full-featured dashboard — see Foundation overview
Compliance	Org → Compliance	On-time rates, per-chapter status, per-requirement performance; per-chapter dashboards
Elections	Org → Elections → results	Vote totals per position, winners; XLSX export
Learning	Org → Learning	Course completion and enrollment dashboards
Retention	Org → Retain	Retention snapshots, alerts, survey responses
Billing	Org → Billing / Org → Settings → Dues & Billing	Per-chapter invoices, rate history, payment records

Not every module ships a dedicated "Reports" tab in the UI. Many surface reporting inline on the module's main page rather than as a separate route. If you're looking for a particular metric and can't find it, check the main page of the module first.

What officers and regional admins see that you don't (and vice versa)

• Chapter officers do not see the standalone Reports page at all. They have access to their own chapter's compliance dashboards, billing detail, election results for their chapter, and learning completion — all scoped to their chapter.
• Regional admins see most of the same per-module surfaces you do, scoped to chapters in their region. They do not currently have a standalone Reports dashboard equivalent.
• Only org admins can generate the AI-assisted org-wide reports on /reports.

Mobile differences

The standalone Reports page works on mobile via the iOS and Android apps, but the experience is awkward — the inline report viewer expects a wider viewport and Markdown rendering is plain <pre> text. For anything beyond glancing at a recent report's status, generate on desktop, then download the Markdown file.

Per-module surfaces vary: Members and Compliance render well on mobile; the Foundation Reports dashboard's charts are desktop-first.

Troubleshooting

"AI provider not configured" or similar. Open Org → Settings → AI Services and confirm a provider is set up and verified. See AI Services — provider config.

The page exists but I can't find a link to it. The standalone Reports page is reachable by direct URL only in v0.62.1 — type /reports after your org base path, or bookmark it. Foundation reports have a dedicated sidebar item; the standalone page does not yet.

The report mentions chapters or numbers that look wrong. AI reports occasionally hallucinate. Always cross-check the underlying data in the relevant module before forwarding a report externally — these are summaries, not authoritative reports.

A previously generated report is missing from history. Reports persist for the life of the org's data. If a row vanishes, it's almost certainly because the user who generated it was disabled or removed; the row may still exist but be hidden by a filter on requested_by. There's no archive surface for deleted-user reports in the current UI.

Related

• AI Services — provider config — sets the provider used by the Reports dashboard
• AI Services — content scope toggles — controls what data the AI can access
• Foundation overview — the Foundation module's own Reports dashboard
• Reports, exports & audit logs — the broader exports + audit log index

Last verified against v0.62.1 (2026-05-11).