> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coderabbit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Requirements and FAQ

> Who can open Triage, what plan and provider it needs, and which actions require a Review seat.

export const OpenBetaBadge = ({tip = "This feature is currently in open beta. We are actively improving it based on your feedback. If you encounter any issues or have suggestions, please share them on our Discord community or visit the support page.", title = "Open Beta", cta = "Contact support", href = "/support", disabled = false}) => {
  return <Tooltip tip={tip} cta={cta} href={href}>
        <Badge icon="badge-alert" disabled={disabled || undefined}>
            {title}
        </Badge>
    </Tooltip>;
};

export const TeamPlanBadge = ({tip = "This feature is available on Team (formerly Pro+), Advanced, and Enterprise. Please refer to our pricing page for more information about our plans and features.", title = "Team Plan", cta = "Read more", href = "https://coderabbit.ai/pricing", disabled = false}) => {
  return <Tooltip tip={tip} cta={cta} href={href}>
        <Badge icon="shield-plus" disabled={disabled || undefined}>
            {title}
        </Badge>
    </Tooltip>;
};

export const GitLabBadge = ({tip = "This feature is available on GitLab.", title = "GitLab", cta, href, disabled = false}) => {
  return <Tooltip tip={tip} cta={cta} href={href}>
        <Badge icon="gitlab" disabled={disabled || undefined}>
            {title}
        </Badge>
    </Tooltip>;
};

export const GitHubBadge = ({tip = "This feature is available on GitHub and GitHub Enterprise.", title = "GitHub", cta, href, disabled = false}) => {
  return <Tooltip tip={tip} cta={cta} href={href}>
        <Badge icon="github" disabled={disabled || undefined}>
            {title}
        </Badge>
    </Tooltip>;
};

<GitHubBadge title="GitHub Cloud" /> <GitLabBadge title="GitLab" tip="Triage is available on both GitLab Cloud and GitLab Self-Hosted" /> | <TeamPlanBadge /> <OpenBetaBadge title="GitLab beta" tip="Triage is in beta for GitLab." />

## Who can open Triage

| Requirement | Detail |
| - | - |
| Plan | Team or higher. See [Plans](/management/plans). |
| Git provider | GitHub Cloud; GitLab Cloud and self-managed GitLab in beta. Bitbucket is not yet supported. A self-managed GitLab instance can connect to CodeRabbit Cloud; Triage is not available on self-hosted CodeRabbit deployments. |
| Organization | Must be backed by an active CodeRabbit workspace, and you must be a member of it. |
| Review seat | You need an active Review seat to open Triage in the app. See [Seat assignment](/management/seat-assignment). |
| Availability | GitHub Cloud is generally available to eligible organizations. GitLab Cloud and self-managed GitLab are available in beta. |

If Triage does not open for you, the page names the specific requirement you are missing — see [When Triage will not open](/triage/troubleshooting#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](/triage/actions#refresh-a-branch), GitHub team views, GitHub merge queues, and [Triage automation rules](/triage/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:

| Action | Checks for a Review seat when it runs |
| - | - |
| Browse, filter, group, and save views | No |
| Read every signal on a card | No |
| Ignore or reject a close candidate | No |
| Start a CodeRabbit review | Yes |
| Repair a pull request | Yes |
| Refresh a branch | Yes |
| Close a pull request | Yes |
| Request, remove, or re-request a reviewer | Yes |
| Set a manual priority | Yes |

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](/triage/rules#who-can-manage-rules) use the organization's CodeRabbit integration for automated GitHub actions and have separate management permissions. See [Seat assignment](/management/seat-assignment) for how seats are granted.

For what each individual action needs, see [Actions on a pull request](/triage/actions#what-each-action-needs).

## 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](/triage/rules) for templates, conditions, activation, and existing-PR handling.

## What's next

<CardGroup cols={1}>
  <Card title="Triage overview" href="/triage" icon="list-filter" horizontal>
    Start here if you're new to Triage.
  </Card>

  <Card title="Actions on a pull request" href="/triage/actions" icon="square-mouse-pointer" horizontal>
    See what each action does, and which ones need a Review seat.
  </Card>

  <Card title="Troubleshooting Triage" href="/triage/troubleshooting" icon="circle-question-mark" horizontal>
    Work out why an action is disabled, refused, or did not appear to take effect.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.