Qalibr docs — your guide to bug intake intelligence. Start a free trial →
Core conceptsThe approval gate
Core concepts

The approval gate

Qalibr never creates or changes anything in your tracker on its own. Every routed ticket passes a human approval gate. This is the guarantee that automation speed never costs you control.

  • Where you approve — from the dashboard (inline on the report) or from the approval card Qalibr posts in the Slack thread. Either works; they stay in sync.
  • What approval does — opens the ticket (or links the duplicate), and posts the outcome back to the original thread.
  • What rejection does — drops the report; nothing is created. You can reject-as-duplicate or reject outright.
  • Edit before you approve — you can edit the drafted title and description first, so what lands in the tracker is exactly what you want. See Approve, reject & edit.
  • Expiry — an approval left untouched past its window expires, so stale drafts don’t pile up. Expired reports can be brought back — see Re-trigger expired reports.

The gate is why Qalibr is safe to point at a busy channel: it prepares everything, but a person always says yes.