diff --git a/src/handbook/operations/signatures.md b/src/handbook/operations/signatures.md new file mode 100644 index 0000000000..aa02a172b8 --- /dev/null +++ b/src/handbook/operations/signatures.md @@ -0,0 +1,18 @@ +--- +navTitle: Signatures +--- + +# Signatures + +FlowFuse uses Hubspot for generating quotes, and requesting the signatures on +them. For other legal documents we're using +[Google eSignatures](https://support.google.com/docs/answer/12315692?hl=en). + +## Signature Circulation Requirements + +Before requesting a signature on any document, the following must be in place and +communicated. + +1. Context: What is the document being signed, and why are we signing this agreement? What does it support? +2. Confirm all required signatures upfront — both internal and counterparty. +3. The document must be fully filled out before circulation. No placeholder text (e.g., [INSERT DESCRIPTION]) or incomplete fields should remain. diff --git a/src/handbook/sales/legal.md b/src/handbook/sales/legal.md index 9379968c27..0dc98a844d 100644 --- a/src/handbook/sales/legal.md +++ b/src/handbook/sales/legal.md @@ -7,18 +7,7 @@ navGroup: Customer Department ## Collecting Signatures -FlowFuse uses Hubspot for generating quotes, and requesting the signatures on -them. For other legal documents we're using -[Google eSignatures](https://support.google.com/docs/answer/12315692?hl=en). - -### Signature Circulation Requirements - -Before requesting a signature on any document, the following must be in place and -communicated. - -1. Context: What is the document being signed, and why are we signing this agreement? What does it support? -2. Confirm all required signatures upfront — both internal and counterparty. -3. The document must be fully filled out before circulation. No placeholder text (e.g., [INSERT DESCRIPTION]) or incomplete fields should remain. +See the [Signatures](/handbook/operations/signatures/) page in Operations for procedures on collecting signatures and circulation requirements. ## Subscription agreement