Skip to main content

Improved Approval Policies – Messaging, Notifications & Easier Authoring

Feature RequestsPolicies

We’ve been long-time users of Spacelift and one of the early reasons we adopted it was your flexible policy engine. That said, approval policies haven’t evolved in a way that supports real-world workflows. Here’s what’s missing:
What’s Needed:

  • Message Visibility in Workflows

    • Ability to display a clear reason for blocking or approving a run.

    • Example: “This change lacks a ticket reference – please include one” → currently this is impossible to express.

  • Built-in Notification Hooks

    • Slack or email notifications when a manual approval is required.

Status: ⬆️ Gathering votes2 comments

Log in to comment and vote

Comments2

  • Ovidiu Moise

    Team•

    Sep 24

    Dear upvoters, for the last bullet point this is already possible. Your users can already link their Spacelift account with an External Account (e.g. Slack) and then you can define Notification Policies to reach them directly in Slack. Docs: https://docs.spacelift.io/concepts/identity-access-management/external-accounts

  • Red Bucket

    •

    Apr 21

    +1 to improved approval-policy notifications.

    Our use case:

    • A plan fails a security policy ➜ an approval from #security-team is required.

    • Once approved, the same run still needs the originator to hit Confirm before it proceeds.

    Today we approximate step 1 with run.state = UNCONFIRMED + policy flags, but there’s no explicit event for “approval granted—please confirm.” This leaves engineers waiting (sometimes unknowingly) and slows deploys.