diff --git a/getting-started/deployment/local.mdx b/getting-started/deployment/local.mdx
index 864ce44..4e9e00c 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:
diff --git a/workflow-management/human-in-the-loop.mdx b/workflow-management/human-in-the-loop.mdx
index ecdfb00..8d54f44 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:
