> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/ads/requests-from-partners/review-email-drop-requests-from-partners.md).

# Review Email Drop Requests from Partners

Some of the partners you work with may advertise or promote your brand via email. These partners can submit requests to you for content, and your suppression list.

* Partners can request to use your existing email ad content from you to drive actions on their channels.
* You can approve or decline these requests and provide approved email ad content for them to use—they'll also have access to your suppression list when approved.
* Partners can also request new email ad content from you—once created, they must then submit an email drop request to use it.

#### Approve or decline requests

1. From the left navigation menu, select ![](/files/CDnwOBeIdds9r3Z6zTnO) **\[Engage]** → **Content → Requests**.
2. In the *Requests* list, find the *Email Drop* request type.
3. To the far right, select ![](/files/mQTDSmR70Q3Eybmgev6e) **\[Menu] →** **Process**.
4. Review the *Request Details*, and **optionally leave a response** to the requesting partner.
5. Select **Reject Request** or **Approve** to complete the process.

When you approve an email drop request from a partner, you are providing them access to one of your pre-created email ads. When approved, partners will have access to your suppression list as configured for the email ad content.


---

# 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://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/ads/requests-from-partners/review-email-drop-requests-from-partners.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.