Capable Sites static export
A published Capable Site renders both macros as READ-ONLY, disabled HTML controls: text, long text, number, radio, checkbox and select all render disabled with their saved values; a URL field renders as a plain link (an unsafe stored URL is never made into a live anchor); and user, space and page fields degrade to the note "This <type> field isn't available on published sites." The Form container emits only its body - no form name heading, no Save button, no submission from a published site.
#Where you do it
Task | Where |
|---|---|
Insert the form container | Confluence page editor, macro browser |
Place fields inside the form body | Confluence page editor, inside the Form macro's body region |
Browse every form on the site | Confluence → Apps → Capable Forms (or the Forms entry in the Capable navbar) → All forms |
#Settings that affect this
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. |
#Related
Better with company.
