Connections & routing
Which repos Angada can see, and which Slack channel each one reports to.
Connected repositories
The repos Angada can see mirror your GitHub App installation — nothing is curated inside Angada itself. If you gave the App access to a repo, it shows up as connected; if you didn't, it won't appear no matter what you do in Angada's settings.
To add or remove a repo, change the GitHub App's repository access from GitHub's side (your installation settings), then let Angada re-sync. See Why don't I see a repo in Angada? if a repo you expect isn't showing up.
Routing a repo to a channel
By default, a connected repo's activity goes to your Workspace's default channel. You can instead route a specific repo to its own Slack channel — useful when a repo belongs to one squad and you don't want its notifications mixed in with everyone else's.
A single repo can be routed to more than one channel; each routed channel gets its own copy of that repo's live PR cards and digests. See Route a repo to a channel for the steps.
The default channel
Any connected repo without an explicit route falls back to the Workspace's default channel. This is what lets a new connection start posting notifications immediately, with zero routing setup — you only need to route a repo if you want it somewhere other than the default.
See The mental model for how Connections fit with Reports and the PR lifecycle.