> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Configure partner notifications by email
> Choose which partner notifications go out by email, scope them to the right partners, and turn on reply-by-email so partners respond from their inbox.
## What you'll achieve
Partner notifications delivered by email for the events you care about, scoped to the right partners, with reply-by-email turned on so partners can respond from their inbox. Partners stay engaged off-portal and their replies land back in Introw.
## Before you start
Partners need valid email addresses on their contacts. See [Troubleshoot partner email delivery](./troubleshoot-partner-email-delivery) if someone is missing messages.
## Watch it
## Steps
Go to [Default settings](https://app.introw.io/settings/segments/default) and open the **Notifications** tab. Events are grouped by area, **Pipeline**, **Portal activity**, **Submissions**, **Tasks**, and **Learning**, so you can scan them by section.
Give every event the audience it deserves: **All partners**, **Collaborating only** for events attached to a CRM record, or **Disabled**. Pipeline (deal and object updates), announcements, submission outcomes, and task assignments are common starting points. Leave lower-value events disabled until partners need them, since too many emails overwhelm rather than engage.
This one value is the whole email decision for that event. There is no separate channel checkbox: email is available for every partner notification, so anything not disabled reaches every eligible partner with a valid address.
To send a program-specific email only to the partners it applies to, open that audience's segment, go to its **Notifications** tab, and switch on **Override the default for this segment**. The override replaces the default for that segment's members, so it can hold an event back as well as open it up.
Each partner contact resolves against the same three-layer cascade (organisation default, then override segments they match, then the contact's own opt-outs), so see [Control who gets notified](/features/engagement/notifications/guides/control-who-gets-notified) to check why a specific contact is or is not receiving an email.
Collaboration emails, comments, deal and object updates, and submission outcomes, include **Respond via email**. Partners can reply from their inbox and the response appears in Introw. For commission payouts, partners can reply with their invoice attached.
To route replies to a real person, send from each partner's assigned manager, see [Wire partner ownership](/features/partners/team/guides/wire-partner-ownership).
By default these emails send from an Introw address. To have them send from your own authenticated domain, so they arrive as your brand and land in the inbox instead of spam, set up a custom sending domain. See [Send notifications from your own domain](/features/portal/email-domain/guides/send-notifications-from-your-own-domain).
[Notification settings](https://app.introw.io/settings/notifications) is the report on what your program sends. The **Last sent** column updates after the next real event, and **Insights** shows emails sent and opened, so you can confirm the channel is firing.
## Verify it worked
**Insights** shows emails sent and opened, and **Last sent** updates on the row after the next event on any event you left enabled.
## Related
Deliver notifications in Slack instead of or alongside email.
Deliver notifications in Teams.
Fix missing partner emails.
Authenticate a custom sending domain so notifications come from your brand.
Full configuration options for partner notifications.