Form on a published Capable Site cannot be filled in

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

What you are seeing

A form on a published Capable Site cannot be filled in.

#Why it happens

By design. A published site renders both macros as read-only disabled controls with no Save button, and user, space and page fields degrade to "This <type> field isn't available on published sites.".

#What to do

There is no way to collect responses from a published Capable Site. Use the Confluence page itself, with signed-in readers who have page edit permission.

#Settings involved

Setting

Where

What it does

Capabilities → Forms (Visible / Hidden)

Capable global settings → Capabilities tab

Hides the Forms nav item and the Forms page byline item for everyone on the site.

Space Capability Settings → Forms (Auto

Space settings → Space Capability Settings

Per-space visibility of the Forms byline entry. Space Admin only - others see "You must be a Space Admin to change these settings.".

Capable Forms admin settings page (stand

Confluence → Apps → Capable Forms settings

The standalone Forms app ships an admin settings screen carrying the shared Capable tabs (Introduction, Features, Indexing, Migration and, where applicable, Permissions/Egress). Shown to signed-in users. There is NO Form

#Limits that apply here

Limit

Value

What happens

Pinned forms in the catalogue sidebar

10 per user

Opening an eleventh form drops the oldest.

Save retry ceiling

5 attempts, backing off 250 ms, 500 ms,

If the save cannot locate the macros in the page content it retries on that ladder and then gives up, surfacing as "Could not save form - try again".

#A few things that catch people out

  • Filling a form in the page editor writes to the DRAFT, not the published page.

Found it? Good.