# Review queue and access

The review queue lists the proposals associated with the App. Open a review to inspect its title, kind, status, saved payload, source links, and revision. Load additional pages when available instead of treating the first visible page as the entire ledger.

## Read the complete proposal

An App can expose a focused set of fields for editing, including fields within arrays. Those controls are a convenience, not the whole saved proposal. Read the complete saved content when deciding whether to approve, especially when the proposal has supporting assumptions or fields outside the visible form.

Check that the title and source set match the task. Similar titles can refer to different revisions or different source documents. Review identity and source capture matter more than the display label.

## Ownership and sharing

The review ledger belongs to the App owner. Sharing a deployed App does not automatically share that ledger. Another workspace administrator also should not be assumed to gain owner-level review access simply by holding an administrative role.

Delegated assistance can prepare, edit, and capture evidence for the owner where permitted. The decision itself remains human-only. A request arriving through an agent transport does not become human provenance merely because a person supplied the agent with authorization.

## Recover the current state

After a reload, reopen the persisted review and check its current revision and history before repeating a change. Another action may have changed its status or payload while your view was open. A stale mutation is refused rather than silently replacing the newer review.

For queue items produced by generation, inspect the associated generation receipt. Reopening a proposal reads its saved provenance and should not start another model call.

See [history and receipts](/docs/reviews/history-and-receipts) and [uncertain requests](/docs/reviews/uncertain-requests).