# Where a response lives In the page's own content. Save writes each field's answer back into that Input macro's stored parameters in the page document, as the signed-in user. Responses therefore inherit Confluence page permissions exactly and travel with a page copy. --- ## Where you do it | **Task** | **Where** | | --------------------------------------- | ----------------------------------------------------------- | | Insert the form container | Confluence page editor, macro browser | | Give the form a Form ID and a Form name | Form macro config panel ("Configure Form") | | Place fields inside the form body | Confluence page editor, inside the Form macro's body region | --- ## 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.". | --- ## Limits that apply here | **Limit** | **Value** | **What happens** | | ------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------- | | Responses table page size | 25 rows | The per-form responses table pages 25 pages at a time using search cursors. Next/Previous and Refresh only - no jump-to-page. | --- ## Worth knowing * The responses table's field columns are derived from the 25 rows currently on screen, so paging can change the column set. * Label write failures are swallowed: the response still saves and still indexes, but the page may not appear in the label-based drill-down until the property fallback takes over. * The macros carry three different names depending on where a customer inserts them: the Confluence macro browser name (which itself differs between apps), and "Form container" / "Form field" in Capable's own insert dialog and the seeded showcase page. --- ## Related [Page content property {appHash}\_capable\_formsAnother connection.](https://help.gocapable.com/forms/page-content-property-apphash-capable-forms.html) [CQL search field {appHash}\_capable\_forms\_form\_idsAnother connection.](https://help.gocapable.com/forms/cql-search-field-apphash-capable-forms-form-ids.html) [IntegrationsEvery connection.](https://help.gocapable.com/forms/integrations.html) --- _Better with company._