--- url: https://docs.codefox.ai/apps/pampas/share-a-form.md --- # Share a form and invite people This page shows you how to get a published form to the people who should answer it: by its link or QR code, on your own website, or with a personal invitation for each person. It also covers the password and the captcha that keep unwanted answers out. Everything here is on the form's **Share** page. ## Before you start * The form is published. A form that was never published has no working link; **Share** shows **Publish to get a link** until it is. * Invitations and reminders need email set up on the server. See [Set up email](/self-host/email). ## Share the public link 1. Open **Share**. 2. Under **Public link**, copy the link. Anyone with it can open the form. 3. To print it or put it on a slide, use **QR code** and download the PNG. 4. Check **Test mode** is off. While it is on, answers are not counted and are deleted every night. **Social preview** is on by default: when the link is pasted in a chat or social network, it shows the form's title and theme. Turn it off to show a plain link. ## Protect the form Under **Access**: * **Password**: type a **New password** of 6 to 200 characters. Everyone who answers uses this one password. Select **Remove password** to open the form to anyone with the link again. * **Captcha**: choose **Every submission** or **When something looks off** (a spam signal, a quota breach or a burst of submissions). A captcha works only once someone who can manage Pampas has saved a provider's keys; see [Set up Pampas for your team](/apps/pampas/set-up-for-your-team). Pampas also checks each answer for signs of spam, such as a form filled in under three seconds. A suspect answer is kept and held back from the form's destinations until you look at it; see [Read and export responses](/apps/pampas/read-responses). Under **Answers**, **Allow AI features** decides whether AI may read this form's answers, for the summary, a response brief and the spelling fix respondents can use. It appears only when AI is set up. ## Embed the form on your website 1. Under **Allowed origins**, add the address of each site that shows the form, such as `https://example.com`, without a path. You can list up to 20. 2. Under **Embed on your own site**, copy the **Iframe (any site)** code. 3. Paste it into the web page. Until a site is in **Allowed origins**, browsers refuse to show the form on it. To prefill answers, pass hidden fields or build the form into your own app, see [Embed a form](/connect/embed). ## Invite people by email Each invited person gets a personal link. Pampas tracks each link from sent to submitted. 1. Under **Recipients**, type one person per line in **Add recipients**: an email, then optionally a comma and a name, for example `jane@client.com, Jane`. 2. Choose **Access**: * **Link only**: the personal link opens the form. * **Email code**: the person also enters a six-digit code sent to their address. Their answer is then marked **Email-verified**. 3. Optionally set **Expires in (days)**, and tick **Single-use link** so the link works for one response only. 4. Select **Add**. The people appear in the table with the status **Not sent**. 5. Select **Send all unsent** to email every new person, or **Send** in one person's row. In a person's row you can also copy their link, set **Prefill** values (one `key=value` per line, using the question keys), show a QR code, **Resend** the invitation, or **Delete** the person. Deleting stops their link at once; any answer they already sent stays in **Responses**. Invited people who have not answered get a reminder email every three days, three times at most. Each reminder carries a link to stop further reminders. To send people to a page on your own site instead of the hosted form, set a **Respondent link template**: an `https` address on one of your allowed origins that contains `{token}`, such as `https://your-site.com/intake/{token}`. ## Add scripts to the form's pages People who can manage Pampas see **Head HTML** at the end of **Share**. It adds HTML, such as an analytics script, to this form's pages, and they confirm it is them before saving. List under **Third-party hosts** each `https` address the HTML loads from. Respondents can see the scripts, and the privacy notice on the form names those hosts. ## Troubleshooting ### "No invites went out" No email service is set up on the server, so Pampas sent nothing. The people are added and their links work: copy each link from its row and send it yourself, or ask whoever runs the server to [set up email](/self-host/email). ### "Today's email limit is reached. Try again tomorrow." The server sends at most a set number of respondent emails a day. Send the rest tomorrow, or copy the links from the rows and send them yourself. ### The embedded form is blank, or says "This page isn't allowed to use the form." The site is not in **Allowed origins**, or its address differs, for example `www.` or `http` against `https`. Add the exact address the page is served from. ### Respondents never see a captcha No captcha keys are saved, so a form set to ask for one sends without it. **Captcha** says **No captcha keys are set yet** in that case. Ask someone who can manage Pampas to add the keys. ### People say the link shows the form is closed The form was closed by hand, reached its **Close at** time, or reached its **Response limit**. If someone closed it, select **Reopen form** on **Share**. If it reached a time or a limit, change **Closing** in the builder's **Form** settings and publish again. ### Test answers vanish overnight **Test mode** is on. Turn it off under **Public link**. Answers already sent in test mode are not kept.