Who can open Triage
If Triage does not open for you, the page names the specific requirement you are missing â see When Triage will not open to match the message you see.
Triage shows only the repositories you can see. Membership in the CodeRabbit organization is not enough on its own: the queue is scoped to the repositories your signed-in Git provider account can access, and archived repositories are excluded.
Provider-specific behavior
Actions depend on the pull request state and your provider permissions. Refresh branch, GitHub team views, GitHub merge queues, and Triage automation rules remain specific to GitHub Cloud.What needs a Review seat
Opening Triage in the app requires an active Review seat. Membership in an eligible organization is not enough on its own: without a seat, you cannot reach the queue at all. On top of that, actions that write to your Git provider or spend model capacity check for an active Review seat each time they run:
Manual Git-provider actions such as merging, closing, and requesting reviewers run as you, using your own Git-provider authorization. An action you are not permitted to perform in your Git provider is refused in Triage too. Triage automation rules use the organizationâs CodeRabbit integration for automated GitHub actions and have separate management permissions. See Seat assignment for how seats are granted.
For what each individual action needs, see Actions on a pull request.
Who can configure automation
Organization administrators can manage merge, close, and Auto-fix rules. Members can manage Slack-only rules within their repository access. Repository-admin access alone does not authorize GitHub automation. See Triage rules for templates, conditions, activation, and existing-PR handling.Whatâs next
Triage overview
Start here if youâre new to Triage.
Actions on a pull request
See what each action does, and which ones need a Review seat.
Troubleshooting Triage
Work out why an action is disabled, refused, or did not appear to take effect.