Home

Multisite Forms makes Statamic forms per-site in a multisite install. A form can be shown on some sites only, give each site its own title, email and storage choice, and keep each site's submissions apart in the Control Panel.

This wiki holds the documentation: a walkthrough, task guides by role, the reference, and troubleshooting. The README keeps an overview, the requirements and installation.

Getting started

• Installation (README): add the package to a multisite install.
• Your first multisite form: assign a form to one site, then two, and see each site's submissions and recipients.

Guides for site builders

• Showing a form on some sites only: assign a form to some sites, and choose what the others show.
• Giving each site its own title, email and store: a site override row, and showing the site's title in an email.
• Checking a form's site in a template: hide a heading, or show something else, where the form does not render.

Guides for administrators

• Giving editors access by site: a role for one site, and what an editor with it sees and can change.
• Attributing submissions from before the add-on: record a site on older submissions so that site's editors see them.

Guides for developers

• Listing forms by site through the API: the site filter on the REST and GraphQL form listings.
• Reading a form as a site sees it: resolve a form for a site in PHP, with its overrides applied.

Reference

• Configuration: the not_assigned setting, and what the form tags do on a site a form is not assigned to.
• Per-site title, email and store: the site_overrides rows in a form file.
• Control Panel access: who sees which forms and submissions, and the Site filter.
• Attribute command: recording a site on older submissions.
• API site filter: the site filter on the REST and GraphQL form listings.
• Form assigned tag: form:assigned, for checking a form's site in a template.
• Site form view: the read-only view of a form that templates, the submit route and listeners receive.

Troubleshooting

• Troubleshooting: one entry per symptom, from the message or behavior you see to its cause and fix.

Project

• Project: reporting a problem, how releases work, development notes and the license.
• Report a problem
• Releases