Attestation
Overview of how Forms can use attestation to add manual review before actions are completed.
Attestation adds a manual review step to a Forms process. It is useful when a requested change is sensitive, requires oversight, or needs a traceable approval before automated actions are carried out.
What attestation is used for
Section titled “What attestation is used for”Use attestation when a Flow should collect data first, then ask one or more designated approvers to review the request before the final action is completed.
Typical examples include:
- access requests that need approval from a manager or resource owner
- sensitive account or group changes
- changes that require auditability and traceability
- processes where the request should be archived as a PDF
How it works
Section titled “How it works”An attestation process normally contains two parts:
- A user-facing Flow where the request is created.
- An attestation Flow where one or more approvers review, accept, or reject the request.
The request data is stored as a work order. Approvers can be notified by email and can review a PDF containing the information they need before making a decision.
When the request is accepted, an accept Pipe can perform the approved action. When the request is rejected, a reject Pipe can handle cleanup, notification, or follow-up.
Traceability
Section titled “Traceability”The generated PDF can be sent to an external archive after the request has been attested. This supports auditability, compliance, and later review of what was requested, who reviewed it, and what decision was made.
See Setup for configuration guidance.
In this section