# DevRev
## DevRev ↔ DevDynamics Integration Guide
**Purpose:**
This document shows how to integrate DevRev with DevDynamics using a Personal Access Token (PAT). It includes clear steps and redacted screenshots suitable for sharing with internal stakeholders and customers.
## **Prerequisites**
• DevRev account (workspace access).
• DevDynamics org admin access.
• Permission to create a DevRev Personal Access Token (PAT).
## **Step-1. Create or Sign in to DevRev**
You can create an account or sign in using Google, LinkedIn, or Email.
\
Figure 1: DevRev sign-up screen with multiple options.
## **Step-2. Open the DevRev Integration in DevDynamics**
In DevDynamics, navigate to Home → Settings → Integrations → DevRev.()
Figure 2: DevDynamics navigation to DevRev integration.
## **Step-3. Generate a DevRev Personal Access Token (PAT)**
In DevRev, go to Settings → Account → Personal access tokens and click New token. Choose a name and validity period, then Generate.
Figure 3: Generate new token.
Figure 4: Copy the Personal Access Token (PAT)
## **Step-4. Connect DevRev in DevDynamics**
Back in DevDynamics → DevRev integration, click Integrate DevRev. In the modal, paste the PAT into the API Token field. For Organization ID, use the org identifier from your DevRev URL: `https://app.devrev.ai/{org-id}/..`.
Figure 5: Connect modal.
## **Step-5. Verify Integration and Sync**
Once connected, DevDynamics will begin pulling data. You should see the integration status marked Active and the list of DevRev repositories/features with toggles for sync.
Screenshot:
Figure 6: Integration status shows Active with repositories listed.
## **Notes & Good Practices**
• Treat the PAT like a password. Store it in a secrets manager and rotate it regularly.
• Use a service account for the integration to avoid personal token ownership.
• Limit the token scope to the minimum required permissions.
• If the status does not turn Active, recheck the PAT, Org ID, and network/firewall settings.
.png?alt=media&token=76145b78-6498-41f1-a87d-3795877ed967)
.png?alt=media&token=51779f7e-951a-49ec-864f-e7179263f5fb)
.png?alt=media&token=5003cd63-cdeb-4c74-932a-60397f32a374)
-redacted_dot_app.png?alt=media&token=f1000a1c-5e77-44ec-bb89-ef2700170ec3)
-redacted_dot_app.png?alt=media&token=99c32af0-37c1-4920-9dd4-ac1f28775dcc)
.png?alt=media&token=8050468a-cf21-46dc-949c-37267fdf3d19)