> 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/understand-where-to-do-daily-work.md). # Understand where to do daily work Choose the shortest correct One Podigee surface for each daily advertising and revenue task. The Podigee Audio Video Ad Server gives you several work surfaces in one Monetization context. Each surface has a clear purpose. Use this map to start in the correct place and avoid unnecessary steps. ## Start with this decision map | Your current need | Start here | | --------------------------------------------------------------- | ------------------------- | | You are not sure what needs attention | **Control Room** | | You need to compare Flights across Campaigns and dates | **Flightboard** | | You need a guided path for a specific or less frequent job | **Revenue jobs** | | You must make a formal decision on an exact saved version | **Approvals** | | You must assign work, discuss a saved item, or review a handoff | **Team inbox** | | You must plan or change one Campaign or Flight | **Campaigns** | | You must prepare supply, packages, or episode ad breaks | **Inventory** | | You must upload, inspect, or prepare an ad | **Creatives** | | You must understand delivery, reports, revenue, or a difference | **Evidence & Money** | | Delivery is at risk or recovery work is open | **Operations** | | You must connect or verify another system | **Integrations** | | You must change workspace rules or controlled values | **Monetization settings** | ## Use Control Room when you need direction Control Room is the normal starting point. It shows the current commercial accounts, Campaigns, Creatives, active delivery, and team handoffs. It also gives direct links to the most common work. ![The current One Podigee Control Room shows the Monetization context, current totals, Campaign work, Creative readiness, Team inbox, and the complete Monetization navigation.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-26951aea79eaafa011049469c1f81335287fd85b%2Fdoc-monetization-065-control-room.png?alt=media) *Start here when you need a summary or do not yet know which area owns the next action.* Do not use Control Room as the final evidence page. Open the linked Campaign, handoff, report, or operational issue when you need exact details. ## Use Flightboard for cross-Campaign delivery work Flightboard puts delivery promises on one operating timeline. Use it to compare schedules, delivery, forecast, capacity, planned value, earned value, and operating state across Flights. ![The current One Podigee Flightboard shows the current Flight count, work that needs attention, reserved capacity, planned value, the next seven days, and Flight filters.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-5f01c9462cb55a5dceb4afd96d49778e4635de24%2Fdoc-monetization-065-flightboard.png?alt=media) *Use Flightboard when the question covers several Flights, Campaigns, or delivery dates.* Open the Campaign from the Flight row when you need to change terms, targeting, Creative coverage, or the exact Flight setup. ## Use Revenue jobs for guided work Revenue jobs is the complete directory of governed work. It includes commercial authority, policies, inventory, breaks, Campaign planning, forecasting, reviews, publishing, live delivery, reporting, finance, marketplace work, integrations, and support. ![The current One Podigee Revenue jobs page organizes guided work by business result and shows whether each job area is ready.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-83097b877505294df90da1732586f8b83f2c0004%2Fdoc-monetization-065-revenue-jobs.png?alt=media) *Use Revenue jobs when the job is less frequent or when you want Podigee to guide the required checks.* If a common object already exists, open it directly from Campaigns, Inventory, Creatives, or the related evidence page. You do not need to enter through Revenue jobs each time. ## Separate formal decisions from teamwork Use **Approvals** only for a governed decision on an exact saved version. The request can require approval, return, rejection, or cancellation under the current review rule. Use **Team inbox** for ownership, handoffs, discussions, and requested input. A discussion does not replace a formal approval. ![The current One Podigee Team inbox shows saved-item discussions, exact feedback locations, teammate notification, accountable ownership, and handoffs.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-461d1a4f88c78fc3ea0d4425abaf655f18212cd4%2Fdoc-monetization-065-team-inbox.png?alt=media) *Use Team inbox when another person must own, review, or comment on the work.* If you work alone, the workspace can use solo confirmation or optional review where policy permits it. You do not need to create a second user only to complete routine work. ## Use the object areas for direct work Use the primary object areas when you already know what you must change: * **Campaigns** for Campaign terms, Flights, targeting, pricing, Creative assignments, capacity, readiness, and publication. * **Inventory** for sellable packages, delivery methods, content scope, and episode ad breaks. * **Creatives** for audio and video masters, prepared versions, preview, rights, and readiness. * **Marketplace** for publisher supply, buyer proposals, deals, and external demand sources. These areas keep the object and its related work together. Start with the object instead of a general report when your goal is to change its setup. ## Separate proof from recovery Use **Evidence & Money** when you need to answer what happened. It includes delivery decisions, qualified delivery, revenue, reports, report runs, reconciliation, and month-end preparation. Use **Operations** when delivery is at risk or when recovery work is open. It brings together delivery holds, high-impact issues, incidents, delayed evidence, and recovery actions. Do not use Operations for routine Campaign planning. Do not use a report to change a live Campaign. Open the exact Campaign or governed action from the evidence or issue. ## Use the shortest correct route Follow this order when several surfaces could apply: 1. Open the exact object if you already know it. 2. Open the formal request if another person must decide it. 3. Open the handoff if another person must own or discuss it. 4. Open Evidence & Money if you need proof of a result. 5. Open Operations if delivery or evidence is at risk. 6. Open Revenue jobs if the correct object or action is not clear. 7. Return to Control Room when you finish and check the next important item. ## Expected result You start each daily job in the surface that owns the result. You use fewer navigation steps, keep formal decisions separate from discussions, and move from summary to exact work without losing context. --- # 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/understand-where-to-do-daily-work.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.