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 GitHub account can access, and archived repositories are excluded.
What needs a Review seat
Any member of an eligible organization can open Triage and read the queue without a Review seat. Reading includes every view, filter, grouping, and card signal. Actions that write to your Git provider or spend model capacity require an active Review seat:
Provider-writing actions additionally run as you, using your own GitHub authorization — Triage never acts as a shared bot identity for them. An action you are not permitted to perform in GitHub is refused in Triage too. See Seat assignment for how seats are granted.
For what each individual action needs, see Actions on a pull request.
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.