Skip to content

🔧 chore(integrations): recommend using service accounts when installing integrations that use personal tokens #13912

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 3, 2025
Merged

🔧 chore(integrations): recommend using service accounts when installing integrations that use personal tokens #13912

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6eb6e3a
:wrench: chore: recommend using service accounts when installing inte…
iamrajjoshi Jun 3, 2025
1681995
:bug: fix: pr feedback
iamrajjoshi Jun 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/organization/integrations/source-code-mgmt/azure-devops/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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".
Expand Down
12 changes: 11 additions & 1 deletion docs/organization/integrations/source-code-mgmt/gitlab/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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**.
Expand Down