Context

Customers may notice that some users with a Seat Status of Unassigned will still have pull requests reviewed by CodeRabbit. This may raise questions about how user licensing, onboarding, and pull request coverage work within an organization.

This article explains how unassigned users are handled in CodeRabbit, how onboarding typically occurs, and how CodeRabbit determines whether pull requests in integrated repositories receive reviews by default. This includes scenarios where users may be excluded by configuration or explicitly opt out.

Answer

Unassigned users generally fall into one of two categories.

1. Users who have not yet opened a pull request

When a CodeRabbit account is first set up, members of the connected Git organization who have not yet opened a pull request will have a Seat Status of Unassigned.

If seat allocation is set to Auto-approval, a seat is assigned the first time a user opens a pull request in a repository that has been integrated with CodeRabbit. This approach is commonly recommended during onboarding, as it allows seats to be allocated automatically as usage begins, without requiring manual intervention.

Once an organization is on a paid subscription, seat allocation can be changed to Manual approval, allowing a CodeRabbit Admin to explicitly assign seats as needed.

2. Users who do not have a CodeRabbit seat by design

Some users may be members of the Git organization but intentionally do not have a CodeRabbit seat assigned. In these cases, code review behavior depends on the organization’s Enable Free Tier setting.

• If Enable Free Tier is turned on, Unassigned users receive high-level CodeRabbit summaries only. These summaries are more limited in scope compared to the feedback generated for users with paid seats.

• If Enable Free Tier is turned off, unassigned users do not receive any CodeRabbit feedback or output on their pull requests.