Gate Keeper: Building Approvals into Your ReleaseOps Pipeline with Playbooks

[Jon G Lind]

On February 5, 2026, ReleaseOps Product Manager Jon Lind and Workflow Product Manager Lisa Holenstein hosted an interactive Platform Academy session that showed how to combine automated deployments with human oversight when necessary.

Playbooks are a foundational technology in designing ReleaseOps pipelines and provide a task-oriented, visual experience that guides release managers through deployment workflows using automation.

Attendees saw how to add conditional approvals to a Deployment Request assessment Playbook based on a Deployment Analyzer risk assessment. These same techniques can be leveraged to add other gating steps to stop the flow, such as waiting for a specific Story state, to your deployment processes.

[2mustang]

Jon you touched on child variants a bit. This may be something for the playbook product team, but figured i could throw it in here. 

Can two or more playbooks variants be triggered and run at the same/similar times? An example may be if we leverage record tags to indicate additional actions. If someone tags their deployment request with a  "Load Data" a variant may kick off for a task for the deployment request, but lets say they also have "Run Fix Script" It will kick off another variant at the same triggered timing to assign another task for running the fix script.

Trying to see how we can build dynamic tasks as developer teams have different needs