> 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/assign-owners-and-discuss-exact-versions.md). # Assign owners and discuss exact versions Assign one accountable owner and keep feedback attached to the exact saved version that needs work. Podigee Audio Video Ad Server keeps ownership and feedback with the saved version that needs work. After the first mention, this article uses Podigee Ad Server for the product name. Use this task when a Campaign, Creative, delivery setup, report, or policy needs one owner and a clear decision. An exact-version discussion does not approve a later version. If the item changes, resolve the old discussion or carry it forward to the current version. ## Before you start * You have access to **Monetization > Team inbox**. * You have permission to assign an owner or write a discussion. * You know the result that the owner must deliver. * You know which saved version and location need attention. * You know the due date or can leave it without a due date. ## Assign an accountable owner 1. Open **Monetization > Team inbox**. 2. Choose **Assign owner**. 3. Select the saved item. 4. Confirm the displayed version and revision. 5. Select the person who owns the result. 6. Enter the requested result and due date. 7. Select the effective time for the assignment. 8. Review the item, version, owner, result, and date. 9. Save the assignment. ![The current One Podigee Team inbox shows saved items, the requested result, due date, state, and Review action, followed by accountable ownership.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-29c533fd32144f87b1f580a76ce41c2cbf1ca03b%2Fdoc-monetization-070-team-inbox.png?alt=media) *Start with work that has no owner or is due soon.* The ownership table shows current, scheduled, and superseded assignments. A scheduled assignment starts at its effective time. A later assignment replaces the current owner for the same saved item. Podigee keeps the earlier assignment in the history. One person can own their own work. A second person is not required unless a separate review rule requires one. ## Start a version-bound discussion 1. Open **Monetization > Team inbox**. 2. Choose **Start discussion**. 3. Select the saved item and exact version. 4. Select the location: whole item, named field, or an audio or video time range. 5. Select a teammate to notify when a specific person must see the message. 6. Write feedback that states what the owner must check or change. 7. Review the saved item, version, location, and message. 8. Select **Start discussion**. ![The current One Podigee discussion form shows Northstar Coffee version 2, the whole-item location, an optional teammate notification, and specific feedback.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-cc9579622170f6e0c78d7c4c718a321dbe1f4e18%2Fdoc-monetization-070-start-discussion.png?alt=media) *Attach feedback to the saved item and the place that needs attention.* The discussion stays with that version and location. It does not become a general message that can lose its product context. ## Reply and resolve 1. Open the discussion from Team inbox or Collaboration. 2. Confirm the saved item and version shown in the discussion. 3. Add a reply when the owner or reviewer needs more information. 4. Mention a teammate when another person must act. 5. Add a closing note when the requested result is complete. 6. Select **Mark resolved**. ![The current One Podigee discussion shows the saved version, the original feedback, reply field, optional teammate notification, and closing controls.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-8bac4a52bfa317227504167dc16740f5adea7e1d%2Fdoc-monetization-070-discussion.png?alt=media) *Reply in the same thread so the item and decision history stay together.* ![The current One Podigee resolved discussion shows the original feedback, the reply, the closing note, and the retained audit details.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-c7585a7342e587ab2fa8ff22b755dff85296e32a%2Fdoc-monetization-070-resolved-discussion.png?alt=media) *A resolved discussion keeps its messages, result, and audit reference.* ## Carry feedback to a newer version Use this action when the saved item changed while the discussion was open. 1. Open the old discussion. 2. Confirm that the current item has a newer version. 3. Choose **Carry forward**. 4. Confirm the current version that should receive the discussion. 5. Add a note that explains what still needs attention. 6. Save the carried discussion. Podigee creates a linked discussion on the current version. The old thread remains attached to the old version, so it cannot appear to approve the new version by accident. Resolve the old discussion when the newer version already addresses the feedback. Carry it forward only when the current version still needs the same decision or correction. ## If the owner or discussion is wrong * **The item has no owner:** assign one owner before work starts. Do not rely on a general team message. * **The version is not the current version:** resolve or carry forward the old discussion. Do not write a new approval on the old version. * **The teammate is not available:** check their Monetization access and selected scope. * **The due date is no longer correct:** create a new ownership assignment with the new effective time. Keep the old assignment in the history. * **The discussion cannot be resolved:** confirm that the exact thread and current subject version are still available, then try again. ## Expected result The saved item has one clear accountable owner, a requested result, and a visible due date when needed. Feedback, replies, resolutions, and carried discussions remain attached to the correct version and location. A comment on an older version cannot silently approve a newer version. ## Next useful task Use [Use Team inbox](/documentation/grow-and-monetize/monetization/use-team-inbox.md) for daily handoffs and discussion work. Use [Complete the required reviews](/documentation/grow-and-monetize/monetization/complete-the-required-reviews.md) when the saved version must pass a configured review rule before publication. --- # 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/assign-owners-and-discuss-exact-versions.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.