Quickstart

This guide takes a workspace administrator from zero to one visible Angada result: a pull request that shows an Angada check on GitHub and a living card in Slack.

GitHubPull request activity

AngadaReview and coordination

SlackLiving pull-request card

Connect GitHub, connect Slack, route a repo, open a PR, watch the card post.

Prerequisites

• You're a workspace administrator in Angada (the person who creates the Workspace is its first admin).
• Admin access to the GitHub organization or account you want to connect.
• Permission to install apps on that GitHub organization, and to approve OAuth requests in your Slack workspace.
• AI Review availability depends on your Workspace's plan.

1. Create or open your Workspace

Sign in to Angada and create a Workspace. A Workspace is tied to exactly one GitHub account and one Slack workspace — pick the pair your team works in. If you're added to several Workspaces later, switch between them from the workspace switcher; each keeps its own repos, Reports, and settings.

2. Connect GitHub

1. On the Connect your code step of onboarding, select Connect GitHub.
2. You're taken to GitHub's own installation screen. Choose All repositories or Only select repositories, then pick which ones.
3. Approve the install. You're returned to Angada, where the step now shows GitHub connected.

The repos you granted are now Angada's connected repos — that set mirrors the App's install, so adding a repo later means changing access on GitHub's side. See GitHub integration for what Angada reads and writes.

3. Connect Slack

1. On the Bring in Slack step, select Add to Slack.
2. Approve the request on Slack's standard OAuth consent screen.
3. You're returned to Angada, where the step now shows Slack workspace linked with your Slack team's name.
4. Choose a default channel — the destination for every connected repo that doesn't have its own route. You can route repos to specific channels later.

See Slack integration for details and recovery steps.

4. Confirm the first workflow

Open Settings → Review and confirm the default review policy works for the first test: draft pull requests are skipped by default, and findings at or above the severity floor publish to the pull request. You can tune this later in Review settings.

5. Open a pull request

Open a new pull request in one of your connected repos — or push a new commit to an existing one. Draft PRs are skipped by default; open a normal PR or mark a draft ready for review.

6. Confirm the result

Two things should now exist:

• On GitHub — an Angada check run on the PR. Depending on your plan and settings, it resolves into a review with findings posted on the PR.
• In Slack — a living card for the PR in your default channel: one message, updated in place as the PR moves through review.

Open the Angada dashboard to see the same PR in your triage feed, grouped by what needs attention.

If something didn't happen

• No check run on the PR — confirm the repo is in the GitHub App's repository access, then wait out the 90-second push debounce window before expecting a review to start.
• No card in Slack — check the repo's routing, and confirm the default channel is set. See Slack integration to re-test the connection.
• Mentions show as plain text — link GitHub logins to Slack users in Identity links.

Next steps

• AI Review — understand the check, verdict, and findings on the pull request.
• AI Wiki — generate a source-cited guide to a connected repository.
• Notifications — route living cards and scheduled summaries to the team.