Poliage

Review Workflow

The Review Queue is the heart of Poliage's governance model. Just like code needs a Pull Request, visual changes need review before going live.

How Items Enter the Queue

Every time you run poliage publish:

Asset StatusQueue StatusAction Required
New VisualsPENDINGNeeds approval
Changed VisualsPENDINGNeeds approval
Unchanged VisualsAPPROVEDNone (auto-approved)

Reviewing Changes

Navigate to Visuals in your project dashboard.

Filter Views

  • All Visuals: Complete gallery
  • Pending Reviews: Items awaiting approval
  • Recently Changed: Last 7 days of activity

Actions

ActionIconResult
ApproveNew version goes live immediately
RejectChange is discarded, previous version remains live

Approval Flow

  1. Developer runs poliage publish locally or in CI
  2. Changed assets appear in Review Queue
  3. Team member reviews changes (with diff overlay)
  4. Approves or rejects each visual
  5. Approved visuals update live CDN URLs instantly

Bulk Actions

For large batches:

  • Approve All: Accept all pending changes at once
  • Filter & Approve: Approve by scenario or variant

Review Permissions

RoleCan Review
Owner
Member
Viewer

Integrate with GitHub to get notified of visual changes via PR comments. See GitHub Integration.