Geiger Assets · Approvals and workflows
Sign-off in stages, on the record
Every review on one board
Gather the files that need sign-off into a review, give it a priority and a due date, and see what is in flight, sent back or late at a glance.
Geiger AssetsDecide file by file, with the reasons on record
Approve, send back or reject each file in a review. Comments sit beside the files, and every decision on the current stage counts toward its sign-offs.
Ask for sign-off in one dialog
Name it, choose the pipeline it runs through, set a priority and a due date of three days, a week or two weeks, then attach the files.
Who decided what, and when
The decision history keeps every sign-off, rejection and change request, with the stage it was made on and the note that came with it.
Pipelines that route the sign-off
Build the route once: who approves at each stage, how many sign-offs each stage needs, and what happens when the last one clears.
Geiger AssetsLock the version that was approved
When the final stage signs off, the pipeline can mark the files approved and lock the approved version, so it can't be swapped without a new review.
In order, or all at once
A sequential pipeline opens each stage only when the one before it clears. Set it to Anytime and every stage can act in any order.
A pipeline for each kind of work
Route assets, collections, galleries or shared links through their own pipelines, and keep each one as a Draft, Active or Paused.
Name the approvers
Let anyone with a role approve a stage, or pick specific people and say how many of them have to sign off.
Start from a template
Begin with a blank pipeline or a ready-made route such as Brand review, Client delivery or External access, then change it to fit.
Workflows that act on the result
When a file is uploaded, sent for review, approved or rejected, a workflow can move it, set its status, tag it and call your own systems with a webhook.
Geiger AssetsFrom approval to the next step, on its own
Lay out a trigger, conditions and actions on the canvas. Each run logs what every step did, from the folder a file moved to the response the webhook got back.
Triggered by what happens to a file
Start a workflow when an asset is uploaded, sent for review, approved or rejected, then move, set status, tag, untag or send a webhook.
Every run on the record
Run History shows each run with its trigger, outcome, duration and steps, so a skipped or failed run is easy to find and read.