> 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/establish-seller-and-representation-authority.md).

# Establish seller and representation authority

Record seller, revenue, and representation authority for podcast inventory.

This task shows how to record commercial authority in the Podigee Audio Video Ad Server. Use **seller authority** for inventory that your organization sells. Add a **representation agreement** only when one organization sells or manages advertising for another publisher.

Complete this task before you plan a Campaign for the affected inventory.

## Before you start

You need:

* Access to **Monetization** and permission to manage commercial authority.
* The workspace or Inventory portfolio that the authority covers.
* The legal entity that may sell the inventory.
* The legal entity that receives the revenue.
* The authority start and end dates.
* For representation, the agreed rights, demand sources, approval rules, visibility, fees, and revenue share.

Create or link the required legal entities before you start. Do not use a brand name or a person in place of a legal entity.

## Choose the correct authority

Use this rule:

* If your organization sells its own inventory, create **seller authority**.
* If your organization acts for another publisher, create seller authority and a **representation agreement**.

A representation agreement does not replace seller authority. It limits what the representative may do for the represented organization.

Seller authority does not replace the publisher's legal ownership records. It records who may sell the selected inventory and who receives its revenue.

## 1. Open seller authority

1. Open **Monetization**.
2. Go to **Revenue jobs**.
3. Open **Authority and commercial context**.
4. Select **Set up seller authority**.

![The Set up seller authority action with the workspace review mode and high-impact confirmation notice.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-b9e19d5968d6603ac9a7d4d77bd91c0ea1e0e8b0%2Fdoc-monetization-013-seller-authority-overview.jpg?alt=media)

*The page shows the review rule that applies before the authority can be published.*

## 2. Create the seller authority draft

1. In **What do you want to do?**, select **Create draft**.
2. In **Where this applies**, select the workspace or the exact Inventory portfolio.
3. In **Selling company**, select the legal entity that may sell the inventory.
4. In **Revenue beneficiary**, select the legal entity that receives the revenue.
5. Set the **Authority period**.
6. Add an external seller reference if a sales partner uses one.
7. Add a short internal note that explains the commercial scope.
8. Enter the reason for the change.
9. Confirm the action and select **Start**.

![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 scope, seller, beneficiary, and authority period must match the real commercial agreement.*

Podigee saves a draft. A draft does not authorize sales or delivery.

## 3. Review and publish seller authority

1. Open **Set up seller authority** again.
2. Select **Publish**.
3. Select the same workspace or Inventory portfolio that you used in the draft.
4. Select the exact saved seller authority.
5. Complete the review step shown by your workspace:
   * For solo confirmation, select **Confirm this exact change yourself**.
   * For independent review, use the approved request from the other authorized reviewer.
6. Enter the reason, confirm the action, and select **Start**.

The scope on the publication form must match the scope of the saved authority. Podigee blocks a workspace publication when the draft covers only one portfolio.

![The activity record after seller authority was published successfully.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-3cdaccc48f2c1cd8a898e87c3a78430c11330749%2Fdoc-monetization-013-seller-authority-published.jpg?alt=media)

*The activity record confirms that the seller authority action completed.*

## 4. Create a representation agreement

Complete this section only when one organization acts for another publisher.

1. Go to **Revenue jobs > Authority and commercial context**.
2. Select **Authorize seller representation**.
3. Select **Create draft**.
4. Select the exact workspace or Inventory portfolio.
5. Select the **Represented organization**.
6. Grant only the rights that the representative needs. Rights can include selling inventory, planning Campaigns, forecasting supply, assigning Creative, and viewing reports.
7. Set the agreement start and end dates.
8. Select the allowed demand sources, such as direct-sold, programmatic, or Marketplace demand.
9. Set pricing authority, publisher approval, forecast visibility, and reporting visibility.
10. Record the financial terms, revenue beneficiary, and represented organization share.
11. Allow delegation only when the agreement permits another approved party to act.
12. Select the representative, enter the reason, confirm the action, and select **Apply action**.

![Representation financial terms with shared revenue, an 80 percent publisher share, no delegation, and the selected representative.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-a4629d5fd570ff2cd892375bb26c4293a4160f04%2Fdoc-monetization-013-representation-terms.jpg?alt=media)

*Revenue terms must agree. A shared beneficiary requires a represented organization share between 1 and 99 percent.*

Use a specific portfolio when the agreement does not cover all workspace inventory. Podigee blocks overlapping published agreements for the same scope and period.

## 5. Submit, accept, and publish the agreement

A representation agreement has a counterparty step. Complete the actions in this order:

1. Select **Submit for approval** and send the exact draft to the representative.
2. The selected representative reviews the terms and selects **Accept**.
3. An authorized publisher operator selects **Publish**.
4. Complete the workspace review step and confirm the exact publication.

The agreement becomes active only after publication. A submitted or accepted agreement is not enough.

![The activity record after the portfolio representation agreement was published successfully.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-b790adda418042a01670155766c9f4e1732f40a1%2Fdoc-monetization-013-representation-published.jpg?alt=media)

*The activity record confirms that the accepted representation agreement was published.*

If the counterparty does not agree, use **Reject** and record the reason. Create a new draft for material changes. Do not change the history of the rejected agreement.

## 6. Renew representation without a gap

Start renewal before the current agreement expires.

1. Go to **Revenue jobs > Partner governance**.
2. Select **Renew a representation agreement**.
3. Select the scope and the exact published agreement.
4. Confirm the represented organization, counterparty, carried rights, and exact handover time.
5. Set the end date for the new agreement.
6. Enter the reason, confirm the action, and select **Apply action**.
7. Ask the counterparty to review and accept the successor agreement.

Podigee starts the successor when the current agreement ends. The current agreement remains active until then, and the successor waits for counterparty acceptance.

![The activity record after a successor representation agreement was created for renewal.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-1bcd22869074dc2a796199ca33c29630762b54cc%2Fdoc-monetization-013-representation-renewal.jpg?alt=media)

*The renewal record confirms that Podigee created the successor agreement and preserved the handover.*

## End or replace authority safely

* Use **End** when the authority must stop and no successor will replace it.
* Create a successor when the seller, beneficiary, rights, scope, or period changes.
* Publish only the exact saved version that all parties reviewed.
* Keep the current authority active until the successor is ready when continuous sales authority is required.

Do not edit historical evidence to represent a new agreement.

## If Podigee blocks the action

* **The scope does not match:** Select the workspace or portfolio used by the saved authority.
* **Another authority overlaps:** Narrow the scope, change the period, or renew the existing agreement.
* **Revenue terms do not agree:** Match the beneficiary to the share. Use 100 percent for the represented organization, 0 percent for the representative organization, or 1 to 99 percent for a shared beneficiary.
* **A review is missing:** Complete the solo confirmation or the independent review required by the workspace.
* **A legal entity is missing:** Create or link the Commercial account and legal entity before you continue.

Podigee keeps the last valid published authority when a new action fails.

## Result

The selected inventory has an exact seller, revenue beneficiary, scope, and authority period. If a representative acts for another publisher, the published agreement also limits its rights, demand, visibility, approvals, and financial terms.

Next, create or link the Commercial accounts that your ad operation needs.


---

# 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/establish-seller-and-representation-authority.md?ask=<question>&goal=<endgoal>
```

`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.