Approval gate
A hard checkpoint in an automated flow where execution stops until a human decides: distinct from a notification, which informs without stopping anything.
Identify where a review actually stops execution and what evidence records the decision. In LinkedBoost, review should precede a send or enrollment call. A suggested confirmation and a scheduler delay do not establish a separate technical approval gate.
In practice
Review the exact audience, sender, copy, and timing before authorizing enrollment, then inspect what was queued.
What to check
A recommended confirmation in assistant instructions is different from a server-enforced gate. LinkedBoost's enrollment delay is not an indefinite approval hold.
Use it in LinkedBoost
- add_lead_group_to_sequence
Enroll a reviewed people group or an explicitly selected subset.
- get_sequence
Inspect campaign copy, performance, and the work waiting to send.
Related terms
- Approval queue
- A holding area for drafts awaiting review before execution. It is distinct from a sending queue, where authorized work is waiting to run.
- Human-in-the-loop
- System design where a person approves consequential actions before they execute. In LinkedIn outreach it means a human yes before any invitation, message or InMail reaches a real inbox, with the account's reputation on the line for every send.