# Bypassing the queue: who can transition directly

URL: https://kywi-docs-production.up.railway.app/governing/bypassing-the-queue-who-can-transition-directly
Type: docPage

Skipping review isn't a siteAdmin privilege — an editor can already move content straight to published, on a ladder one guard enforces everywhere.

Whether a piece of content has to sit in the queue on its way to published is a property of the person’s role, not a switch a site admin turns on for someone. Every role sits at a different point on the same ladder, and an editor’s point on it already includes skipping straight past pending and approved.

## Where each role sits on the ladder

An author can only move a piece of content from draft to pending — asking for review is the whole of what the role can do to a status. A rejection lands the piece back at draft, so resubmitting it is still within reach; everything else — approving, publishing, or moving anything backwards — needs an editor.

An editor can move draft, pending, or already-approved content straight to published in one action, with nothing in between required. That’s the whole reason the queue is skippable at all: it isn’t a special power, it’s what editor already means.

Site admin and super admin aren’t on a per-status table at all — either role can move content between any two statuses, including backward moves like pulling a published page back to draft, which the editor ladder never allows.

## One guard, everywhere status is written

The ladder is checked on every door that writes a status, not only the dedicated approve/reject/publish actions: creating content, editing it, a bulk publish or unpublish, and submitting for review all run through the same check. Whichever way a status change reaches the server, it answers to the same rules described above.

## Restoring an old version skips the ladder

One action writes a status with no ladder check at all: restoring a page to an earlier version. Whatever status that version was captured at, restoring it sets the page to that status directly, regardless of what the ladder would otherwise allow for the person doing the restore. See [Version history and rollback](/governing/version-history-and-rollback/) for what a restore actually changes.

See [Roles and the capability matrix](/governing/roles-and-the-capability-matrix/) for what each role can reach beyond content status — this page covers the status ladder specifically.
