Reviewing and approving submissions
The approvals queue merges draft submissions with pending revisions of live pages into one list, and approving either publishes in a single step.
The Approvals queue holds two different kinds of thing under one list: new pages and posts working their way through draft and pending for the first time, and edits to pages that are already live. The second kind — a pending revision — sits alongside the first without changing anything about the page it targets. A revision is a proposal, not a draft of the page itself; the live version keeps answering every request until someone approves it.
What approving does
For a first-time submission, approving is one step: the page moves from wherever it sat — draft, pending, or already approved — straight to published, in a single action. There is no separate publish afterward.
For a pending revision, approving does two things at once: it writes the proposed changes onto the live page and publishes them. The page you see before you approve is what goes live the moment you do — there’s no intermediate “approved but not yet published” state for a revision to sit in.
What rejecting does
Rejecting either kind discards the submission and leaves the live page exactly as it was. A rejected first-time submission stays off the site; a rejected revision simply never gets applied — the page it targeted was never touched in the first place.
Who can act on the queue
Reading the queue and acting on either kind of item — approve or reject — takes an editor role or above. It isn’t a site-admin-only capability, despite living on a governing surface: anyone with editor access or higher can clear their own queue. See Roles and the capability matrix for the full picture of what each role can reach.