> 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/configure-operational-notifications-and-alerts.md).

# Configure operational notifications and alerts

Configure operational contacts, report recipients, and notification routes without creating alert noise.

Use **Partner governance** to keep the people and delivery routes for operational work in one controlled record. This action covers delivery, capacity, creative, review, integration, and money handoffs. It does not create a new alert for every event. It gives the right people a clear route for the material events that need action.

## Before you start

Select the correct Monetization workspace and commercial partner. You need permission to update the partner operations profile. Prepare the names of the people who handle operations, commercial work, finance, and escalation. Use destination labels that other operators can recognize.

Do not enter passwords, API keys, or private destination addresses in this form. Podigee stores those details in managed storage. The form records a safe label and the delivery method.

## Open partner operations

1. Open **Monetization > Revenue jobs > Partner governance**.
2. Select **Update partner operations**.
3. In **Where this applies**, select the correct workspace.
4. In **Commercial partner**, select the partner operations profile to update.

![The current One Podigee Orbit screen for updating partner operations shows the workspace, partner profile, and confirmation notice.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-e1c2cfdf2b0d7cd8d39d3de815efe7ce816aa5fa%2Fdoc-monetization-075-notification-settings-top.png?alt=media)

*Start with the correct workspace and partner profile.*

The page keeps the selected saved version in the action. Podigee checks the version before it applies the change, so an old partner record cannot silently receive a new route.

## Add operational contacts

Use **Operational contacts** for people who may need to act during normal work or an escalation. For each contact:

1. Enter the contact name and email or phone number.
2. Choose a **Responsibility**: Operations, Commercial, or Finance.
3. Choose a **Role**: Primary, Backup, or Escalation.
4. Select **Add contact** when you need another person.

Keep one primary person for each responsibility. Add a backup when the primary person is not always available. Use the escalation role for a person who can make a higher-impact decision.

![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)

*Use a responsibility and role so an operator knows who should act.*

## Add report recipients

Use **Report recipients** when a team member needs regular delivery, settlement, or billing reports. Choose the team member and the report type. Select **Add recipient** for another combination.

Do not add a person to every report by default. Give each person only the reports needed for the job. This keeps routine reports useful and reduces avoidable notifications.

## Configure operational notifications

Use **Operational notifications** for the route that should receive material operational events. For each route:

1. Choose a **Delivery method**: Secure link, Email, API, or SFTP.
2. Enter a recognizable **Destination name**, such as `Operations inbox`.
3. Select **Add route** when a separate route is needed.

Use a separate route when a different team owns the next action. For example, send delivery and capacity events to Operations, creative and review events to the campaign team, and money events to Finance. Use the same route only when one team truly owns all of those actions.

The route is a destination, not an event rule. Podigee decides whether an event is material from the delivery, capacity, creative, review, integration, and money state. Use **Operations**, **Team inbox**, and the linked evidence pages to investigate the event and assign an owner.

## Keep invoice and payout delivery separate

Configure **Invoice delivery** and **Payout delivery** separately from operational notifications. Choose the delivery method and destination label for each route. This prevents a finance document from appearing in an operational alert stream and makes the money handoff easier to audit.

## Review and apply the change

1. Check the workspace and partner profile again.
2. Check each contact's responsibility and role.
3. Check each report recipient and report type.
4. Check the operational, invoice, and payout delivery methods and destination labels.
5. Enter a reason that explains the operational change.
6. Select **I reviewed these details and authorize this action**.
7. Select **Apply action**.

![The current One Podigee Orbit activity record shows the completed partner-operations action with short, copyable references and a completed status.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-19dc99bc7fff181e4ea057a652391b8f4bfd75f5%2Fdoc-monetization-075-notification-receipt.png?alt=media)

*The receipt proves which saved partner-operations version was changed.*

The activity record must show **Update partner operations** and **Completed**. It includes short, copyable references for the receipt, action, item, version, and fingerprint. Use these references when you share the change with another operator or support person.

## Assign ownership and escalate

When a material event needs work, open **Monetization > Operations**. Take ownership of the issue before you diagnose or change it. The issue keeps the impact, owner, evidence, response, and recovery record together.

If a connected partner owns the next action, use **Partner support** from the issue. The action is available only when the partner operations route and a current evidence package are ready. Keep one accountable owner in Podigee and track the partner response from the issue.

For the full recovery flow, see [Manage an operational issue](/documentation/grow-and-monetize/monetization/manage-an-operational-issue.md).

## Example: route a material delivery problem

1. Add an Operations contact as Primary and a Backup.
2. Add the Operations team member as a recipient for delivery performance reports.
3. Add a Secure link route named `Operations inbox` for operational notifications.
4. Add separate Finance routes for invoices and payouts.
5. Apply the action and keep the activity receipt.
6. When a delivery issue appears, take ownership in **Operations**.
7. Escalate to the partner only when the issue evidence and route are ready.

## Expected result

Material events reach the people who can act, routine reports go only to the people who need them, and finance documents stay separate from operational alerts. Every route change has an accountable owner, a saved version, and a short activity receipt that can be checked later.


---

# 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/configure-operational-notifications-and-alerts.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.