# 'Per Connector' Email Deduplication Option

As part of day-to-day processing in Email systems and integration with other systems, it is possible for errors to result in duplicate emails. To combat this Enate provides built-in capabilities to deduplicate received emails. Let’s take a look at the details for this.

#### Enate Email Deduplication Logic

As a core principle, Enate will generate or update 1 Work Item per received Email after deduplication. To guard against accidental creation of multiple work items caused by duplicate incoming emails, Enate checks for such duplicates and deduplicates them so that only one work item is created. This is how Enate is set up as standard, and is termed ‘Global Level deduplication’.

* <mark style="color:blue;">**Global Level Deduplication**</mark> (default) – where emails deduplication logic is run globally on all emails, and any mails considered duplicate are *always* de-duped.

However in some business operations, it is possible that the same exact email will be explicitly forwarded into two different parts of the business, with the intention of creating two different work items in Enate. In order to allow this, Enate has now introduced a new feature to allow this deduplication scope to be at a 'per email connector' level:

* <mark style="color:blue;">**Per-Connector Level Deduplication**</mark> – where emails are deduped if received into the same individual Email Connector, but are not deduped if the two mails are sent into two separate Email Connectors in Enate.\
  **In Per-Connector mode, Enate will only search for existing Emails that have been received to the same Email Connector as configured in Enate.**

{% hint style="info" %}
Note: This is a database-level setting - if you want to make this change you should get in touch with Enate Support via the Helpdesk.
{% endhint %}

For a more detailed discussion of Email Deduplication, including likely Email Server behaviour and the impact on work item creation in Enate, check out the [Email Receipt and Deduplication](https://docs.enate.net/enate-help/builder/builder-2021.1/email-mailbox-configuration/email-receipt-and-deduplication) section in the main help articles.


---

# Agent Instructions: 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:

```
GET https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2022.2-changes-overview/builder-changes/per-connector-email-deduplication-option.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.