# The signing workflow

Signing is how every movement and asset action is approved. Each signer reviews the transaction and signs it with their own key. When enough signers have signed, it is finalised and broadcast automatically.

> Part of the SQRL documentation, section "SQRL Enterprise".
> Rendered page: https://docs.sqrl.tech/enterprise/movements/the-signing-workflow

## Signing a pending movement

**Required:** A key in the vault's signer set, and Approve movement (`APPROVE_PAYMENT`) to see the movement queue. You cannot sign a movement you proposed.

1. Open the movement from your notification, or from **Movements**.
2. Review the type, vault, destination, asset, amount, description, and for enforcement actions, the reason and case.
3. Select **Sign Transaction**.
4. Choose **Software Key** or **Hardware Wallet**.
   * Software key: enter your wallet password. Your browser signs.
   * Hardware wallet: confirm the details on your Trezor's screen and approve.
5. The signature is submitted automatically.

The movement shows each signer as **Signed** or **Pending**, and the progress toward the threshold.

  Your key signs on your device. SQRL receives only the signature, adds it to the transaction, and never sees your private key.

## After the final signature

When the threshold is met, the transaction is finalised and broadcast. The movement moves through **Broadcasting** and **Confirming** to **Completed**. There is no step in between: the final signature is the point of no return.

  A movement moves forward only when signers sign it, it is never signed on your behalf, and it cannot be undone once the threshold is met. Treat every signature as final.