---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Email retention

# Email retention {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

You can archive and eventually destroy email messages that you no longer need or if your
Email table is excessively large.

Email retention is available starting with the Helsinki release.

## Email archive and destruction plugins

The email archiving and destruction feature uses the [Data archiving](https://servicenow-prod.fluidtopics.net/60mARpaFgej2R9OvmTQDBA "Move data that's no longer needed every day from a primary table to an archive table.") and [Email
Retention](https://servicenow-prod.fluidtopics.net/948U7w6vFfvNWYI8F7_DWw "The Email Retention plugin provides archive and destruction rules for email messages. It is active by default for new instances, but must be activated for upgrades.") plugins. The Data Archiving plugin must be active to archive and destroy email records. The Email Retention plugin provides a set of rules that specify when the system archives and destroys email records.  
Note:  
The Email Retention plugin also prevents the system from deleting watermarks, which are required for inbound email actions to continue to function.

The Email Retention plugin and associated archive and destroy rules are active by default on
new instances. On upgraded instances, you must manually activate both the plugin and the archive
and destroy rules. ServiceNow recommends
that you review and approve these rules before activating them.

If your instance already has a process to manage email records, you do not need to activate
the Email Retention plugin. If you want to replace your current process with Email Retention, be
sure to deactivate the current process before activating the archive and destroy rules.

## Archiving and destroying email records

Archiving means moving records from the Email \[sys_email\] table to the Archive
Email \[ar_sys_email\] table when they exceed the archive rule time limit. Destroying
means deleting records in the Archive Email table when they exceed the destroy rule time limit.  
Note:  
When a destroy rule deletes email records, associated watermarks are not deleted. They are preserved to ensure that your inbound email actions continue to function.

## Default archive and destroy rules

Email Retention provides this email archive rule:{#email-retention__archive_destruction_rules}

Email - Over a year old or Ignored: archives email message records that were created more than 365 days prior to the current date and are of type received-ignored or
sent-ignored.

Email Retention also provides this email destroy rule:

Email Archive - Over a year old: destroys email records that have
been archived for more than 365 days prior to the current date.

With these default settings, your email messages are kept on the instance for a total of two
years: one year in the Email table, and one year in the Email archive table. At the end of this
period, the system deletes the expired email records from the Email archive table.  
Note:  
By default these rules are active on new instances and inactive on upgrades. The system runs archive and destroy rules when you activate them.

## Compatibility with other record management implementations

If you are already using another method to manage email records, such as table cleaners, you
do not have to use the Email Retention feature. To prevent unexpected record deletion, ServiceNow recommends that you avoid using
multiple email management processes on the same instance at the same time.  
Note:  
For assistance replacing your existing record management implementation with Email Retention, contact your professional services or sales representative.

## Effects of archiving and deleting email records

Inbound email actions copy the body of an email to the work notes of the related record. If
the inbound email record is later deleted, Email Received section is no longer visible in
the work notes though it still contain a text copy of the email.  
When the system sends an email message about a record, the activity formatter displays a Sent Email section with a link to the email message. If the system archives the email message, the activity formatter removes Sent Email section. When the system deletes the email message, it is no longer visible in the activity formatter nor the work notes.  
Note:  
Set the archive time length long enough so your users can access sent emails though the activity formatter.

Archiving email records changes the methods available to the system to identify inbound email
as a reply. After archiving an email record, the system can no longer use the
In-Reply-To field to match an incoming email to an email record.
However, the system can still match incoming email to an existing record from a record number or
watermark.
* **[Activate the Email Retention plugin](https://servicenow-prod.fluidtopics.net/948U7w6vFfvNWYI8F7_DWw)**   
  The Email Retention plugin provides archive and destruction rules for email messages. It is active by default for new instances, but must be activated for upgrades.
* **[Archive email manually](https://servicenow-prod.fluidtopics.net/3enyMXxts0V7Q0eMKkBJRw)**   
  You can archive email messages manually on demand instead of waiting for the instance to archive them based on a scheduled job.

**Related concepts**   

* [Email templates](https://servicenow-prod.fluidtopics.net/iXLnNLgAAE9nyHDMEbRihw "Email templates enable administrators to create reusable content for the subject line and message body of email notifications.")
* [Email layouts](https://servicenow-prod.fluidtopics.net/x5fARNzjadceeKnQXiylrQ "Create reusable content for the message body of email templates.")
* [Watermarks on notification emails](https://servicenow-prod.fluidtopics.net/bHQBtKE5oqqm0bF97yvHOw "By default, a unique watermark label will be generated at the bottom of each notification email to allow matching incoming email to existing records.")
* [Email digests](https://servicenow-prod.fluidtopics.net/TeonCpDluhL1dVG~CpZSpQ "An email digest is a single email that summarizes the activity for a selected notification and its target record during a specified time interval. You can enable an email digest to reduce the number of notifications received when frequent updates to the associated record occur within a short time period.")
* [Domain separation and Notifications](https://servicenow-prod.fluidtopics.net/XNfc92L4MJNR37JtITEWXQ "Domain separation is supported in the Notifications application. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.")
* [Email FAQs and troubleshooting notification emails](https://servicenow-prod.fluidtopics.net/SHxMvAzWvIY03fxq7AtH3g "Logs and diagnostics are provided to help determine whether notification emails are being sent and received successfully, what any issues are, and who receives the email.")  
**Related tasks**   

* [Create notification categories](https://servicenow-prod.fluidtopics.net/N2jGMUoz_N4G6Yg~OInZSg "You can create notification categories to identify and group related notifications that are listed in the notification settings for your users.")
* [Create an email notification](https://servicenow-prod.fluidtopics.net/1uxmFe3Zi5x_C3q5DOmU5Q "Create an email notification specifying when to send it, who receives it, what it contains, and if it can be delivered in an email digest.")
* [Parse an email thread](https://servicenow-prod.fluidtopics.net/_Ecer425ZkOHFbM4LlUd7w "When an email is received, parse the most recent message in an email thread by creating Email Reply Separators using specified string or regular expressions.")

