Skip to content

Commit ea764fe

Browse files
iamrajjoshibitsandfoxes
authored andcommitted
🔧 chore(integrations): recommend using service accounts when installing integrations that use personal tokens (#13912)
1 parent b304798 commit ea764fe

File tree

2 files changed

+23
-1
lines changed

2 files changed

+23
-1
lines changed

docs/organization/integrations/source-code-mgmt/azure-devops/index.mdx

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,18 @@ Azure DevOps was formerly known as Visual Studio Team Services (VSTS).
88

99
## Install
1010

11+
<Alert title="Note">
12+
<p>
13+
We recommend using a dedicated service account when installing this integration rather than a personal user account.
14+
</p>
15+
<p>
16+
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.
17+
</p>
18+
<p>
19+
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.
20+
</p>
21+
</Alert>
22+
1123
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.
1224

1325
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".

docs/organization/integrations/source-code-mgmt/gitlab/index.mdx

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,18 @@ description: "Learn more about Sentry’s GitLab integration and how it helps yo
88

99
<Alert>
1010

11+
<p>
1112
Sentry owner, manager, or admin permissions and GitLab owner or maintainer permissions are required to install this integration.
12-
13+
</p>
14+
<p>
15+
We recommend using a dedicated service account when installing this integration rather than a personal user account.
16+
</p>
17+
<p>
18+
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.
19+
</p>
20+
<p>
21+
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.
22+
</p>
1323
</Alert>
1424

1525
1. Navigate to **Settings > Integrations > GitLab**.

0 commit comments

Comments
 (0)