Azure Devops - Cloud (recommended)
Integrate Azure DevOps with a Personal Access Token
Last updated
Integrate Azure DevOps with a Personal Access Token
To connect Azure DevOps to Hivel using a Personal Access Token (PAT), follow these steps:
Data Access by Hivel
Hivel accesses the past 30-90 days of commits and pull requests from active repositories during the initial sync.
Authorization Mechanism
Hivel gets access using a Personal Access Token, which can be created using this open the API tokens page.
Users maintain full control and can withdraw access anytime by revoking the Personal Access Token.
Requirements
Ensure to create the Personal Access Token from an account that has "Project Administrator" permissions for all relevant projects and repositories.
Best Practice
Opt for a service account rather than an individual-linked account.
Service accounts are typically overseen by the company's admin.
Log into the Azure DevOps service account:
Use a dedicated service account that has "Project Administrator" permissions for the projects and repositories Hivel should analyze.
Avoid using personal accounts to ensure only the intended projects are accessed.
Click on the user settings on the top right corner to the left of the profile icon.

Create a new Personal Access Token in Azure DevOps.

Enter Hivel as the token name.
Ensure 'All accessible organizations' is selected while creating the Personal Access Token.
Set the expiration to the longest period your organization's policy allows. (You can revoke the token manually when the engagement ends.)

Set the scope to Custom Defined.
Please ensure you select all the permissions below -all Read:
Project And Team: Read
User Profile: Read
Code: Read
Work Items: Read
Create the token and copy it immediately, as you won't be able to view it again.
Copy the generated token immediately, as you won't be able to view it again.
Submit the token to Hivel.
Hivel validates the token instantly -if the token is wrong, expired, or revoked, Hivel shows a clear message telling you exactly what the problem is. Generate a new token with the correct permissions and reconnect.
That's it, all done!
Last updated