diff --git a/docs/organization/integrations/source-code-mgmt/azure-devops/index.mdx b/docs/organization/integrations/source-code-mgmt/azure-devops/index.mdx
index e7a682c25ef8e..1443434d6865f 100644
--- a/docs/organization/integrations/source-code-mgmt/azure-devops/index.mdx
+++ b/docs/organization/integrations/source-code-mgmt/azure-devops/index.mdx
@@ -8,6 +8,18 @@ Azure DevOps was formerly known as Visual Studio Team Services (VSTS).
 
 ## Install
 
+<Alert title="Note">
+  <p>
+  We recommend using a dedicated service account when installing this integration rather than a personal user account. 
+  </p>
+  <p>
+  Since the integration uses personal access tokens for authentication, activities such as comments and work item creation will be attributed to the user who installed the integration. 
+  </p>
+  <p>
+  Using a service account helps maintain proper access control, prevents disruption when team members leave, and ensures consistent attribution for all features across your organization.
+  </p>
+</Alert>
+
 1. To install this integration, you need to have Sentry organization owner, manager, or admin permissions, as well as Azure organization owner permissions, or be a user in the Project Collections Administrators group.
 
 2. Go to your Azure Org's settings to make sure third-party access via OAuth is enabled - navigate to **Organization Settings > Security > Policies** and enable "Third-party application access via OAuth".
diff --git a/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx b/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx
index c5ce8ef7ec728..ab20b534747c9 100644
--- a/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx
+++ b/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx
@@ -8,8 +8,18 @@ description: "Learn more about Sentry’s GitLab integration and how it helps yo
 
 <Alert>
 
+<p>
 Sentry owner, manager, or admin permissions and GitLab owner or maintainer permissions are required to install this integration.
-
+</p>
+  <p>
+  We recommend using a dedicated service account when installing this integration rather than a personal user account. 
+  </p>
+  <p>
+  Since the integration uses personal access tokens for authentication, activities such as comments and work item creation will be attributed to the user who installed the integration. 
+  </p>
+  <p>
+  Using a service account helps maintain proper access control, prevents disruption when team members leave, and ensures consistent attribution for all features across your organization.
+  </p>
 </Alert>
 
 1. Navigate to **Settings > Integrations > GitLab**.