Skip to content
GearDock

Coming Soon · in Build

Review Workflows for Teams Larger Than One Reviewer

GearDock already separates drafting, approval, release, and export, and records who did each action. It does not yet route work to specific reviewers, hold a second opinion where one is required, or show a team its assigned queue.

Available Today

What You Can Use Instead, Now

This capability is not released. Here is what already covers the same ground.

Review, approval, and release already work as separate decisions with separate permissions. A single reviewer or a small team sharing one queue can approve and release content today. Work assignment and routing are not yet available.

When It Ships

What This Will Do

Stated as behavior rather than as benefit, so it can be checked against the release when it happens.

  • Assign products and content to named reviewers rather than a shared queue.
  • Require a second approval on classes of claim a team decides are high-consequence.
  • Escalate a review that has been sitting, to a person rather than to a report.
  • Show a team's workload as a queue with an owner per item.

The Honest Reason

Why It Is Not Out Yet

Routing work between people is a governance change, not a UI feature. Assignment, quorum, and escalation all decide who is permitted to approve what, and shipping that before the permission model behind it is complete would mean a workflow that looks like it enforces a rule while enforcing nothing.

Common Questions

Review Workflows, Answered

Can more than one person review content today?

Yes. Multiple people can hold review roles and work the same queue, and every decision is attributed to the person who made it. What is not yet available is assigning a specific product to a specific reviewer, or requiring a second approval before release.

Is approval already separate from release?

Yes, and it always has been. Marking content approved does not make it publishable, and nothing is exported on approval alone. That separation is part of the shipped product, not part of this roadmap item.

Private Beta

Waiting on Review Workflows?

Tell us what it is blocking. Which capability customers are actually held up by genuinely affects the order the work is done in.