# 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

* Form reference macro - retired.
* Date, time, file-upload, rating, signature and rich-text input types - none exist. The types are exactly the ten listed. A code comment mentioning a future "date" type is a forward-compatibility note about the render fallback, not a released feature.
* A separate response store, submission log or response history - responses are the page.
* Anonymous or external submission - anonymity short-circuits to read-only before any permission check, both server operations require a signed-in account, and a published Capable Site renders forms as disabled read-only controls with no Save.
* Notifications on submission - no notification path exists anywhere in the capability.
* Retention policy, response deletion, per-form access control and a "close this form" / deadline state - none exist. Deleting the page is the only removal.
* A Forms-specific settings tab - Forms declares no capability settings, so no tab is built. (The standalone app DOES ship an admin settings page carrying the shared Capable tabs; there is simply no Forms tab within it.).
* Cross-form reporting, charting or aggregation - the catalogue's Responses column is a page count and the responses view is a flat per-page table.
* Any Rovo agent or MCP exposure - no Forms tool or action appears in the Suite's Rovo blocks. An agent cannot create or read forms.
* Any Forms entry in the migration wizard or third-party macro mapping.
* Unreleased UI: a forms CRUD page, a form response page, a form CRUD component, a form response view component and a form insights view all exist as files but have no importers and no routes. There is no form-insights or form-CRUD surface in the product.
* The label query works because label is Confluence's own built-in field; Forms merely offers it as a hint row in Capable's CQL builder.

ℹ️

**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

[LimitsThe hard numbers.](https://help.gocapable.com/forms/limits.html)

[How it worksWhat is available.](https://help.gocapable.com/forms/how-it-works.html)

---

_Better to know now than hunt for a switch._