Tables, Charts & Reporting Workbench | HTF

A useful report, step by step.

Product guide. Learn the reporting workflow and supported limits. Check the product page for Marketplace availability.

Create your first report

1. In Confluence, open a space, then Apps → Reporting Workbench | HTF. You must be signed in and able to access the page that will own your report.
2. Enter the saved page's link or numeric page ID and select Check page access. Editing requires permission to update that page. A draft page must be published or saved first.
3. Give the report a clear title, such as “Monthly delivery budget”. Open the import step and choose a supported file or paste CSV, TSV or JSON. Review the replacement confirmation before continuing.
4. Check column types, missing values and formula errors. The first row should contain column names. Supported formulas use familiar cell references such as =SUM(B2:B4).
5. Filter or sort the rows you need. To compare totals, open the pivot step, select a grouping column, a numeric measure and an aggregation.
6. Select Save release. Wait for Saved and up to date before leaving. Unsaved changes exist only in the current browser view.

Saved releases remain available after you reopen the app. Unsaved drafts do not survive a browser refresh.

Check a simple example

Paste the following fictional CSV. Group by Team, measure Amount and choose Sum. The expected results are Platform 200 and Operations 50.

Team,Amount
Platform,120
Platform,80
Operations,50

The interactive fictional demo is also available without an account. Its changes and saved releases disappear on refresh. It does not test Confluence storage, permissions or billing.

Review changes and keep control

The release view lets you compare the draft with saved data. Choose a unique matching column when rows have moved. At most five saved releases are retained. Restoring an older retained release creates a new current release. If another editor saves first, keep your draft and review the latest release before trying again.

Reports use the permissions of their owning Confluence page. All fields in a report share that access; there is no private-cell permission. Referenced report pages are checked separately when data is requested. Removing someone's page access is the way to revoke access to that page's reports. Previously viewed browser data and downloads cannot be recalled by later permission changes. Fresh requests recheck current access.

Delete report requires confirmation and removes the current report and its retained releases, not the Confluence page. Export any data you need first.

Known accounts and privacy cleanup

Native table imports retain the account identifiers attached to Atlassian mentions. For uploaded or pasted content about known Atlassian accounts, open Known Atlassian accounts in this report in the overview, enter the actual account identifiers separated by commas, and select Attribute these accounts. Names and email addresses are not account identifiers. Do not guess an identifier or add the editor merely because they imported the file.

Attribution follows the report through edits, up to five retained releases, restoration, references and materialized joins, pivots or query results. Removing a cell or reference does not remove historical attribution. Use fictional data when learning this workflow.

A privacy update or account closure can permanently delete the whole affected report, all retained releases and tracked materialized copies, including unrelated information mixed into them. There is no undo. Original Confluence pages and unrelated reports remain. Reports that reference an erased source cannot return its data. Previously viewed browser content and downloaded files cannot be recalled.

The app retains a small hashed reporting/status marker while the installation's Forge storage is retained so old drafts cannot restore erased data. The marker can be linked using the original account identifier and is not anonymous. See the product privacy notice for its purpose and retention. Deleting a report does not remove that marker.

If a report contains personal information without a known Atlassian account mapping, contact your Confluence administrator and follow your organization's privacy-request process. Permanently delete affected reports and identify any separate app-managed copies. Editing a current cell alone leaves earlier retained releases in place. Handle the original Confluence pages and exported files separately.

A privacy check can temporarily prevent saves involving the accounts being checked. Keep the draft and retry later. If reporting becomes overdue, fresh access to the affected tracked report is blocked until its privacy check completes. If a save exceeds privacy-worker capacity, or the app asks for review of the reporting period, keep the draft and contact your administrator or support. Do not repeatedly retry or change account attribution to bypass the message.

Supported formats and limits

• Datasets: up to 2,000 rows, 50 columns and 10,000 cells, subject to the report-size limit. A report can reference five saved sources. Each page can hold 20 reports.
• Files: CSV, TSV, JSON and supported XLSX worksheets. XLSX files are limited to 5 MB compressed and 20 MB expanded. Merged cells, shared formulas, VBA, external links and workbook styling are not supported.
• Calculations: 48 documented deterministic functions. Unsupported functions return visible errors. This is not universal Excel compatibility.
• SQL: a restricted, read-only SELECT over the supplied report data. It does not connect to a database or execute writes or arbitrary scripts.
• Saved report: up to 300 KB of normalized report data and 200 KB in its compressed storage record. A shorter dataset can still exceed these limits if cells contain long text.
• Charts and joins have additional category, series and computation limits. Filter or split a report when prompted.
• Reports with known-account attribution also require enough privacy-worker capacity for Atlassian's reporting period. This depends on the installation's attributed reports and retained subject references. A save that exceeds that capacity is rejected before changing saved data. Generic reports without known-account attribution keep the ordinary report limits.

Exports and page macros

Native acceptance has verified CSV, JSON, XLSX and SVG file contents, the configurable saved-report macro, and the report table in Confluence PDF and Word exports. PDF layout was also visually checked. The Word download contains the expected table; its layout in Microsoft Word has not been certified. PDF and Word exports contain the report table, not chart images.

Get help

Email support@howthtechnologyfactory.pro with the product name, version, action you took and a redacted screenshot or error. Keep passwords, access tokens, private report data and identity documents out of the message.

Howth Technology Factory provides product setup and defect support by email. No guaranteed response time, 24-hour service, managed reporting service or availability SLA is offered. Billing and subscription administration use Atlassian Marketplace. See the customer terms and product privacy notice.

If access repeatedly asks for consent, stop repeating the prompt and contact support. If the app page remains on a Confluence loading screen, return to a loaded space and reopen it from Apps. Do not uninstall as a routine troubleshooting step: a new installation does not automatically restore old Forge data.