> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/complete-the-required-reviews.md). # Complete the required reviews Find an exact review request, check its item version and rules, then approve it, return it for changes, reject it, or cancel it without changing the wrong version. The Podigee Audio Video Ad Server connects every review to one exact item version. The reviewer can see what needs a decision, which rule applies, how many decisions are required, and when the request expires. Use **Approvals** for Campaign terms, ad break placements, Creative suitability, launch setup, capacity, finance, policies, integrations, and governed exceptions. ## Understand review rules Your workspace can use one of these review modes for an action family: * **No approval required:** Authorized work can continue without a human review. * **Optional review:** A teammate can give advice, but the request does not block the work. * **Solo confirmation:** The authorized operator confirms the exact action without a second person. * **Independent review:** A different authorized person must decide the request. The rule shown on the request is the rule that applies to that exact item. Do not assume that all Campaign, Creative, editorial, launch, finance, or exception reviews use the same mode. ## Find the request 1. Open **Monetization**. 2. Open **Approvals**. 3. Search by item name, message, or reference when needed. 4. Filter by **State** or **Item type**. 5. Select **Open** for the request. ![The current One Podigee Approvals page shows approved Campaign setup and ad break placement requests with filters, item versions, required decisions, and expiry dates.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-518cfa89c3e153c05b164839d192ee2a4643cde0%2Fdoc-monetization-053-approvals-list.jpg?alt=media) *Use the state and item-type filters to find the exact decision.* The list can show **Pending**, **Approved**, **Rejected**, **Returned**, **Canceled**, and **Expired** requests. A request can remain in the history after it stops blocking work. ## Check what you are reviewing Before you decide, confirm: * The item name and type. * The item version. * The short reference and version fingerprint. * The request message and the complete business context. * The review rule and whether an independent reviewer is required. * The number of required decisions. * The expiry date. The page can include Campaign terms, forecast and capacity, Inventory, delivery scope, Creative media, rights, ad breaks, policy changes, finance amounts, or exception details. Check the complete context that the page shows for the item type. ![The current One Podigee Review approval page shows an approved Campaign setup, its exact version, its version fingerprint, the solo-confirmation rule, and the expiry date.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-606d6b0b3571559333d89dec7374becaf80216d8%2Fdoc-monetization-053-approved-detail.jpg?alt=media) *The decision applies only to the exact version shown on the page.* ## Approve the exact version Select **Approve** only when the displayed item and its complete context are correct. Podigee records your identity, the exact item version, the applicable policy version, the time, and the decision. For an independent review, the author of the item cannot approve their own request. The reviewer must also have the permission and scope required by the displayed policy. ## Return the item for changes Use **Return for changes** when the work can continue after a correction. 1. Select the area that needs a change when the page provides review sections. 2. Write one clear instruction that tells the requester what to correct. 3. Select **Return for changes**. The current item remains unchanged. The requester can create a corrected version without losing the accepted parts of the work. The returned decision does not approve the corrected version. ## Reject the request Use **Reject** when the proposed item should not proceed in its current form and a normal correction is not enough. Select the relevant review area and provide a clear reason. Rejection closes that request. The requester must create a suitable new version and, when required, send a new review request. ## Cancel a pending request The authorized requester can cancel a pending request that is no longer needed. The confirmation dialog prevents an accidental cancellation. Cancellation does not delete the item or its review history. It prevents the canceled request from authorizing the item. ## Handle an expired request A pending request expires at the time shown on the page. An expired request cannot receive a new decision. Confirm that the item is still current, then create a new request when the work still needs review. Do not extend the old request or copy its decision to a newer item version. ## Handle a change after review An approved decision applies only to the displayed item version and fingerprint. A later change to the Campaign, Creative, ad break, policy, finance item, or exception can require another review. Podigee keeps the earlier decision as evidence, but it does not use that decision to approve the changed version. Return to the connected work, prepare the new exact version, and request the review that the current rule requires. If an approved action must be stopped after it takes effect, use the control for the live object, such as pause or revoke publication. Do not try to edit the earlier approval record. ## Expected result The review request has a durable outcome for one exact item version. An approved item can continue only within the scope of that decision. A returned, rejected, canceled, expired, or changed item cannot use the earlier request as current approval. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podigee.com/documentation/grow-and-monetize/monetization/complete-the-required-reviews.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.