A designer, not a blank canvas.
Start with a wizard or a layout. Bring tables, charts, images, page headers, and reusable sections into one report.
Explore the platformConnect sources, author reusable layouts, and give readers a consistent place to run their reports.
Start with a wizard or a layout. Bring tables, charts, images, page headers, and reusable sections into one report.
Explore the platformWork with database queries and file-based datasets. Map fields explicitly and review the result before saving.
Explore the platformPreview and export reports to PDF, with additional Word and Excel options for different downstream needs.
Explore the platformCombine reusable page structures, headers, footers, images, and grouped records. Keep layout and field binding separate.
Explore the platformSave revisions and review changes. Recovery helps retain unfinished work; permissions decide who can edit or run a report.
Explore the platformUse configured AI providers to propose report changes. Review the result and keep control of the saved report. Provider setup is required.
Explore the platformUse PDF when page layout matters. Choose data-oriented or editable formats when your reader needs to work with the result.
Illustrative report · Synthetic data · H1 2026
| Region | Revenue | Orders | Share |
|---|---|---|---|
| North | $92,400 | 462 | 37.2% |
| Central | $81,600 | 431 | 32.8% |
| South | $74,500 | 391 | 30.0% |
Give each organization its own accounts, reports, uploads, credentials and AI settings. Platform administrators create, manage or suspend organizations; organization administrators manage their own team.
Share an organization-specific sign-in link with its team. User accounts belong to that organization.
Discuss your setupKeep report catalogs, managed files and configuration separate between organizations within the same application service.
Plan your deploymentManage organization lifecycle centrally while letting organization administrators manage their own users and settings.
Discuss administrationConfigure access controls to suit your deployment. These are product controls, not a claim of independent security certification.
Use administrator, designer and reader roles alongside report permissions to control who can work with reports.
Evaluate permissionsUse integration credentials and configured embedding origins to define access from other applications.
Explore integration controlsManage organization connections and credentials separately. Configure HTTPS and backup procedures for your installation.
Review deployment planningUse report history and recorded user activity to support review and operational follow-up.
Review saved revisions, who made changes and when they were recorded.
Explore the report lifecycleInspect recorded sign-in and application activity when reviewing how the workspace is used.
Discuss activity requirementsInspect data, bindings and the rendered report before saving or sharing the final result.
Explore report examplesUse application controls for organization backup and recovery, with an operational plan for the whole installation.
Create organization backups and download them for your retention process.
Plan backupsManage scheduled backups and restore workflows with the appropriate administrative access.
Discuss recovery requirementsPlan separate protection for every organization and the installation configuration, with an encrypted off-server copy.
Read deployment guidanceBring supported design structure into the reporting workflow. Import results depend on the source frame and supported elements.
Configure access to a Figma file and inspect available frames before importing.
Try the design workflowImport a supported frame or use the Figma exporter workflow to create a reusable template.
Explore reusable templatesAssign datasets and fields in the report designer. Check typography, images, layout and export results before using the template.
See sample reportsThese example roles explain the product workflow. Actual access depends on the permissions configured for each report and organization.
Reader example selected
A reader uses the reports they are permitted to access.
Design access does not make someone an installation administrator.
An organization administrator manages their team and settings; platform administration is separate.
Each organization has its own accounts, report catalog, managed files and configuration within the installation.
Northstar team example selected
A team works with its own reports and configuration.
Switching this illustration changes the example, not an application session.