Connections & integrations
Integrations are the highest-leverage setup you'll do: an admin configures each one once, at the org or enterprise level, and every member benefits in every session afterwards. They matter beyond convenience: engineers spend well under a third of their time actually writing code, and the rest goes to tickets, reviews, and coordination, so integrations are what put Devin where most of the work actually happens. For source control, the critical path is three steps: connect → grant permissions → index. Miss any one and members hit a wall that looks like a Devin problem but is really a setup problem.
Connect. For most teams, the GitHub App is the default path: install it, choose which repositories it can see, done. Self-hosted setups have their own paths: GitHub Enterprise Server for on-prem GitHub, GitLab self-managed for on-prem GitLab, and Azure DevOps via a service principal. Pick the one that matches where your code actually lives; the grant-and-index steps that follow are the same idea everywhere.
Grant. Connecting makes repos visible to Devin; granting decides who gets them. Repository permissions are granted per Devin org by enterprise admins, which is where the org boundaries from Lesson 1 pay off. Grant least-privilege: give each org the specific repo set its team works on, not blanket access to the whole GitHub org. Grants aren't one-way, either; you'll update them as teams pick up new repos and revoke them when ownership moves.
Index. A newly granted repo must be indexed before Devin is any good at it. Indexing is what builds DeepWiki and the codebase understanding behind Ask Devin; until it finishes, they don't work for that repo at all. Watch indexing status after every grant, and if you're onboarding a large fleet of repos, use the bulk-index API instead of clicking through them one at a time.
Beyond source control, wire up where work already happens. Slack and Microsoft Teams let anyone in a channel start a session by mentioning @Devin. Jira and Linear link tickets to sessions, so a well-written ticket becomes a well-briefed session. And for everything else, the MCP marketplace connects Devin to your other internal tools.
The test of a good integration setup is that members never think about it: they mention Devin in Slack, point at a ticket, and Devin already knows the repo. Getting to that point is connect, grant, index, in that order, for every org.