Forms on your site | Doghouse SaaS Knowledge Base [Skip to content](#main) [ ![Doghouse SaaS Knowledge Base](/storage/branding/01M3N8PQ7PSDNQBBKKJM6XGW03.svg) ](https://nginx.deploy-lagoon-production.districtcms-docs.dh1.amazee.io) [Product documentation](/articles) [Roadmap](/roadmap) Toggle navigation [Product documentation](/articles) [Roadmap](/roadmap) 1. [Home](/) › 2. [Product documentation](/articles) › 3. [Forms](/articles?category=8) › 4. Forms on your site Forms on your site ================== Updated 5 days ago · 3 min read Search Search Overview -------- A form on your Doghouse SaaS site is built once, lives at its own address, and collects what people send you in one place. Everything to do with forms sits in one screen. In the admin menu, open **Structure**, then **Webforms**, then **Forms**. > **⚠️ Important:** Forms are an administrator's job. Content editors have no form permissions at all, so they cannot build a form, change one, or read what people have submitted. An editor can link to a form and place it on a page, which is covered below. --- The Webforms screen ------------------- The list shows every form on the site with its status and how many submissions it holds. Across the top are five tabs. Tab What it holds **Forms** Every form on the site. This is where you start. **Submissions** Everything submitted across all forms, in one list. **Options** Reusable lists of choices, such as states or categories, shared between forms. **Configuration** Site-wide defaults for every form. **Help** The Webform module's own support and community links. Aimed at developers, so you can leave it alone. ![The Webforms screen with its Forms, Submissions, Options, Configuration and Help tabs outlined in red, above the list of forms.](/storage/xAFCn98wfApz6M6iFIhmvst9VZJqropbSG1oGImY.png) --- What each form gives you ------------------------ Open a form and six tabs run across the top. Five of them matter day to day. Tab What you do there **Build** Add and arrange the questions. **Settings** The confirmation message, the email notifications and whether the form is open. **Results** What people have submitted, and the download. **View** The form as a visitor sees it. **Test** The same form pre-filled with sample answers, so you can try a submission. ![The top of a form in the admin, with its six tabs outlined in red: View, Test, Results, Build, Settings and Export.](/storage/HAapBGPITpvMI1RmKTZ8m3OMhXIIaoz5ZPDaxyP3.png) > **⚠️ Important:** Use **Test** rather than **View** when you are checking a change. It fills the fields for you, so you can reach the confirmation in one click without inventing answers. Pressing **Submit** on the Test screen is real: it saves a permanent submission and can send a real email. See [**Testing a form safely**](/articles/testing-a-form-safely). --- Putting a form in front of people --------------------------------- Every form already has its own page, so there is nothing to build. The address is `/form/` followed by the form's name, so the Contact form lives at: > */form/contact* The quickest way to get a form's address is to press **View** on the form and copy it out of your browser. You put a form in front of people by linking to that address, the same way you link to anything else: - Add it to a menu, so the form sits in the navigation where people look for it. See [**Adding and organising menu items**](/articles/adding-and-organising-menu-items). - Link to it from a page, beside the service it belongs to. See [**Linking to pages, files and addresses**](/articles/linking-to-pages-files-and-addresses). Either one is ordinary editing work, so a content editor can do it without help. What they cannot do is change what the form asks. ### Placing a form inside a page A form can also sit inside a page, using the **Webform** component. Add the component to an article or landing page, choose the form, and give it a title and short introduction if you want one. See [**Adding and removing site components**](/articles/add-remove-and-delete-site-components). This is ordinary page editing, so a content editor can do it. The form itself, and what it asks, is still changed only by an administrator. Related articles ------------------ - [ Roles and what they let you do → ](/articles/roles-and-what-they-let-you-do) - [ Adding and removing site components → ](/articles/add-remove-and-delete-site-components) - [ Testing a form safely → ](/articles/testing-a-form-safely) Was this article helpful? ------------------------- Your feedback helps us prioritise what to rewrite. Yes No [ Back to Forms ](/articles?category=8) On this page **Need additional help?** Submit a support request through the [**support portal** ](https://doghouse.atlassian.net/servicedesk/customer/portals)or email © 2026 [Doghouse SaaS](https://doghouse.agency) [Glossary](/articles/glossary)