Confluence labels
Forms adds Confluence global labels to customers' pages as the app: capable_forms_page on every page carrying a form, plus one capable_forms_{formId} per form. Labels matching that prefix that Forms no longer wants are deleted. Only labels matching those patterns are ever touched.
#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 |
Publish the page and fill the form in | The published Confluence page |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
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. |
#Worth knowing
In the Suite on Standard without the confluence.forms flag, Forms is effectively invisible: the nav item is replaced by an upgrade promo, the search panel is filtered out, and every type except single-line text refuses to render standalone.
Product-event indexing carries a licensed-site filter: on an unlicensed or expired install, answers still save but the catalogue, labels and registry stop updating entirely.
#Related
Better with company.
