> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/sami-b2b-onboarding/settings/notification-recipients.md).

# Choose who gets notified

Choose who on your team receives the app's emails, give a form its own list, and turn on the daily summary of applications waiting for review.

Sami B2B Onboarding emails your team when there is something to act on. You choose the people once in **Settings › Email**, and you can give any application form a list of its own, for example so distributor applications reach a different team.

These emails go to your team:

| Email                     | When it's sent                                                                                                                                    | On at first |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
| **New application**       | A buyer submits an application.                                                                                                                   | Yes         |
| **Buyer resubmitted**     | A buyer sends the information you asked for.                                                                                                      | Yes         |
| **Daily pending summary** | Each morning around 8 a.m. in your store's time zone, with how many applications are waiting for review. Skipped on days when nothing is waiting. | No          |
| **Import completed**      | A company import from a CSV file finishes.                                                                                                        | Yes         |

## Who receives a team email

The app looks for recipients in this order and uses the first list that has anyone in it:

1. **The form's own recipients**, for **New application** and **Buyer resubmitted**, if the form has a list in the builder's **Email** section.
2. **Default recipients** in **Settings › Email**.
3. **A fallback address.** The store owner's email once they have opened the app, otherwise your store's contact email in Shopify. **Settings › Email** shows this address under the default list: "When this list is empty, emails go to …", followed by the address.

All recipients get the same email together, so they can see each other's addresses.

## Set your default recipients

{% stepper %}
{% step %}

### Open Default recipients

In the app, click **Settings**, then click **Email**. Find the **Default recipients** card.
{% endstep %}

{% step %}

### Add people

Click **Add an email** in **Recipients**. A list opens with the email addresses of the people on your team who have opened the app, apart from collaborator accounts. Click an address to add it, or type any email address and press `Enter`. Add as many as you need.

To remove someone, click the **×** on their address.

<figure><img src="https://3844812229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRrf4pQPgjvb3GW7IN3Ci%2Fuploads%2Fgit-blob-b5712aea2bf9474edd5f2eafe5eaa5dfd2900a04%2Fscreenshot-email-default-recipients.png?alt=media" alt="The Default recipients card with two addresses added and the Recipients list open, where team members&#x27; addresses can be ticked or a new address searched for."><figcaption><p>Pick team members from the list, or type any email address and press Enter.</p></figcaption></figure>
{% endstep %}

{% step %}

### Save

Click **Save** in the save bar. The next team email goes to everyone on the list. If an address isn't valid, the save stops with "… isn't an email address we can send to." Fix or remove it, then save again.
{% endstep %}
{% endstepper %}

## Give a form its own recipients

Use this when different forms belong to different teams. The form's list replaces the default recipients for that form's **New application** and **Buyer resubmitted** emails.

{% stepper %}
{% step %}

### Open the form's Email section

Go to **Forms** and click **Edit** beside the form, for example **Wholesale application**. In the rail on the left of the builder, click **Email**.

A form that has never been saved shows "Save the form once before editing its emails." Save it first.
{% endstep %}

{% step %}

### Add the form's recipients

Under **Who hears about this form**, click **Add an email** and add people the same way as on **Settings › Email**. While the list is empty, the section says "Using the default recipients on Settings → Email." If the default list is empty too, it names the fallback address the emails go to instead.

<figure><img src="https://3844812229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRrf4pQPgjvb3GW7IN3Ci%2Fuploads%2Fgit-blob-6a6b32acf7128e5bc35d10e626c4671fd93144e1%2Fscreenshot-builder-email-recipients.png?alt=media" alt="The form builder&#x27;s Email section with one address under Who hears about this form, above the lists of buyer and team emails."><figcaption><p>A form's own recipients replace the default list for that form's team emails.</p></figcaption></figure>
{% endstep %}

{% step %}

### Save the form

Click **Save** in the builder's save bar.
{% endstep %}
{% endstepper %}

To go back to the default list, remove every address from **Who hears about this form** and save the form.

## Turn on the daily pending summary

The summary is off when you install the app.

{% stepper %}
{% step %}

### Find Store emails

Go to **Settings › Email** and find **Store emails**.
{% endstep %}

{% step %}

### Turn the summary on

Under **Sent to your team**, turn on the switch next to **Daily pending summary**.
{% endstep %}

{% step %}

### Save

Click **Save** in the save bar.
{% endstep %}
{% endstepper %}

From then on, the default recipients get one email a day, sent from 8 a.m. in your store's time zone. It says how many applications are waiting for review (new ones and ones the buyer sent back), and its **Open the review queue** button opens them in the app. On a day with nothing waiting, no email is sent.

## Turn team emails off

An empty recipient list doesn't stop team emails: they go to the fallback address instead. To stop an email, turn it off.

| Email                                           | Where to turn it off                                                                                                    |
| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **New application**, **Buyer resubmitted**      | For one form: **Forms** › **Edit** › **Email**, then turn off its switch under **Sent to your team** and save the form. |
| **Daily pending summary**, **Import completed** | **Settings › Email › Store emails**: turn off its switch and click **Save**.                                            |

The **New application** email also stops when **Application received** is off under **Automation › Automations**, and **Buyer resubmitted** when **Application revised** is off. Turning off **Application received** also stops the buyer's **Application received** email. See [Automations and Shopify Flow](/sami-b2b-onboarding/automation/automations-and-shopify-flow.md).

## Next steps

* [Edit email templates](/sami-b2b-onboarding/settings/email-templates.md) — change what each team email says.
* [Team and roles](/sami-b2b-onboarding/settings/team-and-roles.md) — add the people you want to pick as recipients.
* [Send from your own address (SMTP)](/sami-b2b-onboarding/settings/smtp.md) — send team emails through your own mail server.
* [Activity log](/sami-b2b-onboarding/settings/activity-log.md) — check which emails went out and to whom.


---

# 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.samita.io/sami-b2b-onboarding/settings/notification-recipients.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.
