> 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/request-external-operational-input.md). # Request external operational input Ask a host or partner for one scoped contribution without giving access to the full workspace. Podigee Audio Video Ad Server lets you request one recording or document from a host, producer, buyer, agency, publisher, or other partner. After the first mention, this article uses Podigee Ad Server for the product name. The request is linked to the saved item that needs the input, has a deadline, and uses a private task page. The recipient can submit the requested file and a note. They cannot browse your Monetization workspace. The request remains useful for host-read recordings, rights evidence, delivery details, and other partner work that must stay connected to a Campaign or delivery item. ## Before you start * You have access to the item that needs the external input. * You have permission to request an external contribution. * You know the partner who should provide the input. * You know the requested result and the deadline. * You have the rights terms or instructions that the recipient must follow. ## Send a request 1. Open the Campaign or revenue job that needs the input. 2. Open the external contribution or host-read work. 3. Select **Request a recording** or **Request contribution**. 4. Select the contributor. 5. Set the due date. 6. Enter the recording instructions or requested result. 7. Confirm the rights terms and the delivery channel. 8. Review the item, contributor, deadline, and request. 9. Select **Send request**. ![A host-read recording request with the selected contributor, deadline, instructions, and send action.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-d3ebce9e9f7d8816df7dad21c25442d7c2b90f9d%2Fdoc-monetization-008-request-recording.png?alt=media) *Check the recipient and deadline before you send the private request.* Podigee creates a private, time-limited task link. Copy the link and send it only to the intended recipient. The link is limited to this request. It does not give access to the Monetization workspace, Campaigns, reports, or other partner records. ## What the recipient sees The recipient opens the task link and submits the requested file or document. For a host-read recording, the page asks the recipient to: 1. Select a supported audio or video file. 2. Add a production note when needed. 3. Confirm the recording rights. 4. Select **Submit**. ![The secure contribution page with a selected audio file, a production note, the confirmed rights statement, and the submit action.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-541e23c3ee1675e39f88177d43d523eb365e48c5%2Fdoc-monetization-008-secure-upload.png?alt=media) *The recipient submits the file and confirms the rights in one focused task.* The recipient sees only the information needed for the task. They do not need a Podigee account to submit the contribution when the private task link allows guest access. ## Check the returned input 1. Return to the external contribution or host-read work. 2. Check the request state. 3. Open the returned file or document. 4. Check the media or document validation result. 5. Read the contributor note and rights confirmation. 6. Add a review note when the input needs a change. ![The current One Podigee secure contribution page confirms that the recording was received for further checks.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-5d4a43a2208deff4fdf2464a206de619873a0427%2Fdoc-monetization-050-recording-received.jpg?alt=media) *A received contribution is not an approved contribution. Check it before you use it.* For media, use the preview to check the sound, picture, duration, and content. The returned input must pass the required checks before you accept it or connect it to delivery. ## Accept, request a change, or close the request * **Accept** the input when the file, rights, and requested result are correct. * **Request a change** when the input is incomplete or does not meet the brief. Keep the original request and explain the required correction. * **Close** the request when it is no longer needed. Do not leave an expired request open when the Campaign has moved to another source. If a review rule applies, request the required review after the input is received. A single-person operation can use the configured solo confirmation when the workspace allows it. A second reviewer is not required unless the workspace policy requires one. ## Expiry and access revocation The task link stops working after its expiry time or when the request is closed. If the recipient does not submit the input by the deadline: 1. Check the request state in the external contribution work. 2. Contact the recipient through your normal business channel. 3. Set a new deadline or close the request. 4. Send a new request when the scope or rights terms changed. Do not reuse an old link for a different recording, Campaign, or recipient. Create a new request so the input, deadline, and audit history remain correct. ## If the request is wrong * **Wrong recipient:** close the request and create a new one for the correct person. * **Wrong item or Campaign:** do not accept the returned file. Close the request and start it from the correct item. * **Missing rights confirmation:** ask the recipient to submit again with the required confirmation. * **Unsupported file:** ask for a supported format. Keep the request context and do not create a duplicate record only to bypass validation. * **Expired link:** create a new request. Do not ask the recipient to use a copied or altered URL. * **Input is no longer needed:** close the request and keep the closure reason. ## Expected result The request has one recipient, one item, one requested result, and one deadline. The returned input is stored with its rights confirmation and validation result. The recipient never receives access to unrelated workspace data, and the final acceptance or closure remains visible in the item history. ## Next useful tasks Use [Launch your first host-read sponsorship](/documentation/grow-and-monetize/monetization/launch-your-first-host-read-sponsorship.md) for a complete recording workflow. Use [Request and approve a host read](/documentation/grow-and-monetize/monetization/request-and-approve-a-host-read.md) when the returned recording must pass review and connect to a delivery break. --- # 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/request-external-operational-input.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.