> 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/new-ad-operations-team-learning-path.md). # New ad operations team learning path A guided path for a team that shares campaign planning, reviews, delivery, and reporting. This path shows how a small or mid-sized team can run the Podigee Ad Server together. It starts with the solo first success path, then adds clear ownership, handoffs, independent review, and daily delivery checks. ![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) *Give each important result one accountable owner.* ## Before you start Read [New solo operator learning path](/documentation/grow-and-monetize/monetization/new-solo-operator-learning-path.md) first. Then make sure each teammate can open the workspace and the shows that they support. Agree on these points before the first Campaign: * Who prepares inventory and ad breaks. * Who plans Campaigns and reserves capacity. * Who uploads and checks Creatives. * Who reviews changes when a second person is required. * Who publishes approved work. * Who checks delivery and reports each day. ## Build the team workflow ### 1. Give work a clear owner Use [Assign owners and discuss exact versions](/documentation/grow-and-monetize/monetization/assign-owners-and-discuss-exact-versions.md). Assign one person to the result, not to a vague area. Add a due date and keep comments attached to the exact saved version that needs work. ### 2. Use the Team inbox for handoffs Use [Use Team inbox](/documentation/grow-and-monetize/monetization/use-team-inbox.md) to see work that is assigned to you, due soon, waiting for another person, or blocked. Reply in the same discussion when the item needs clarification. Resolve the discussion when the requested result is complete. ### 3. Configure the right review mode Use [Configure review rules](/documentation/grow-and-monetize/monetization/configure-review-rules.md) and [Complete the required reviews](/documentation/grow-and-monetize/monetization/complete-the-required-reviews.md) to choose the smallest safe review process. Use no approval, optional review, or Solo confirmation when a second person is not needed. Use independent review for changes that need separation of duties. ![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) *Review the exact version shown in the request.* ### 4. Run one Campaign together Use [Launch your first audio and video campaign](/documentation/grow-and-monetize/monetization/launch-your-first-audio-and-video-campaign.md). The planner sets the buyer promise and forecast. The inventory operator checks eligible supply. The Creative operator uploads and previews the master. The reviewer checks the exact version when the policy requires it. The publisher activates only the approved setup. ### 5. Establish a daily check Start in [Understand where to do daily work](/documentation/grow-and-monetize/monetization/understand-where-to-do-daily-work.md). Check delivery, fill, pacing, no-fill, creative readiness, and items waiting in Team inbox. Assign an owner before you ask a team to fix a problem. Use [Read Campaign and creative performance](/documentation/grow-and-monetize/monetization/read-campaign-and-creative-performance.md) for business results. Use [Investigate an auction or deal result](/documentation/grow-and-monetize/monetization/investigate-an-auction-or-deal-result.md) when the issue affects Marketplace or connected demand. ## Keep reviews useful The review mode belongs to the workspace and the action family. It does not mean that every action needs a second person. A solo operator can confirm their own Campaign when Solo confirmation is enabled. A team can reserve independent review for high-risk changes, such as a new delivery destination, a finance mapping, or a large Campaign amendment. Never use a chat message as the only approval record. Keep the decision, the item version, the rule, and the reason in the saved request. ## If the team is blocked * **No one owns the work:** assign one accountable owner in Team inbox. * **The reviewer sees a newer version:** close or carry forward the old discussion, then review the current version. * **The review rule is too strict:** ask an administrator to change the rule for that action family. * **The Campaign cannot meet its promise:** return to the forecast and capacity step before launch. * **Delivery is wrong:** use the delivery evidence and keep the Campaign version unchanged until the owner understands the cause. ## Expected result Every active Campaign has an owner, a clear handoff, and the smallest review process that is safe for the workspace. The team can see what is ready, what is waiting, what is live, and what needs attention without relying on private messages. ## Next useful path Use the Sales planner or account executive learning path when the team needs a buyer-to-booking workflow. Use the Campaign and traffic operator learning path when the team needs detailed trafficking and pacing work. --- # 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/new-ad-operations-team-learning-path.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.