What is not available
Every product has a shape people expect it to have, and this is where this one differs from that shape. Nothing here is coming in a particular release; it is simply not offered today.
The page exists so you can plan around it rather than spending an afternoon looking for a switch.
#Not available
No macros.
At-risk / self-harm phrase detection.
Word-count buckets (under 50, 50 to 300, 300 to 1000, 1000+). They are collected by the weekly sweep and stored on every snapshot, but no chart or view displays them.
Daily trend granularity.
Configurable empty-page word threshold, no-headings minimum word count, custom inappropriate words and custom non-inclusive terms. Present in the stored settings model but with no control on the Rules page and (apart from the auto-fixers reading the custom lists) no effect on detection.
The input type exists but no route uses it; the Top-spaces chart is built in the browser from the full rollup and sliced to 10.
A single-space rollup writer (upsertSpaceRecord). Exported but never called; the sweep rewrites the whole rollup at each checkpoint instead.
A 'quality:enabled' runtime flag. The string appears in every app's environment flags but nothing reads it, so it is not a switch anyone can rely on. It is also present in the standalone client environment but not the standalone server environment, with no runtime effect either way.
A Quality settings tab in Confluence global settings or space settings. Quality declares no global-settings or space-configuration view of its own; the standalone app's "Capable Quality" settings entry renders the shared Capable settings shell, not a Quality-specific page.
It is harmless and should not be documented as a feature.
A Capabilities tab in the standalone app. Both apps honour the site-wide "hide Quality" app property, but the screen that writes it is only rendered for the Capable Suite. The standalone app has no way to set it.
"Always" space visibility in the standalone app. The standalone byline condition never reads the alwaysOn property, so "Never" works there but "Always" does nothing.
Migration tooling in the standalone app. The Migration tab is explicitly excluded, so Capable Quality standalone can report third-party macro migration opportunities but offers no way to act on them.
A dedicated background queue for Quality. Aggregation is an event routed inside the app's single shared 900-second queue consumer, not a queue of its own. It competes with content indexing.
Export of the Dashboard, and any alerting when a Priority rule fires. There is no export, no email or Slack notification and no webhook on the Quality side. The only export is the search table's CSV/Excel export of the Quality column, which exports the raw issue count rather than rule names.
A Confluence space-settings sidebar entry in the standalone app.
None of this is a bug to report. If one of them blocks you, tell us: customer demand is what moves them.
#A few things worth knowing
If one of these is the reason you are evaluating the product, say so before you buy rather than after.
The list changes with each release, so check the release notes before assuming it still applies.
Where the app's own wording differs from this page, believe the app.
#Related
Better to know now than hunt for a switch.
