> ## Documentation Index
> Fetch the complete documentation index at: https://docs.serval.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage forms

> Versions, run history, folders, copies across teams, and taking a form out of service.

## The forms list

**Service Management → Forms** shows the state of every form at a glance:

| Column or badge         | Meaning                                                            |
| :---------------------- | :----------------------------------------------------------------- |
| **Name**                | The form's name and folder                                         |
| **Fields**              | How many questions it asks, and how many automations it's wired to |
| **Last edited by**      | Who last changed it                                                |
| **Never published**     | Has drafts, never deployed. Employees can't reach it               |
| **Unpublished changes** | A version is live, but the draft differs                           |

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

<Note>
  Sessions are pinned to the version they opened. Publishing never changes a form out from under someone part-way through.
</Note>

## Run history

**Run history** 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](/sections/documentation/workflows/Run/run-history) view.

## Duplicate to another team

<Steps>
  <Step title="Open the form's ⋯ menu">
    Choose **Duplicate form**.
  </Step>

  <Step title="Pick the destination">
    Any team where you can manage forms.
  </Step>

  <Step title="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.
  </Step>
</Steps>

The copy arrives as an unpublished draft, so nothing is live until someone there publishes it.

<Warning>
  A copy references the same workflows the original did. Check the target team has the integrations and workflows the form depends on before publishing.
</Warning>

### 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.

## Take a form out of service

| Action      | Effect                                                                                               |
| :---------- | :--------------------------------------------------------------------------------------------------- |
| **Disable** | Stops new submissions and leaves the catalog. Versions stay intact, and enabling restores it exactly |
| **Delete**  | Permanently removes the form. Can't be undone                                                        |

<Tip>
  Disable first. It's the reversible way to stop a form that's producing bad requests, and it keeps the version and run history you'll want while diagnosing.
</Tip>

## Permissions

| Capability                                      | Who                                                        |
| :---------------------------------------------- | :--------------------------------------------------------- |
| Fill and submit the team's forms                | Anyone in the organization, subject to the form's audience |
| Create, edit, preview, publish, disable, delete | Team agents and managers                                   |
| Duplicate into another team                     | Requires manage-forms permission on the target team        |

See [Permissions](/sections/documentation/platform/permissions) for role assignment, and [Share and fill](/sections/documentation/forms/share-and-fill#control-who-can-open-a-form) to restrict who can open a given form.

***

<CardGroup cols={2}>
  <Card title="Forms overview" icon="clipboard-list" href="/sections/documentation/forms/overview">
    What forms are and when to reach for one.
  </Card>

  <Card title="Create a form" icon="wand-magic-sparkles" href="/sections/documentation/forms/create-a-form">
    Build, preview, and publish end to end.
  </Card>
</CardGroup>