> 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/manage-partner-contacts-and-eligibility.md). # Manage partner contacts and eligibility Keep partner contacts, delivery identities, and capability access current and safe. Podigee Audio Video Ad Server keeps partner contacts, delivery identities, and capability access in one controlled context. After the first mention, this article uses Podigee Ad Server for the product name. Use this task when a buyer, seller, agency, publisher, demand provider, or other partner changes people, routes, identities, or delivery eligibility. Contacts explain who acts. Identities explain which seller, seat, or supply-chain path a provider may use. Eligibility explains which certified delivery capabilities may run. These records are related, but they are not the same record. ## Before you start * Select the correct Monetization workspace and commercial partner. * Have permission to update partner operations, register identities, or change eligibility. * Confirm the current partner agreement and the connector certification. * Prepare the contact details, seller ID, seat IDs, supply-chain nodes, and applicable capabilities. * Know the effective time and the reason for the change. ## Keep operational contacts current 1. Open **Monetization > Revenue jobs > Partner governance**. 2. Select **Update partner operations**. 3. Select the workspace and commercial partner. 4. Add one contact for each responsibility: Operations, Commercial, or Finance. 5. Set the role to **Primary**, **Backup**, or **Escalation**. 6. Add report recipients only for reports they need. 7. Add operational, invoice, and payout routes with clear destination names. 8. Set **Valid until** when the contact or route must be reviewed again. 9. Review the partner version and apply the action. ![The current One Podigee Orbit partner-operations form shows an operational contact with a name, contact detail, responsibility, and role.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-97d3afb9e1583309606b6a021d9f64c594b284e7%2Fdoc-monetization-075-notification-routes.png?alt=media) *Give each contact a responsibility and a role so the next action is clear.* Keep one Primary contact for each responsibility. Add a Backup when the Primary contact may be unavailable. Use Escalation for a person who can make a high-impact decision. Do not add every person to every report or route. ## Register seller, seat, and supply-chain identities Use **Register a programmatic identity** when a partner needs a programmatic seller identity. The identity belongs to the selected partner version and can be used by a certified connector. 1. Open **Monetization > Revenue jobs > Partner governance**. 2. Select **Register a programmatic identity**. 3. Select the commercial partner. 4. Enter the seller ID. 5. Add at least one buyer or seller seat ID. 6. Add each supply-chain node in the order used for the request. 7. Select the standards profile. 8. Check the identity, partner, and connector details. 9. Apply the action and keep the receipt. Do not type a secret, credential, or unverified provider value into an identity field. Use the managed credential process for secrets. Register a new version when the seller, seat, supply-chain node, or standard changes. Keep the old version for records and old delivery evidence. ![Seller authority details for one Harbor and Pine Inventory portfolio, including the seller, revenue beneficiary, authority period, external reference, and notes.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-01726a6766945e6a0b5be55b62eae132b716e8e1%2Fdoc-monetization-013-seller-beneficiary-window.jpg?alt=media) *The seller identity must match the authority and the inventory scope.* ## Pause, resume, or revoke delivery access Use **Change partner eligibility** when a partner must stop or regain access to one or more certified capabilities. 1. Open **Monetization > Revenue jobs > Partner governance**. 2. Select **Change partner eligibility**. 3. Select the commercial partner. 4. Select the certified connector. 5. Choose **Pause access**, **Enable or resume access**, or **Revoke access**. 6. Choose only the affected delivery capabilities. 7. Set **Effective from**. 8. Select an approved reason when one applies. 9. Check the certification and authority notice. 10. Apply the action. Use **Pause access** for a temporary problem, such as a failed provider check or a short policy restriction. Use **Enable or resume access** after the connector, authority, and evidence are current again. Use **Revoke access** when the capability must not return without a new decision. Eligibility is capability-specific. Pausing video demand does not need to stop an independent audio path. Select only the capabilities that the evidence supports. ## What changes for delivery The eligibility change applies at its effective time. A paused or revoked capability cannot win a new delivery decision. Existing evidence remains available for reporting and reconciliation. A restored capability still needs a current connector certification, authority, identity, and policy before it can run. If the form says that certification or authority is not ready, do not bypass the warning. Repair the connector or authority record first. A partner can remain paused while the evidence is reviewed. ## Keep contacts and eligibility aligned Review these records together when a partner changes: * Contact responsibility and escalation route. * Seller and seat identity. * Supply-chain nodes. * Connector certification and supported media. * Markets, privacy rules, and delivery capabilities. * Effective time and review date. Changing a contact does not change delivery eligibility. Changing eligibility does not update a contact. Apply each change to the correct record and keep its receipt. ## If a partner no longer meets policy 1. Take ownership of the operational issue. 2. Record the failed requirement and affected capabilities. 3. Pause only the unsafe or unsupported capabilities. 4. Notify the Primary or Escalation contact through the configured route. 5. Keep the last safe eligibility state and the evidence package. 6. Restore access only after the current connector and authority pass their checks. Do not delete the partner, identity, contact, or old eligibility record to hide a failed check. Create a successor version or a declared eligibility change so the history remains complete. ## Expected result Each partner has clear operational contacts, the correct seller and supply-chain identity, and an eligibility state for each certified capability. The effective time, reason, evidence, and receipt show why a capability can run, is paused, or was revoked. Delivery uses only the current safe state. ## Next useful tasks Use [Configure operational notifications and alerts](/documentation/grow-and-monetize/monetization/configure-operational-notifications-and-alerts.md) for detailed contact and route settings. Use [Connect an OpenRTB demand source](/documentation/grow-and-monetize/monetization/connect-an-openrtb-demand-source.md) when you must certify a provider before it can receive demand. --- # 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/manage-partner-contacts-and-eligibility.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.