Roles and permissions
Admins versus members, how people get access, and what review seats govern.
The two roles
Anyone who signs in to Angada is a member of your Workspace, with one of two roles:
| Admin | Member | |
|---|---|---|
| View dashboards and Reports | ✓ | ✓ |
| Own notification preferences | ✓ | ✓ |
| Workspace settings | ✓ | |
| Connect/disconnect integrations | ✓ | |
| Configure AI review | ✓ | |
| Invite and manage members | ✓ | |
| Billing | ✓ |
Your Workspace always has at least one admin — the person who connected Slack is the first, and additional admins are promoted from existing members.
Members list with role column and the promote/suspend actions.
How people get access
Two doors into a Workspace:
- GitHub roster — people who belong to the GitHub account your Workspace is tied to can be granted access based on that roster.
- Invitations — an admin invites a person directly; the invite lands in their inbox and grants access when accepted.
Access is not review eligibility
Workspace membership decides who can open Angada. Whether a person's pull requests receive reviews is governed separately by Review Seats. Someone can be a member without occupying a review seat, and vice versa.
Suspending and restoring access
An admin can suspend a member — someone who's left the team, say — which blocks their access without deleting their history. Restoring a suspended member returns their access as it was.