Assign seats

Assign seats to developers whose changes should receive automatic reviews. Seats are not billed per person.

Seats lists Jordan, who has no seat and two pull requests that were not reviewed, above Alex and Sam, who have seats, with each person's credits this month and the View pull requests action.
Seats and this month's usage are managed together. Fictional demo workspace.

Find the developer#

Open Settings → People → Seats and search the developer list. Developers appear after their pull requests reach Proofline.

When recent pull requests were not reviewed because their author has no seat, Seats says how many and lists those authors first. Each author's row links to their pull requests that were not reviewed, and View pull requests opens all of them. To return to the saved order, choose Seated first under Order.

Bot accounts, such as a coding agent's, are listed after people and marked Bot account. Assign a bot a seat only to review its pull requests. Setup's developer question leaves bots out.

If someone is missing, confirm that the GitHub app can access their repository and that their pull request appears in Proofline.

Assign a seat#

  1. On Seats, find the developer.
  2. Select their Seat checkbox, or clear it to remove the seat.
  3. Read the count above Save seats. It shows how many developers will be selected for review.
  4. Select Save seats.

A removed seat stops automatic reviews of that person's pull requests when you save.

Credits this month shows the credits that the person's reviews spent this month. Hover over or focus the amount to see each funding source, including organization credits and plan credits recorded before per-person plans ended.

Own-key equivalent appears when someone's reviews ran on your organization's own provider key. Your provider bills those reviews, so they spend no Proofline credits; the column shows what they would have cost in credits.

Assign seats automatically#

Select Automatically assign seats to pull request authors, then select Save seats. Bots and people whose seat you removed are excluded.

Separate review eligibility from access#

Use seats to choose whose pull requests receive automatic reviews. To change what a person can view or edit, check their roles and GitHub repository access instead. You need the seat permission to change assignments.

If a pull request was not reviewed, inspect its recorded reason before changing the seat. See Find out why a pull request was not reviewed. When that list shows pull requests whose author has no seat, a repository's seat action, such as Assign 2 seats, opens Seats with its unseated authors already selected. Select Save seats to assign them.

Seat assignment and recovery#

Search help

Tab to a result. Enter to open. Escape to close.