From 6eb6e3a8a3607c3dd8a8c55e4cde095ccba5fbd4 Mon Sep 17 00:00:00 2001 From: Raj Joshi Date: Tue, 3 Jun 2025 11:54:57 -0700 Subject: [PATCH 1/2] :wrench: chore: recommend using service accounts when installing integrations that user personal tokens --- .../source-code-mgmt/azure-devops/index.mdx | 12 ++++++++++++ .../integrations/source-code-mgmt/gitlab/index.mdx | 12 ++++++++++++ 2 files changed, 24 insertions(+) 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 e7a682c25ef8e7..d9acc8983dc775 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 + +

+ We recommend using a dedicated service account when installing this integration rather than a personal user account. +

+

+ Since the integration uses personal access tokens for authentication, all activities such as comments, work item creation, and commit associations will be attributed to the user who installed the integration. +

+

+ 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. +

+ + 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 c5ce8ef7ec7286..2d92f1bce031cd 100644 --- a/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx +++ b/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx @@ -12,6 +12,18 @@ Sentry owner, manager, or admin permissions and GitLab owner or maintainer permi + +

+ We recommend using a dedicated service account when installing this integration rather than a personal user account. +

+

+ Since the integration uses personal access tokens for authentication, all activities such as comments, work item creation, and commit associations will be attributed to the user who installed the integration. +

+

+ 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. +

+ + 1. Navigate to **Settings > Integrations > GitLab**. ![Install GitLab integration](./img/gitlab-overview.png) From 1681995d0e1264daccc9e990f4328c93e04d6e78 Mon Sep 17 00:00:00 2001 From: Raj Joshi Date: Tue, 3 Jun 2025 13:37:34 -0700 Subject: [PATCH 2/2] :bug: fix: pr feedback --- .../integrations/source-code-mgmt/azure-devops/index.mdx | 2 +- .../integrations/source-code-mgmt/gitlab/index.mdx | 8 +++----- 2 files changed, 4 insertions(+), 6 deletions(-) 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 d9acc8983dc775..1443434d6865fb 100644 --- a/docs/organization/integrations/source-code-mgmt/azure-devops/index.mdx +++ b/docs/organization/integrations/source-code-mgmt/azure-devops/index.mdx @@ -13,7 +13,7 @@ Azure DevOps was formerly known as Visual Studio Team Services (VSTS). We recommend using a dedicated service account when installing this integration rather than a personal user account.

- Since the integration uses personal access tokens for authentication, all activities such as comments, work item creation, and commit associations will be attributed to the user who installed the integration. + 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.

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. diff --git a/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx b/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx index 2d92f1bce031cd..ab20b534747c94 100644 --- a/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx +++ b/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx @@ -8,16 +8,14 @@ description: "Learn more about Sentry’s GitLab integration and how it helps yo +

Sentry owner, manager, or admin permissions and GitLab owner or maintainer permissions are required to install this integration. - - - - +

We recommend using a dedicated service account when installing this integration rather than a personal user account.

- Since the integration uses personal access tokens for authentication, all activities such as comments, work item creation, and commit associations will be attributed to the user who installed the integration. + 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.

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.