Skip to main content

​
The forms list

Open Library → Forms in the compact rail, or Forms in the classic sidebar’s Service Management section, to see the state of every form at a glance: Search filters by name. Select several forms to publish, enable, disable, or delete them at once. Create folders and drag forms in, the same way you organize workflows.

​
Versions

Every publish creates an immutable version. Edits between publishes autosave into the current draft.
  • Switch versions from the version selector. The action bar says whether you’re on the published version, the draft, or an older one
  • Compare versions to see what changed before publishing or restoring
  • Restore an older version to bring it back as a new draft. Restoring publishes nothing and deletes nothing
Sessions are pinned to the version they opened. Publishing never changes a form out from under someone part-way through.

​
Form activity

Form activity lists every session opened against the form, newest first, with the workflow runs each one started. Use it to answer: did this submission start the workflow, which version was the requester on, and why did it fail? Click through for the workflow’s own run history and debugging view.

​
Duplicate to another team

1

Open the form's ⋯ menu

Choose Duplicate form.
2

Pick the destination

Any team where you can manage forms.
3

Decide where it lands

Keep in the same folder recreates the source’s folder in the target team. Otherwise the copy goes to the top level.
The copy arrives as an unpublished draft, so nothing is live until someone there publishes it. It keeps the source form’s Who can request audience. The built-in Team Members profile is created automatically in the destination when needed. For other access profiles, choose a team that already has matching profiles or promote them to a linked destination before duplicating the form. A copy to a team without matching profiles does not proceed.
A copy references the same workflows the original did. Check the target team has the integrations and workflows the form depends on before publishing.

​
Keeping copies in sync

A cross-team copy stays linked to its source.
  • On the copy: a Linked to badge points at the source. When the source publishes a newer version, Update Available appears. Pull update brings it in as a new draft. Ignore update stops offering that version
  • On the source: a linked forms popover lists its copies, so you can see who’s downstream before changing something
Pulling writes a draft. It never publishes on the copy’s behalf or replaces the copy’s Who can request audience. Review that audience in the destination before publishing.

​
Take a form out of service

Disable first. It’s the reversible way to stop a form that’s producing bad requests, and it keeps the version and Form activity you’ll want while diagnosing.

​
Permissions

See Permissions for role assignment, and Share and fill to restrict who can open a given form.

Forms overview

What forms are and when to reach for one.

Create a form

Build, preview, and publish end to end.