The job of this console
Pick a domain, add fields, preview, save. Schedule on Scheduled reports. If the number is wrong, fix the source entity.
Analytics · Builder
Report Builder
Ad-hoc definitions over canonical domains — saved views, not a warehouse you load by hand and not Project → Reports catalogs.
Scroll to Flowcharts. Scenario: Build a custom analytics report.
Ad-hoc definitions
Saved queries, not a private warehouse
Report builder lets you assemble dimensions on people, projects, and finance you already have. The definition is not a second ledger.
Analytics → Report builder
Route
/analytics/report-builder
Org flag reportBuilderEnabled
Executive · Finance · HR · Project Manager · Admin
Seat at the table
Executives, finance, HR, project managers, admins with reportBuilderEnabled. Masking still applies.
The working rhythm
Define, preview, save, optionally schedule, share the output not the raw grant.
Moments that bring you here
A board appendix the packs do not cover. A one-off slice. Replacing a spreadsheet extract.
ⓘ
Definitions only
Persona masking on export. Project → Reports remains the operational catalog. No unmasked salary dumps.
Flowcharts
1 — Define then preview
Pick a domain, add fields, preview, save. Schedule separately.
flowchart TD
A[Open Report builder] --> B[Choose domain]
B --> C[Dimensions / metrics]
C --> D[Preview]
D --> E[Save definition]
E --> F[Optional schedule]
- 1OpenAnalytics → Report builder.
- 2DomainPeople, project, finance, etc.
- 3PreviewChart or table.
- 4SaveSchedule on Scheduled reports.
Overview
Report builder stores definitions that query canonical domains. Project → Reports is the operational catalog. Exports must apply persona masking. This is not a place to paste a CSV as truth.
How to use
1. Respect grants
A report cannot unmask salary for a persona that lacks it.
2. Operational vs ad-hoc
Delivery exports may already exist under Projects → Reports.
3. Schedule is sibling
Do not expect cron on the builder canvas itself if the org uses Scheduled reports.