--- title: Octopus Approvals | daily.dev description: Octopus Deploy has launched Octopus Approvals, a lightweight approval workflow that gates deployments to sensitive environments like production without... canonical: https://daily.dev/posts/octopus-approvals-jphkz70xl twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Octopus Approvals | daily.dev og:description: Octopus Deploy has launched Octopus Approvals, a lightweight approval workflow that gates deployments to sensitive environments like production without... og:url: https://daily.dev/posts/octopus-approvals-jphkz70xl og:image: https://api.daily.dev/og/posts/jPhKz70xL.png og:image:alt: Octopus Approvals og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Octopus Approvals **[OctopusDeploy](https://daily.dev/sources/octopusdeploy)** · 5 min read · 0 upvotes · 0 comments ## Summary Octopus Deploy has launched Octopus Approvals, a lightweight approval workflow that gates deployments to sensitive environments like production without requiring a full ITSM implementation (e.g. ServiceNow, Jira Service Management). Teams can require a minimum number of approvers from specific teams, block the deployment creator from self-approving, and scope rules by project tags at the space level. Approvals occur before deployment starts, rejected change requests can't be revived (a new deployment must be created), redeployments of already-approved releases skip re-approval, and scheduled deployments can be pre-approved outside working hours. The feature is available as a Public Preview for cloud customers and in the 2026.3 server release, but currently only supports deployments, not runbooks, and cannot automate approvals. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is Octopus Approvals and how does it differ from using ServiceNow or Jira Service Management for deployment approvals? Octopus Approvals is a lightweight, built-in approval workflow in Octopus Deploy for gating deployments to sensitive environments like production, aimed at teams that need more rigor than manual intervention steps but can't justify a full ITSM implementation like ServiceNow or JSM. It lets teams set the number of required approvers, restrict approving teams, and block deployment creators from self-approving, without replacing ITSM tools for highly regulated, complex compliance needs. _Teams weighing lightweight approval gates against full ITSM tooling can track release details like this on daily.dev._ ### Do I need to re-approve a redeployment of the same release in Octopus Deploy with Approvals enabled? No, each release only requires one approval; redeploying the same already-approved release to the same environment does not trigger another approval request. This design specifically ensures that rollbacks to a previously approved version are not blocked by the approval gate, keeping rollback workflows fast even with approval rules in place. _Anyone configuring rollback-safe approval rules can follow release notes like this via daily.dev._ ### What happens if an approver rejects a change request in Octopus Approvals? The deployment does not proceed and is marked as failed; a rejected change request cannot be revived. To try again, a new deployment must be created, which generates a new change request. Teams can track these failures through their normal failed-deployment process or by setting up a Subscription to get notified of change request status changes. _Release engineers debugging blocked deployment pipelines can keep tabs on tooling changes like this through daily.dev._ ## Similar posts on daily.dev - [Octopus Easy Mode - Manual Interventions](https://daily.dev/posts/octopus-easy-mode---manual-interventions-w1yddxrsk) · OctopusDeploy · 1 upvotes · 0 comments - [Pulumi ESC: Open Approvals](https://daily.dev/posts/pulumi-esc-open-approvals-7m8zjf6fb) · Pulumi · 0 upvotes · 0 comments - [Octopus Easy Mode - Progressive Rollout](https://daily.dev/posts/octopus-easy-mode---progressive-rollout-eznedy7aa) · OctopusDeploy · 1 upvotes · 0 comments - [Amazon Quick now supports approval policies for sharing](https://daily.dev/posts/amazon-quick-now-supports-approval-policies-for-sharing-pdfrkfost) · AWS · 0 upvotes · 0 comments - [Optionally skip approval for Copilot coding agent Actions workflows](https://daily.dev/posts/optionally-skip-approval-for-copilot-coding-agent-actions-workflows-vhdeokyjj) · GitHub Changelog · 0 upvotes · 0 comments --- Tags: [#devops](https://daily.dev/tags/devops), [#cicd](https://daily.dev/tags/cicd), [#compliance](https://daily.dev/tags/compliance), [#octopus-deploy](https://daily.dev/tags/octopus-deploy) [View this post on daily.dev](https://daily.dev/posts/octopus-approvals-jphkz70xl) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Octopus Approvals","url":"https://daily.dev/posts/octopus-approvals-jphkz70xl","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/octopus-approvals-jphkz70xl"},"datePublished":"2026-09-29T11:39:04.079Z","dateModified":"2026-09-29T11:39:28.975Z","description":"Octopus Deploy has launched Octopus Approvals, a lightweight approval workflow that gates deployments to sensitive environments like production without...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6fe94dfe18f440eb57bd38297a792e62?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6fe94dfe18f440eb57bd38297a792e62?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"OctopusDeploy","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"OctopusDeploy","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/71110ae886d64eac9f3a01496feb2bd8","url":"https://daily.dev/sources/octopusdeploy"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/octopus-approvals-jphkz70xl","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"devops,cicd,compliance,octopus-deploy","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"OctopusDeploy","item":"https://daily.dev/sources/octopusdeploy"},{"@type":"ListItem","position":3,"name":"Octopus Approvals"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/octopus-approvals-jphkz70xl#faq","mainEntity":[{"@type":"Question","name":"What is Octopus Approvals and how does it differ from using ServiceNow or Jira Service Management for deployment approvals?","acceptedAnswer":{"@type":"Answer","text":"Octopus Approvals is a lightweight, built-in approval workflow in Octopus Deploy for gating deployments to sensitive environments like production, aimed at teams that need more rigor than manual intervention steps but can't justify a full ITSM implementation like ServiceNow or JSM. It lets teams set the number of required approvers, restrict approving teams, and block deployment creators from self-approving, without replacing ITSM tools for highly regulated, complex compliance needs. Teams weighing lightweight approval gates against full ITSM tooling can track release details like this on daily.dev."}},{"@type":"Question","name":"Do I need to re-approve a redeployment of the same release in Octopus Deploy with Approvals enabled?","acceptedAnswer":{"@type":"Answer","text":"No, each release only requires one approval; redeploying the same already-approved release to the same environment does not trigger another approval request. This design specifically ensures that rollbacks to a previously approved version are not blocked by the approval gate, keeping rollback workflows fast even with approval rules in place. Anyone configuring rollback-safe approval rules can follow release notes like this via daily.dev."}},{"@type":"Question","name":"What happens if an approver rejects a change request in Octopus Approvals?","acceptedAnswer":{"@type":"Answer","text":"The deployment does not proceed and is marked as failed; a rejected change request cannot be revived. To try again, a new deployment must be created, which generates a new change request. Teams can track these failures through their normal failed-deployment process or by setting up a Subscription to get notified of change request status changes. Release engineers debugging blocked deployment pipelines can keep tabs on tooling changes like this through daily.dev."}}]} ```