diff --git a/docs/best-practices.md b/docs/best-practices.md
index 4f8f31cd644dfbd593d56381cefc3e0696ecdbba..fcb05e0991f11184b4ff27aca4596c97989e4c0a 100644
--- a/docs/best-practices.md
+++ b/docs/best-practices.md
@@ -7,3 +7,4 @@ Here are some recommended best practices for designing and working with integrat
 * [AWS S3 as a Flat file alternative](best-practices/flat-file-alternative.md)
 * [Cloud Data Integration (CDI) vs. Cloud Application Integration (CAI)](best-practices/cai-vs-cdi.md)
 * [Migrating Assets between Organizations](best-practices/asset-migration.md)
+* [Email Alerting](best-practices/email-alerting.md)
diff --git a/docs/best-practices/email-alerting.md b/docs/best-practices/email-alerting.md
new file mode 100644
index 0000000000000000000000000000000000000000..bedf1294d674ab9253ab636b8c0197dec6774ade
--- /dev/null
+++ b/docs/best-practices/email-alerting.md
@@ -0,0 +1,11 @@
+# Email Alerting
+
+It's important to know when your integration fails and why.  If no email is entered, no one will be alerted that an integration fails and it may be very inconvenient if things start falling apart. 
+
+## Tutorial
+
+Informatica has created a [knowledgebase article located here](https://knowledge.informatica.com/s/article/496185?language=en_US) to help you through the process in adding your email into your tasks and task flows.
+
+## Confirmation
+
+Success alerts can also be configured in this way, letting you know your integration ran without issue.