> ## Documentation Index > Fetch the complete documentation index at: https://interfere.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Overview > Connect Interfere to where your code lives, where it runs, and where your team talks. Integrations give Interfere the context around your code and a way to reach your team. You connect and manage them from [**Settings → Integrations**](https://interfere.com/~/*/settings/integrations). They fall into three groups: * **Sources** are where your code lives, so Interfere can tie a problem to the change that caused it. * **Destinations** are where your code runs, so Interfere can line a problem up with the release that shipped it. * **Communications** are how Interfere reaches your team and takes direction back. Deploying somewhere without a native integration, like AWS, Fly, Render, or your own servers? Use the [CLI](/integrations/cli) to report releases and upload source maps from your pipeline. Interfere requests the least access each integration needs, and read-only wherever possible. Each page lists the exact permissions and why.