diff --git a/Form-Design-Guidelines.md b/Form-Design-Guidelines.md
index b74a893..878a2b7 100644
--- a/Form-Design-Guidelines.md
+++ b/Form-Design-Guidelines.md
@@ -42,4 +42,8 @@ Make field and section labels and titles as self explanatory as possible. Descri
 
 ### 11. Positioning of "Enabled" or "Disable"
 
-If the form has an "Enabled" or "Disabled" field, it must be in the last field in the first column of the first section. When the form is disabled, all fields other than the enable/disable field should be read-only.
\ No newline at end of file
+If the form has an "Enabled" or "Disabled" field, it must be in the last field in the first column of the first section. When the form is disabled, all fields other than the enable/disable field should be read-only.
+
+### 12. Logs related to a transaction / sync / integration must be linked in the "Settings"
+
+If there are any logs related to background activities related to an integration or transaction, they must linked from the parent transaction or the configuration object. (Example: General Ledger Entries for an invoices are linked form the Invoice, or Email Queue linked from Email Account).
\ No newline at end of file