Skip to content

Commit 6eb6e3a

Browse files
committed
🔧 chore: recommend using service accounts when installing integrations that user personal tokens
1 parent 0947ab4 commit 6eb6e3a

File tree

2 files changed

+24
-0
lines changed

2 files changed

+24
-0
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, all activities such as comments, work item creation, and commit associations 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: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,18 @@ Sentry owner, manager, or admin permissions and GitLab owner or maintainer permi
1212

1313
</Alert>
1414

15+
<Alert title="Note">
16+
<p>
17+
We recommend using a dedicated service account when installing this integration rather than a personal user account.
18+
</p>
19+
<p>
20+
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.
21+
</p>
22+
<p>
23+
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.
24+
</p>
25+
</Alert>
26+
1527
1. Navigate to **Settings > Integrations > GitLab**.
1628

1729
![Install GitLab integration](./img/gitlab-overview.png)

0 commit comments

Comments
 (0)