From f7a2ce8e780757e27c111015351535fca7c43d54 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Wed, 11 Feb 2026 14:34:01 +0000 Subject: [PATCH 1/2] clarify approval link behavior in hitl guide --- workflow-management/human-in-the-loop.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/workflow-management/human-in-the-loop.mdx b/workflow-management/human-in-the-loop.mdx index ecdfb007..8d54f448 100644 --- a/workflow-management/human-in-the-loop.mdx +++ b/workflow-management/human-in-the-loop.mdx @@ -65,6 +65,9 @@ In this case, you can create the approval part of your workflow as follows: 3. Add the **Wait For Approval** action from the **Approval** block. Once the stakeholder clicks a link, this action updates the approval status accordingly. 4. Add the **Condition** action to define steps for approval and disapproval. +> Note: The links generated by **Create Approval Links** are OpenOps resume links. +> When a stakeholder opens one of these links, OpenOps shows a confirmation page before resuming the workflow with either the `approve` or `disapprove` action. + Here's a sample workflow that uses **Create Approval Links**, delivers an email notification using **Send Email** from the **SMTP** block, and then proceeds based on the output of the **Wait For Approval** action: ![Sending approval links via email](/images/hitl-email-approval-links.png) From 56688b27a28117b37d0230caefe3235388eb9b1e Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Wed, 11 Feb 2026 14:36:41 +0000 Subject: [PATCH 2/2] clarify slack approval link behavior --- getting-started/deployment/local.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/getting-started/deployment/local.mdx b/getting-started/deployment/local.mdx index 864ce440..4e9e00cc 100644 --- a/getting-started/deployment/local.mdx +++ b/getting-started/deployment/local.mdx @@ -130,7 +130,11 @@ If you would like to run a workflow that uses Slack approvals in a local install OPS_SLACK_ENABLE_INTERACTIONS=false ``` -This will open a new tab in your default browser when you approve or reject an action. You can safely close the tab after the action is completed. + +Approving or rejecting an action opens a new browser tab. + +After approval or rejection, OpenOps shows a confirmation page with details. The tab can be closed after confirming the result. + After updating your `.env` file, restart the containers: