diff --git a/10/umbraco-deploy/getting-started/deploy-settings.md b/10/umbraco-deploy/getting-started/deploy-settings.md
index fcc967c03d2..ed92b8f7919 100644
--- a/10/umbraco-deploy/getting-started/deploy-settings.md
+++ b/10/umbraco-deploy/getting-started/deploy-settings.md
@@ -36,7 +36,7 @@ For illustration purposes, the following structure represents the full set of op
     "Deploy": {
         "Settings": {
             "ApiKey": "<your API key here>",
-            "Edition": "Default",            
+            "Edition": "Default",
             "ExcludedEntityTypes": [],
             "RelationTypes" : [],
             "ValueConnectors": [],
@@ -52,7 +52,7 @@ For illustration purposes, the following structure represents the full set of op
             "IgnoreBrokenDependenciesBehavior": "Restore",
             "AcceptInvalidCertificates": false,
             "TransferFormsAsContent": true,
-            "TransferDictionaryAsContent": false,            
+            "TransferDictionaryAsContent": false,
             "SetEmptyDictionaryItemsOnTransfer": true,
             "IgnoreMissingLanguagesForDictionaryItems": false,
             "AllowMembersDeploymentOperations": "None",
diff --git a/12/umbraco-deploy/getting-started/deploy-settings.md b/12/umbraco-deploy/getting-started/deploy-settings.md
index 64807c89aef..7f2f5ac026b 100644
--- a/12/umbraco-deploy/getting-started/deploy-settings.md
+++ b/12/umbraco-deploy/getting-started/deploy-settings.md
@@ -36,7 +36,7 @@ For illustration purposes, the following structure represents the full set of op
         "Settings": {
             "ApiKey": "<your API key here>",
             "ApiSecret": "<your API secret here>",
-            "Edition": "Default",            
+            "Edition": "Default",
             "ExcludedEntityTypes": [],
             "RelationTypes" : [],
             "ValueConnectors": [],
diff --git a/13/umbraco-deploy/getting-started/deploy-settings.md b/13/umbraco-deploy/getting-started/deploy-settings.md
index 97b02de3a01..a0acc2f030d 100644
--- a/13/umbraco-deploy/getting-started/deploy-settings.md
+++ b/13/umbraco-deploy/getting-started/deploy-settings.md
@@ -68,6 +68,7 @@ For illustration purposes, the following structure represents the full set of op
             "NumberOfSignaturesToUseAllRelationCache": 100,
             "ContinueOnMediaFilePathTooLongException": false,
             "SuppressCacheRefresherNotifications": false,
+            "ResolveUserInTargetEnvironment": false,
             "Suspensions": {
               "DiskRead": "All",
               "PartialRestore": "All",
@@ -380,6 +381,14 @@ In production this setting shouldn't be changed from it's default value of `fals
 
 If attempting a one-off, large transfer operation, before a site is live, you could set this value to `true`. That would omit the firing and handling of these notifications and remove their performance overhead. Following which you would need to ensure to rebuild the cache and search index manually via the backoffice _Settings_ dashboards.
 
+## ResolveUserInTargetEnvironment
+
+With this setting assigned a value of `true`, Umbraco Deploy will attempt to resolve users when transfers are made to new environments.
+
+Users and user groups are maintained separately in different environments, so it isn't always the case that an editor has accounts across all environments. When an account exists matching by email address, Deploy will associate the changes made in upstream environments with the user that initiated the transfer. Allowing the expected information about save and publish operations to be available in the audit log of the environment where the data was transferred.
+
+When the setting is set to `false`, or a matching account isn't found, the audit records will be associated with the super-user administrator account.
+
 ### Suspensions
 
 Deploy operations suspend scheduled publishing, Examine indexing, document cache and/or signature database update events by default. You can amend this behavior for all supported or specific operations using these settings.