Authenticate GitHub, GitLab, Bitbucket, Azure DevOps, or AWS CodeCommit and configure the webhooks Review needs
Review supports GitHub, GitLab, Bitbucket, Azure DevOps, and AWS CodeCommit. This page covers each provider’s authentication options and the manual webhook step some providers require.
Click Install GitHub App to begin the GitHub App installation.GitHub redirects you to select an organization and grant repository access. After you authorize, the wizard resumes automatically. Webhooks are registered by the GitHub App — no manual webhook configuration is needed.
Installing CloudThinker to a GitHub organization requires Organization Owner permissions. If you are not an owner, ask an owner to install the app.
Click Connect to GitLab to authenticate via OAuth. This is the simplest option for GitLab.com users.After connecting, configure a webhook manually.
Use a Project Access Token or Group Access Token for self-hosted GitLab instances or if you prefer manual token management. Comments then appear from a bot user, tokens stay scoped to specific projects or groups, and access is easy to revoke. CloudThinker supports self-hosted GitLab version 12.0 and above.Connection details:
GitLab URL: Enter https://gitlab.com for GitLab.com, or your self-hosted instance URL (e.g., https://gitlab.example.com)
Token Type: Select Project Access Token (single project) or Group Access Token (all projects in a group)
Access Token: Paste your generated token
How to create a Project Access Token
Go to your project → Settings → Access Tokens
Click Add new token
Set role to Developer or higher
Select scope: api
Set an expiration date (recommended)
Copy the generated token
How to create a Group Access Token
Go to your group → Settings → Access Tokens
Click Add new token
Set role to Developer or higher
Select scope: api
Set an expiration date (recommended)
Copy the generated token
The token must have Developer role or higher to post code review comments. Guest and Reporter roles cannot comment on merge requests.
Click Connect to Bitbucket to authenticate via OAuth. Bitbucket redirects you to authorize workspace access.Webhooks are registered automatically — no manual webhook configuration is needed.
Connect using a Bitbucket access token. Choose the token type that matches your access level:
Token Type
Scope
Plan Required
Workspace Access Token
All repositories in a workspace
Premium
Project Access Token
All repositories in a project
Premium
Repository Access Token
Single repository only
Free
Connection details:
Token Type: Select the token scope from the dropdown
Bitbucket Workspace: Enter your workspace slug (from the URL: bitbucket.org/<workspace>/repo)
Repository Slug (Repository tokens only): Enter the repository slug
Access Token: Paste your generated token
Click Validate Token first to verify access, then click Connect to complete.Required token permissions:
Account: Read
Repositories: Read, Write
Pull requests: Read, Write
Webhooks: Read and write
Pipelines: Read, Write
How to create a Workspace Access Token
Go to Workspace → Settings → Access tokens
Click Create workspace access token
Enable the required permissions listed above
Set an expiration date (recommended)
Copy the generated token
How to create a Project Access Token
Go to Project → Project settings → Access tokens
Click Create project access token
Enable the required permissions listed above
Set an expiration date (recommended)
Copy the generated token
How to create a Repository Access Token
Go to Repository → Repository settings → Access tokens
Click Create Repository Access Token
Enable the required permissions listed above
Set an expiration date (recommended)
Copy the generated token
Webhooks are registered automatically — no manual webhook configuration is needed.
Azure DevOps uses a Personal Access Token (PAT) for authentication.Connection details:
Organization URL: Enter your Azure DevOps organization URL (e.g., https://dev.azure.com/your-org or https://your-org.visualstudio.com)
Project: Enter the project name containing your repositories
Personal Access Token: Paste your generated PAT
Click Validate PAT first to verify access, then click Connect to complete.Required PAT scopes:
Build — Read
Code — Read & Write
Pull Request Threads — Read & Write
How to create a PAT
Go to Azure DevOps → User Settings (top-right) → Personal Access Tokens
Click New Token
Set the organization and expiration date
Select the scopes listed above
Click Create and copy the generated token
PATs expire on the date you set during creation. Rotate your PAT before it expires to avoid disrupting reviews.After connecting, configure webhooks manually.
CloudThinker connects to AWS CodeCommit with an IAM role (recommended) or an IAM access key. The setup wizard generates the exact policies and commands for both options.
IAM role (recommended)
Access key
The wizard provides a trust policy scoped to CloudThinker with a unique external ID, plus the AWS CLI commands to create the role.
Follow the wizard’s guided steps to save the generated trust policy and permissions policy files.
Run the provided aws iam create-role and aws iam put-role-policy commands.
Copy the role ARN and paste it into the connection form.
The permissions policy grants read access to repositories and pull requests, permission to post and update review comments, and permission to manage the CloudThinker-prefixed EventBridge rules used for change notifications.
The wizard provides a script that creates a dedicated IAM user with the same CodeCommit permissions and generates an access key pair.Run the script — or follow the equivalent manual steps shown in the wizard — then paste the access key ID and secret access key into the connection form.
