diff --git a/rules/do-you-know-not-to-send-attachments-in-emails/rule.md b/rules/do-you-know-not-to-send-attachments-in-emails/rule.md index cfe5c9b95a0..033c6642551 100644 --- a/rules/do-you-know-not-to-send-attachments-in-emails/rule.md +++ b/rules/do-you-know-not-to-send-attachments-in-emails/rule.md @@ -19,15 +19,17 @@ guid: 25648802-8fef-4ddd-94ad-41c2d3d649ab How you work with attachments should change depending on who you are emailing. -If you're sending to a fellow employee, use a link to a document store on your intranet (E.g.: `intranet.northwind.com/SharedDocuments`) +For internal communications, linking to a document store on the intranet keeps files accessible, up-to-date, and minimizes the risk of broken links. When communicating externally, attaching the file directly is often more convenient for recipients who may not have access to internal systems. + + -If you're sending to a client, either get them to share a publically available link or attach the files to the email (recommended). E.g.: For a Spec Review. +## Internal documents - +If you're sending to a fellow employee, **use a link** to a document store on your intranet (E.g.: `intranet.northwind.com/SharedDocuments`) -### Internal Docs +When sharing documents internally it's best to keep the work alive in a link. The best way to do that is to have it hosted in one place where all working parties can access it. -When sharing documents it's best to keep the work alive and the best way to do that is to have it hosted in one place where all working parties can access it. Using SharePoint will also help minimize broken links. +**Tip:** Using SharePoint will help minimize broken links. ::: bad ![Figure: Bad example - Don't attach documents to emails when sending internally](bad-example-email-attachments.png) @@ -37,22 +39,22 @@ When sharing documents it's best to keep the work alive and the best way to do t ![Figure: Good example - The file is shared from SharePoint and everyone can work on the same document](good-example-sharepoint.png) ::: -### External Docs +## External documents + +If you're sending to a client, either get them to share a publically available link, or **attach the file** to the email (recommended). E.g.: For a Spec Review. -When communicating with external contacts, it's often easier to attach the file than share a link due to permission issues. This also allows them to share the document internally and always have access to the copy. +It's often easier to **attach the file** than share a link due to permission issues. This allows them to easily share the document internally and always have access to the copy. + +* Clients like attachments +* They can forward it to whoever they want +* There is a paper trail of changes and feedback that they can share internally on their end ::: bad ![Figure: Bad example – Added the file as a link. This requires maintenance as we would need to add them as guests to Teams or would have to make the file an anonymous link](email-bad-example.png) ::: ::: good -![Figure: Good example – Added the file as an attachment](email-external-good-example.png) +![Figure: Good example – Added external file as an attachment](email-external-good-example.png) ::: -#### Benefits - -✅ Clients like attachments - -✅ They can forward it to whoever they want -✅ There is a paper trail of changes and feedback that they can share internally on their end.