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

# Approval workflow

> Set who approves a form's applications, and in what order.

The approval workflow is step 4 of the [Form manager](/proof/form-manager). It lists the members who must approve each application, in order. Use it to require more than one sign-off, for example an analyst then a director.

## Key concepts

| Term | Meaning |
| - | - |
| **Approver** | A member in the workflow list |
| **Assigned reviewer** | The approver whose turn it is. Only they can approve, decline or request information. |
| **Super Admin fallback** | If no listed approver is active, the earliest active Super Admin is assigned. |

## How it works

```mermaid theme={"system"}
flowchart TD
  A[Application accepted] --> B[Assign first active approver]
  B --> C{Approver approves}
  C -->|More approvers| D[Assign next active approver]
  D --> C
  C -->|Last approver| E[Approved]
  E --> F[Credential issued]
```

The workflow:

* Assigns approvers in list order.
* Skips approvers who already approved.
* Skips members who are inactive or no longer exist.
* Lists each member once, even if you add them twice.
* Falls back to the earliest active Super Admin if no listed approver is left.

## Set the workflow

<Steps>
  <Step title="Pick the approvers">
    Click **Add Approver** (2) and pick a member for each row (1). The number on the left is the order.

    <Frame caption="Step 4: Approval workflow">
      <img src="https://mintcdn.com/blupryntinc/g347_GY0e0vbB9tj/images/proof/form-workflow.webp?fit=max&auto=format&n=g347_GY0e0vbB9tj&q=85&s=a6b05adf2b2cf9791567c7ff79760b1b" alt="Approval Workflow step with two approvers, names redacted, and callouts on the first approver and Add Approver" width="2880" height="1800" data-path="images/proof/form-workflow.webp" />
    </Frame>
  </Step>

  <Step title="Order them">
    Drag a row by its handle to change the order. Click the bin to remove an approver.
  </Step>

  <Step title="Continue">
    Click **Next** to go to **Review & publish**.
  </Step>
</Steps>

## Reference

| Situation | Who is assigned |
| - | - |
| First approver is active | First approver |
| First approver approved | Next active approver |
| An approver is inactive | They're skipped |
| No listed approver is active | Earliest active Super Admin |
| No approver and no active Super Admin | Nobody. The action fails with *No valid approver or superadmin found*. |

## Worked example

You list two approvers: a Reviewer, then an Organization Admin. An application is accepted, so the Reviewer is assigned. They approve, and the Organization Admin is assigned. The Organization Admin approves, the application becomes **Approved** and the credential is issued. If the Reviewer had been inactive, the Organization Admin would be assigned first.

## Errors and troubleshooting

| Message | Cause | What to do |
| - | - | - |
| *No valid approver or superadmin found* | Every approver is inactive and there's no active Super Admin | Add an active approver. |
| *User is not in the approvers list* | Someone outside the workflow tried to approve | Add them to the workflow, or ask a listed approver. |
| *You are not assigned to this application yet* | It isn't your turn | Wait for the earlier approver. |

## FAQ

<AccordionGroup>
  <Accordion title="Does a Filing form use the workflow?">
    No. Filing forms issue their credential on submit, without review.
  </Accordion>

  <Accordion title="What if I leave the list empty?">
    The earliest active Super Admin is assigned.
  </Accordion>
</AccordionGroup>

## Related pages

* [Form manager](/proof/form-manager)
* [Application states](/proof/application-states)
* [Members and settings](/proof/members)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.