Approvals

Approvals put a required sign-off between a draft and publishing. When the lane is on, a post can’t be scheduled or published until an approved request clears — and editing approved content sends it back for review.

Turning on the approval lane

Approvals are off by default; posts publish without review until an owner or admin enables the lane under Settings → Approvals. Setting the rule is an owner/admin action. There you:

1. Require approval — flip the switch on. Now every post must carry an approved request before it can arm for scheduling or publishing.
2. Choose approvers — pick which members can sign off. At least one is required to save.
3. Choose a policy — how many of those approvers must approve:
   • Any one approver — the first approval clears the post.
   • A quorum — a set number of approvals is needed; leave it blank to require all named approvers.

There is one active rule per organization. The rule is snapshotted onto each request when it opens, so changing it later never rewrites reviews already in flight.

Submitting and the reviewer queue

A post author submits their own post for approval, which moves it to a pending state and opens a request. Approvers then work the reviewer queue — pending requests each shown with a one-line excerpt of the post, so a teammate can triage sign-offs without opening every post.

Each approver records one decision, and the outcome follows the policy:

• Approved — once enough approvals land (one for any one approver, the quorum otherwise), the request clears and the post becomes ready to schedule or publish.
• Rejected — any single rejection concludes the whole request, and the post returns to draft to be revised.

Every member can see the queue; deciding is limited to the approvers the rule names. A repeated click on the same decision is a no-op, never a double vote.

Reset-on-edit

An approval covers the exact content that was approved. If a post’s content changes after it was approved, Inklate cancels the open approval — the publish gate then refuses until the post is submitted and approved again. In short: what was approved is what ships, or approval runs again.

Because of this, edit before you submit rather than after. The Composer is where posts are written, submitted, and re-submitted.

The publish gate

When the lane is on, the gate is enforced wherever a post arms — the dashboard, the calendar, or an agent over the API — not just in one screen. A post without an approved request is turned away with a clear reason to submit it first. When the lane is off, there is no gate and posts publish directly.

Approvals are separate from publishing rules (quiet hours, banned terms, blocked link domains), which owners and admins configure under Settings → Publishing rules and which apply to every post regardless of the approval lane.