---
title: "Get client approval on a Flow Step"
description: "Share a document, a note or a link in a step, and let your client approve it or request changes before the Flow moves on."
url: https://support.hubflo.com/fr/articles/15704495-get-client-approval-on-a-flow-step
collection: "Flows"
updated: 2026-11-09
language: fr
alternates: [en]
---

# Get client approval on a Flow Step

Share a document, a note or a link in a step, and let your client approve it or request changes before the Flow moves on.

Share something in a Flow, like a quote, a draft, or a document, and let your client **approve it** or **ask for changes** before the Flow moves on. You stay in control of the content, and your client signs off before the next step.

**When to use it**

-   An engagement letter or quote to validate before work starts
    
-   A deliverable (draft, report, design) to approve before moving on
    
-   A document to confirm before your client signs it in the next step
    

> **Note:** **Before you get started**
> Client approval is only available on steps that share something (a Note, Link, Embed, or Shared files) and are assigned to an external role (your client).

## Set up an approval step

1.  Go to **Flows > Templates** and open your template.
    
2.  Select the step that shares your content.
    
3.  Open the **Assignment** tab.
    
4.  Under **How does this step end?**, select **The client approves it, or asks for changes (approval)**.
    

Every Flow you launch from this template now includes the approval step.

> **Tip:** Approval isn’t available on File request, To-do, or Form steps. To check a client’s submission, choose “The participant completes the step, then a team member reviews it”.

## What your client sees

The step shows a **Needs your approval** badge. Your client opens the content and clicks **Approve** or **Request changes**.

![](https://staticfiles.gleap.io/ghelparticle/6ZmS4GJZqvJ1VBWa6vlHRBMo1Izl29CHWvzDFAHuJIa6NoirXPlqErF0hS4peRqBpAog1y4kmNy.png)

To request changes, they must leave a comment. They’ll see after sending: “Your request has been sent to the team. You’ll be notified when the step is ready again.”

## Handle a change request

1.  Open the Flow. The step shows **Changes requested** with your client’s comment.
    
2.  Click the **pencil** icon next to the content card to edit it. For **Shared files**, this reopens the uploader.
    
3.  Click **Send back for approval**.
    

![The Steps tab shows the selected Engagement letter step with Changes requested, a reviewer comment asking to update the fee schedule, and Skip and Send back for approval buttons. Visible: Steps, Files, Kickoff video, Completed, How we'll work together, Engagement letter.](https://staticfiles.gleap.io/ghelparticle/Lc0PzyDyhEhEzLod8i4fhfXwSl2aA2RRLY6SC8X8oe0l5CmwPNNULbb6UGvWF3j0pcnSt4wzakt.png)

Your client gets an email to review it again and once your client approves, the step shows **Approved by \[client name\] · \[date\]** and the Flow moves to the next step.

## **How notifications work for approvals**

<table data-id="aec7d88d-f20e-461d-81ca-7f40e469a4b9" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p data-id="196f7273-4bbe-4642-b978-385cf2b215ab">When</p></th><th colspan="1" rowspan="1"><p data-id="f2a844f2-11e1-4c55-bca6-35cfca1bb761">Who</p></th><th colspan="1" rowspan="1"><p data-id="e52eb25c-6f34-448d-8b10-540d5f603ad5">How</p></th></tr><tr><td colspan="1" rowspan="1"><p data-id="de5015ba-6328-4a9a-9f86-c6a0d49d3723">The step opens</p></td><td colspan="1" rowspan="1"><p data-id="0606f22d-2686-4d7d-b32f-cbc8b02f1b63">Client</p></td><td colspan="1" rowspan="1"><p data-id="d0ce3743-fd11-4db3-87ad-9decab2ee6e9">Email</p></td></tr><tr><td colspan="1" rowspan="1"><p data-id="82ced1c0-f881-41e3-9d85-3f72a8ab4bfe">The step is sent back for approval</p></td><td colspan="1" rowspan="1"><p data-id="16f1bf5d-8ecf-4f83-af54-c11fa16ba9a2">Client</p></td><td colspan="1" rowspan="1"><p data-id="3e86d15a-25cb-4264-9f0c-8ce770c6f6fd">Email</p></td></tr><tr><td colspan="1" rowspan="1"><p data-id="7c0b2684-aef7-4281-9f8d-1596da3ce881">The client approves</p></td><td colspan="1" rowspan="1"><p data-id="61249108-0e37-4af2-b47a-6c5e5922ae74">The person who launched the Flow, plus the contact’s owner</p></td><td colspan="1" rowspan="1"><p data-id="32282df3-b9f7-4fed-92c5-0f2ae913058b">In-app + push</p></td></tr><tr><td colspan="1" rowspan="1"><p data-id="e073d1cf-b759-454f-9c28-42738612a6b3">The client requests changes</p></td><td colspan="1" rowspan="1"><p data-id="f24a8fef-0613-4119-8045-99602231ca39">The person who launched the Flow, plus the contact’s owner</p></td><td colspan="1" rowspan="1"><p data-id="cdf3774a-417f-466c-80b6-f5fdc44a707f">In-app + push + email</p></td></tr></tbody></table>

## Related articles

-   [Start and manage a Flow](https://support.hubflo.com/en/articles/15704489-start-and-manage-a-flow.md)
    
-   [Notifications and reminders in Flows](https://support.hubflo.com/en/articles/15704493-notifications-and-reminders-in-flows.md)
    

* * *

💬 **Still have questions?** Start a chat with us or email [hello@hubflo.com](mailto:hello@hubflo.com). We'll be happy to help.
