Dashboard reports are the stored artifacts of what the dashboard showed at a moment. Strkr's reports library carries every saved run with a versioned export, a searchable archive, retention controls, and the audit posture finance and compliance expect. The library is the evidence trail, not a folder of PDFs on a share drive.
Most teams store reports in a shared drive that becomes archaeology within a quarter. Strkr's reports library catalogues every saved run with metadata, searchable content, and a trust signal that reflects freshness and provenance. The library replaces the drive and the email thread that search for the right version.
Every scheduled snapshot and every ad-hoc export saves to the reports library with a title, a timestamp, a producing dashboard, a dataset signature, and a run metadata record. A quarterly board report is findable five years later without a side process.
Search covers titles, authors, tenant tags, and body content within rendered PDFs. A finance director looks up every quarterly bookings report from 2024 by typing a two-word query. The library returns the right set with a readable preview on each row.
Facet filters cover producing dashboard, author, date range, lifecycle state, and tenant tag. A legal team pulls every report containing a project tag across the last two years in under a minute. The library behaves like a research tool, not a dumping ground.
Each report row shows run date, producing dashboard, author, and dataset signature. The dataset signature says whether the underlying data has changed since the report ran. Finance and audit judge trust at a glance without opening the file.
Each row carries a preview thumbnail of the first page. The viewer reads the anchor numbers from the row without opening the full report. The preview reduces false-start downloads and speeds research across dozens of reports in a single session.
Owners pin frequently referenced reports to a collection: quarterly bookings, board decks, annual retention. The collection groups the right set for a use case. New hires land on the right starting point without rebuilding the mental map.
A good report answers what the dashboard looked like at a moment. Strkr's versioned exports lock the data snapshot, the dashboard version, and the applied filters together so a stored report always matches what the viewer saw at run time. Re-rendering an old report returns the same output byte for byte.
Each report locks a snapshot of the underlying dataset at the moment of the run. The report can be re-rendered from the snapshot without pulling live data, so re-opening a quarterly report two years later shows exactly what the quarter closed on.
The report references the dashboard version used for the run. If the dashboard evolves, the report still carries the version it was generated against. Readers see the layout that was in production when the report ran, not a current layout with a stale snapshot.
The filters applied at run time (date range, owner, region, custom predicate) store with the report. A reader opening the report sees exactly what slice was captured. The report is not ambiguous about scope.
Re-rendering a stored report produces an identical output byte for byte. The library serves the stable artifact rather than regenerating against a drifted source. Audit teams get the artifact they can hash and sign.
Each report carries a stable reference ID the organization can cite in meeting minutes, external filings, or audit submissions. The ID resolves to the exact artifact in the library. Finance teams stop referencing moving targets.
Enterprise tenants can enable digital signing on exports for high-stakes reports. The signature validates the report has not been tampered with after export. Auditors verify the artifact independently rather than relying on a report-side promise.
Enterprise reports carry retention requirements. Financial reports often require seven years. Healthcare reports often require six. Operational reports may retain for ninety days. Strkr's retention policies apply per report class, per tenant, per role, so the library honors policy without a manual cleanup job.
Policies apply per report class. Finance reports retain for seven years. Healthcare operational reports retain for six years with HIPAA posture. Sales operational reports retain for 90 days by default. Each class carries the right default and admins override per tenant.
Legal teams flag specific reports or classes with a legal hold. Flagged reports do not expire until the hold is lifted. Discovery and litigation workflows get the artifacts they need without racing a retention clock.
The admin console carries a preview of reports scheduled to expire in the next 30 days. Legal and compliance teams review the list before the policy fires. A report that should be retained longer gets flagged before deletion.
Every automated deletion logs into an immutable audit trail with the report ID, the applied policy, and the deletion timestamp. Compliance teams produce evidence that retention is enforced, not just configured.
Owners can export a report to an external vault or long-term archive before the retention policy expires. The export honors the audit trail with a destination record. Nothing disappears without the organization's consent.
Reports store in the tenant's configured data region. European tenants keep reports in European regions. Canadian tenants keep reports in Canadian regions. Residency travels with the report, not just the dashboard that generated it.
A reports library is only trustworthy if access control is enforced on every artifact. Strkr enforces role-based scoping, named-user access lists, and expiring external shares on every report in the library. A report viewer sees what they are cleared to see and nothing more.
Each report carries a role access list. Finance reports surface to the finance role. Executive reports surface to the exec role. The library view respects what the viewer is cleared to open, so a reader never sees a title they cannot access.
Admins add specific individuals to a report's access list beyond role-based access. A board member who is not in the role library can still read the quarterly board snapshot. The access record logs so the audit trail shows who was granted explicit access.
External shares generate scoped read-only links to a report with a configured expiration (24 hours, 7 days, 30 days). The link enforces the scope in the rendered output. Customers, partners, and board members read the artifact without a Strkr login.
Every download of a stored report logs into the audit trail with the downloader's identity, the timestamp, the report ID, and the context (library browse, link click, API call). Compliance teams see exactly who accessed which artifact when.
Admins enable watermarking on sensitive report classes. The watermark carries the viewer's identity and the download timestamp. A leaked report traces back to the viewer who exported it, which deters casual sharing of restricted artifacts.
An admin revokes access to a report, a class, or a external share with one click. Access terminates immediately across all channels. External links expire within seconds of revocation. The library stays under administrator control.
The reports library carries the compliance posture of the rest of the Strkr platform. HIPAA with BAA, SOC 2 Type II in progress through 2026-Q4, encryption everywhere, and an open API so other systems can integrate with the library when the organization needs it.
Strkr is HIPAA compliant with a BAA available. Reports containing PHI store with encryption at rest, role scoping, and audit trails. Healthcare customers run the reports library on real patient operational data within the right boundary.
SOC 2 Type II is in progress through 2026-Q4. The reports library produces access logs, retention records, and change evidence auditors expect. Enterprise buyers get the posture their security program requires.
Stored reports encrypt at rest with AES-256. Report fetches travel over TLS 1.2 or newer. Credentials for the library and the download pipeline live in KMS. Encryption is on by default across the pipeline, never a tenant-side toggle a team could miss.
The reports library is reachable over an open API. A compliance system fetches reports on a schedule. A finance system cites report IDs programmatically. The library is a shared asset rather than a locked box inside the dashboard surface.
Enterprise tenants generate thousands of scheduled reports per week. The library handles the volume with horizontal scaling on the storage and rendering layers. Infrastructure is Strkr's problem, not the tenant's.
High-priority reports can deliver as a Strkr Messaging link to the owner's phone. The link opens the full report in a mobile-friendly rendering. Delivery meets the owner where they are, even when the inbox is swamped.
The reports library earns daily and quarterly use through a handful of concrete patterns. Strkr's library carries six established patterns that cover the majority of real archival needs: the quarterly bookings run, the annual compliance package, the per-customer QBR archive, the incident postmortem file, the executive series, and the audit trail bundle.
A finance team runs the quarterly bookings dashboard the week after quarter close and saves it to the library as the quarter's signed artifact. The report carries the dataset signature so the controller can confirm the numbers at any point in the future. Audit teams cite the ID.
The compliance package pulls every finance, security, and operations report from the trailing year into a single collection with the audit trail attached. The auditor receives the collection through a scoped external share. Evidence production becomes a few hours instead of weeks.
Each strategic account carries a folder in the library with the quarterly QBR snapshots. CSMs walking into a QBR open the prior quarter's snapshot alongside the current one. The customer sees continuity across the relationship rather than a repeated setup.
When an incident closes, the incident commander exports the incident-command dashboard with the final state and files it to the library tagged with the incident ID. Future postmortem reviews and pattern analysis pull from the file set rather than reconstructing the incident from logs.
The weekly leadership digest archives automatically into the library. Executives looking back at how the business trended through a quarter pull the series rather than relying on memory. The archive is searchable and the trajectory tells a story.
When legal or compliance opens a inquiry, the admin pulls an audit trail bundle: all dashboard changes, access events, and report deliveries over the inquiry window, exported with hashes. The bundle is self-contained evidence rather than a scattered set of CSV files.
A reports library that ships only PDFs serves one audience. Strkr's library supports six output formats so stored reports reach every reader in the right form: PDF for formal filings, CSV for data teams, PowerPoint-ready layouts for presentations, HTML snapshots for in-browser viewing, interactive drill links for exploratory use, and signed JSON for programmatic verification.
PDF outputs render the dashboard with a cover page, timestamp per page, and signed metadata appendix. The format travels through enterprise document management systems cleanly. Board materials and audit packages produce in the right form on the first try.
CSV exports carry the underlying rows behind every tile. Data teams load the CSV into their favorite analysis tool. The export respects the applied filters so the CSV matches what the dashboard viewer saw. Nothing is reconstructed by hand.
PowerPoint-ready exports render each dashboard section as a slide with the title, chart, and short caption. Presenters open the deck, add their narrative, and present. The library saves the hours otherwise spent copying charts between tools.
HTML snapshots render the report as a static page viewable in any browser without a Strkr login. The snapshot is useful for sharing with external auditors or embedding in internal knowledge bases. The static form preserves the exact state at the time of the run.
Each stored report carries an optional interactive drill link that opens the frozen snapshot in a Strkr view with the same filters applied. Readers who want to explore the underlying records can do so from the stored artifact without opening a separate live dashboard.
Signed JSON outputs carry the full report payload with a digital signature. Downstream systems verify the signature and consume the data programmatically. Compliance pipelines pull signed JSON into their audit systems rather than parsing PDFs with brittle text extraction.
Dashboard reporting is the delivery layer: scheduled snapshots, subscriber lists, threshold alerts. Dashboard reports is the storage layer: the library of saved runs with search, retention, access control, and audit trails. Reporting ships the artifact; reports stores it.
No by design. Stored reports are frozen snapshots. Re-opening a stored report returns the exact artifact that ran at the time. To get current data, run the dashboard again as a new report. The two artifacts coexist in the library, each with its own run timestamp.
Retention applies per report class. Finance reports default to seven years. Healthcare operational reports default to six years with HIPAA posture. Sales operational reports default to 90 days. Admins override per tenant. Legal hold flags specific reports as exempt from expiration.
Yes. Full-text search covers report titles, authors, tenant tags, and body content within rendered PDFs. A finance director finds every quarterly bookings report by typing a two-word query. Facet filters narrow by date range, author, producing dashboard, and lifecycle state.
Yes. HIPAA with BAA for healthcare. SOC 2 Type II in progress through 2026-Q4 for enterprise security programs. Encryption at rest and in transit. Residency controls per tenant. Legal hold for discovery workflows. Audit trails on every access.
Yes. External shares generate scoped read-only links to specific reports with configured expiration windows. Watermarks optionally identify the viewer on the exported artifact. Access revokes with one click across all channels.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
