Skip to content

Documentation Update: 0.6.18 #319

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sg-doc-holiday wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Documentation Update: 0.6.18 #319

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f7a2ce8
clarify approval link behavior in hitl guide
sg-doc-holiday[bot] Feb 11, 2026
56688b2
clarify slack approval link behavior
sg-doc-holiday[bot] Feb 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion getting-started/deployment/local.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
```

<Note>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.</Note>
<Note>
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.
</Note>

After updating your `.env` file, restart the containers:

Expand Down
3 changes: 3 additions & 0 deletions workflow-management/human-in-the-loop.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)

Expand Down