Skip to content

Commit ca630cf

Browse files
committed
minor updates
1 parent f07dcb8 commit ca630cf

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

docs/deployment/managed-scanning/bitbucket.md

+8
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ Semgrep Managed Scanning requires one of the following plans:
2424
- Bitbucket Cloud Premium
2525
- Bitbucket Data Center
2626

27+
### Bitbucket Cloud
28+
2729
You must provide a Bitbucket [workspace access token](https://support.atlassian.com/bitbucket-cloud/docs/workspace-access-tokens/) to Semgrep, which can be created by a user with the `Product Admin` role. Once you have Managed Scanning fully configured, you can update the token provided to Semgrep to one that's more restrictive. The scopes you must assign to the token include:
2830

2931
- `webhook (read and write)`
@@ -34,6 +36,12 @@ You must provide a Bitbucket [workspace access token](https://support.atlassian.
3436

3537
See [Pre-deployment checklist > Permissions](/deployment/checklist#permissions) for more information about the permissions used by Semgrep.
3638

39+
### Bitbucket Data Center
40+
41+
You must provide a Bitbucket [HTTP access token](https://confluence.atlassian.com/bitbucketserver/http-access-tokens-939515499.html) to Semgrep, which can be created by a user with the `Product Admin` role. This access token must be created with with `PROJECT_ADMIN` permissions.
42+
43+
See [Pre-deployment checklist > Permissions](/deployment/checklist#permissions) for more information about the permissions used by Semgrep.
44+
3745
## Enable Managed Scanning and scan your first repository
3846

3947
<!-- vale off -->

0 commit comments

Comments
 (0)