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

> ## Agent Instructions
> IronBee (ironbee.ai) is an AI QA engineer: it verifies code changes against the running app and keeps the evidence. It is not related to the IronBee open-source web application firewall.
> The console is at https://console.ironbee.ai.
> Install the CLI with `npm install -g @ironbee-ai/cli`, sign in with `ironbee login`, and set up a project with `ironbee install`.
> In GitHub workflows, use the action as `ironbee-ai/ironbee-action@v1` and pass the `IRONBEE_API_KEY` secret as the `ironbee_api_key` input.
> In GitLab pipelines, include the component `gitlab.com/ironbee-ai/ironbee-gitlab/verify@v1`; it reads the `IRONBEE_API_KEY` CI/CD variable by default.
> In Bitbucket Pipelines, run the pipe `docker://ghcr.io/ironbee-ai/ironbee-bitbucket:v1` and pass `IRONBEE_API_KEY: $IRONBEE_API_KEY` and `BITBUCKET_OAUTH_TOKEN: $BITBUCKET_OAUTH_TOKEN` under its `variables:`.
> Console scenarios (https://docs.ironbee.ai/console/scenarios) and CLI saved scenarios (https://docs.ironbee.ai/cli/guides/scenarios) are separate features.
> For plans and prices, link to https://ironbee.ai/pricing; the website is the source of truth for them.

# Pull requests and findings in the console

> Every pull request IronBee reviews, with its review status and open findings, and each pull request's jobs, findings and history.

The console lists the pull requests of your connected repositories with what IronBee's code review said about each one. Open a pull request to read its findings, follow the jobs that ran on it, and see the settings its next review will use. How a review works is covered in [Code review](https://docs.ironbee.ai/code-review/overview.md), and what it posts on GitHub in [Code review on GitHub](https://docs.ironbee.ai/code-review/on-github.md). Where a label on these pages names GitHub, such as **Open on GitHub**, a GitLab or Bitbucket repository's pages name GitLab or Bitbucket.

***

## Find the pull requests

Two lists show the same rows and open the same pull request page.

| List | Where | What it shows |
| - | - | - |
| **Pull requests** | The sidebar's **Code review > Pull requests** | The pull requests of every repository connected to your account, newest opened first. Archived projects aren't included |
| **Code review** tab | A project's first tab | One repository's pull requests, most recently updated first. The project picker in the page header switches to another repository |

Next to a project's **Code review** tab, its [Code wiki](https://docs.ironbee.ai/console/code-wiki.md) tab explains the repository's code.

On [Projects](https://docs.ironbee.ai/console/projects.md), a GitHub, GitLab or Bitbucket project's card links in too:

* Click the project's name or its **Code review** row to open the project's **Code review** tab with the same date window.
* Click a bar of the **Code review** row to open the pull requests reviewed in that slice of the window.

Click a row in either list to open its [pull request page](#the-pull-request-page).

![The Pull requests list with the date filter, the search and filter bar, and rows reading Reviewing, Passed, Changes requested and Retracted with their open findings by severity](https://mintcdn.com/ironbee/yXiHzqPAo_3Hu63x/images/console/code-review/pull-requests-list-light.png?fit=max\&auto=format\&n=yXiHzqPAo_3Hu63x\&q=85\&s=553955c7d9c519fc463b80a444f73697)

![The Pull requests list with the date filter, the search and filter bar, and rows reading Reviewing, Passed, Changes requested and Retracted with their open findings by severity](https://mintcdn.com/ironbee/yXiHzqPAo_3Hu63x/images/console/code-review/pull-requests-list-dark.png?fit=max\&auto=format\&n=yXiHzqPAo_3Hu63x\&q=85\&s=8a50ec7b8395794bb1841613641819f8)

***

## Filter and search

* **The date filter** in the page header shows the pull requests IronBee reviewed in that window: those whose latest review started inside it. Pick **Last 24 Hours**, **Last 7 Days**, **Last 30 Days**, **Last 90 Days**, or a **Custom Range**. A pull request with no review in the window isn't listed; tick [**Needs review**](#pull-requests-that-need-a-review) to see the open ones.
* **Number or title** finds a pull request by its number, with or without `#`, or by words from its title.
* **Repositories** (sidebar list only) and **States** (**Open**, **Merged**, **Closed**) take several values at once. Each option shows how many pull requests it has.
* **Author** and **Base branch** take one value. Pick it from the menu, which shows each one's count, or type a GitHub login or a branch name. **Any author** and **Any branch** clear them.
* **Needs review** shows only the open pull requests IronBee hasn't reviewed. See [Pull requests that need a review](#pull-requests-that-need-a-review).
* **Clear filters** resets them all. The count at the end of the bar says how many pull requests are left, such as **12 of 40 pull requests**.

In the sidebar list, click a repository's name in a row to show only that repository's pull requests.

### Pull requests that need a review

Tick **Needs review** in the filter bar to list only the open pull requests IronBee hasn't reviewed, whatever the dates. The box shows how many there are.

* The date filter is hidden and **States** is disabled, since the list holds open pull requests only.
* A pull request whose first review is running stays listed until the review ends.
* The list reads the newest 100 open pull requests. When there are more, the box's count ends with `+`, such as `12+`, and the count at the end of the bar reads like **12 among the newest 100 open pull requests**.
* On a project's **Code review** tab, for owners and admins, the console first asks GitHub, GitLab or Bitbucket for the repository's open pull requests. One IronBee never heard of, such as a pull request opened before the repository was connected, is listed too.

In this list, the **Open Findings** cell of a pull request with no review holds a **Review** button. Click it to start the review without opening the pull request. Owners, admins and members see it. When the team's credits are used up, it's disabled and says when they reset.

***

## Columns

| Column | What it shows |
| - | - |
| **Pull Request** | The pull request's state icon (open, merged or closed, with a dashed icon for a draft), its number and title. **paused** marks a pull request whose reviews are paused |
| **Repository** | Sidebar list only. The repository the pull request belongs to |
| **Author** | The GitHub login that opened it |
| **Branches** | The head branch and the base branch it merges into |
| **Review** | Where IronBee's review stands, with a detail line under it. See [Review](#review) |
| **Open Findings** | The open findings by severity. See [Open findings](#open-findings) |
| **Opened** | Sidebar list only. When the pull request was opened |
| **Last Review** | **Code review** tab only. When the latest review finished, or `-` while none has |
| **Updated** | When the pull request last changed |

Hover a time in **Opened** or **Updated** to see the full date and time.

You can sort by **Pull Request** (its number), **Opened** and **Updated**. A page shows 25 rows; switch to 50 or 100 under the list.

While a review runs, the list refreshes on its own until it ends.

***

## Review

The **Review** column, and the band on the pull request page, show one of these words with a detail line under it:

| Review | Detail line | Meaning |
| - | - | - |
| **Reviewing** | **started 2m ago** | A review is running |
| **Changes requested** | **on a1b2c3d** | IronBee's check on GitHub is blocking: an open finding reaches the repository's merge block severity |
| **Passed** | **on a1b2c3d** | IronBee's check passed: no open finding reaches the merge block severity |
| **Could not complete** | **the review could not finish** | The review failed or gave up, and the check says so |
| **Cancelled** | **the review was stopped** | The review was cancelled before it finished |
| **Retracted** | **taken back** | IronBee took back everything it had posted on the pull request |
| **Reviewed** | **no check written** | IronBee published a review but wrote no check |
| **Not reviewed** | The reason | No review was published. The reasons are below |

For **Changes requested** and **Passed**, the detail line names the commit the check is on. It adds **an earlier commit**, as in **on a1b2c3d, an earlier commit**, when that isn't the commit IronBee last reviewed. The merge block severity is the **Block merging when** setting; see [Code review settings](https://docs.ironbee.ai/code-review/settings.md).

**Not reviewed** gives the first reason that applies:

| Detail line | Why |
| - | - |
| **a draft** | The pull request is a draft. Whether drafts are reviewed is the **Draft pull requests** setting |
| **a bot's pull request** | A bot opened it. Whether bots' pull requests are reviewed is the **Pull requests opened by bots** setting |
| **reviews paused** | Someone paused IronBee's reviews on this pull request from GitHub. See [Code review on GitHub](https://docs.ironbee.ai/code-review/on-github.md) |
| **no review yet** | IronBee hasn't published a review of this pull request |

***

## Open findings

The **Open Findings** column shows four counts, always in this order: critical, high, medium and low. A zero is drawn hollow. Hover a count to read it, such as **2 High open** or **no Medium finding open**.

Before IronBee has published a review, the column shows `-`, or **after the review** while the first one runs. With **Needs review** ticked, an open pull request with no review shows a **Review** button there instead; see [Pull requests that need a review](#pull-requests-that-need-a-review).

***

## Empty lists

| The list says | When |
| - | - |
| **No pull requests yet** | The repository, or the account, has no pull requests yet. They appear as the repository's host tells IronBee about them |
| **No reviews in this window** | There are pull requests, but IronBee reviewed none of them in the selected dates. Pick a longer window |
| **Nothing needs a review** | **Needs review** is ticked, and every open pull request has a review. "An open pull request IronBee has not reviewed appears here." |
| **Nothing matches** | The filters leave no pull request. **Clear filters** resets them |
| **No repository connected** | Sidebar list: "Code review runs on repositories connected through the GitHub App, a GitLab group or a Bitbucket workspace." **Integrations** opens the integrations page |
| **Code review runs on GitHub, GitLab and Bitbucket repositories** | **Code review** tab of a Vercel, Netlify or CLI project: "This project is not one. Pick a repository above." **Open integrations** leads to setting one up |

***

## The pull request page

The page's title is the pull request's number and title. The line under it gives:

* the state (**Open**, **Merged**, **Closed**, or **draft**)
* the author
* the head and base branches
* when it was opened, or merged
* when it was last updated
* **paused**, when reviews are paused on it
* **Open on GitHub**

If GitHub hasn't sent the pull request's details yet, the line says **GitHub has not described this pull request yet**.

The breadcrumbs lead back to the list you came from: **Pull requests** and the repository from the sidebar list, or **Projects**, the project and **Code review** from a project's tab. **Review now** sits on the right of the header; see [Review now](#review-now).

While a job runs on the pull request, the page refreshes on its own until it ends.

***

## The status band

The band under the header sums up what IronBee says of the pull request, from left to right:

1. **The review**: the same word and detail line as the list's **Review** column. The commit links to the repository's host.
2. **What's open**: the open findings by severity, such as **1 Critical · 2 High open**, or **nothing open**. Then **3 addressed** and **2 listed below the comment threshold** when there are any. These counts match the findings list under the band.
3. **The check**: **IronBee's check on a1b2c3d, the head**, or **an earlier commit** when the check isn't on the latest commit IronBee reviewed, or **no check on GitHub** (**no check on Bitbucket** on Bitbucket). After it comes the merge block in effect: **blocks a merge while medium or worse is open**, **blocks a merge while high or worse is open**, or **never blocks a merge**.

   On GitLab, the band reads **IronBee's result on a1b2c3d, the head** instead, because a project may carry no status of IronBee's. With **Block merges** off, the merge part reads "writes no new status that holds a merge; an earlier red one clears at the next review, a reply under a finding, a resolved thread or a push". With **Block merges** on and **Block merging when** on **Never**, it reads "a review's result never blocks a merge; where pipelines must succeed, a running one holds it". See [Merges](https://docs.ironbee.ai/code-review/on-gitlab.md#merges).
4. **The reviews**: how many reviews IronBee published and when the last one finished, such as **3 reviews · the last finished 2h ago**, or **no published review**.

![A pull request page header with Review now and Open on GitHub, above the status band reading Changes requested, 1 High and 2 Medium open, the check sentence and 3 reviews](https://mintcdn.com/ironbee/yXiHzqPAo_3Hu63x/images/console/code-review/pull-request-band-light.png?fit=max\&auto=format\&n=yXiHzqPAo_3Hu63x\&q=85\&s=2efbb2e16afa47465854477ca21f7284)

![A pull request page header with Review now and Open on GitHub, above the status band reading Changes requested, 1 High and 2 Medium open, the check sentence and 3 reviews](https://mintcdn.com/ironbee/yXiHzqPAo_3Hu63x/images/console/code-review/pull-request-band-dark.png?fit=max\&auto=format\&n=yXiHzqPAo_3Hu63x\&q=85\&s=010214d0d1afa6aa1768b7d5040f1667)

***

## The summary

Under the status band, the **Summary** card shows the [pull request summary](https://docs.ironbee.ai/code-review/on-github.md#the-pull-request-summary) IronBee wrote for the approver. The console reads it from the host: IronBee's section of the description on GitHub, IronBee's summary note on GitLab, or IronBee's summary comment on Bitbucket.

* **Folded:** the card shows the summary's first paragraph. Click the **Summary** heading or **Show more** to open the rest, and **Show less** to fold it again.
* **The header:** the commit the summary describes, such as **of a1b2c3d**, which links to it, and **Open on GitHub**. When someone edited the summary on the host after IronBee wrote it, the header adds **changed on GitHub since IronBee wrote it**.
* **What it draws:** the summary's text, tables and Mermaid diagrams, with its folded parts closed. Images aren't drawn.

The card appears once IronBee has published a review of the pull request. A pull request with no summary, such as one reviewed with **Pull request summary** off, has no card. If the host can't be read, the card says **Couldn't read the summary from GitHub.** and offers **Try again**.

***

## Jobs and settings in effect

The rail on the left of the page has two parts. In a narrow window, it moves under the findings.

### Jobs on this pull request

Every job IronBee ran on the pull request, newest first. When there are more than the rail shows, the last line says how many older ones are left out, such as **4 older not shown**. With no job yet, the rail says **No job has run on this pull request.**

Each job shows its kind, its status, and a line with what started it, what came of it, its [credits](https://docs.ironbee.ai/console/pricing.md) (what it used, what it's expected to use while it runs, or **free**), how long it ran and when it was created. Hover the line to see the date and time.

| Kind | What started it, as the line says |
| - | - |
| **Review** | **asked · from the console** or **asked · through the API** for a review someone asked for, with **full** for a full review. **push a1b2c3d** for a review a push started, or **on a1b2c3d** |
| **Reply** | **a reply in a thread**, or **a review asked for in a thread** when the reply asked for a review |
| **Answer** | **a question in a thread** |
| **Recheck** | **a thread resolved** |
| **Reactions** | **learning from reactions** |
| **Retract** | **taking the review back** |

What came of a job reads **4 comments** or **2 answers**, the reviewer's own word for the run, or why it failed. A cancelled job adds nothing there.

The status is one of **queued**, **starting**, **running**, **publishing**, **succeeded**, **failed** or **cancelled**. A job that hasn't ended has a **Cancel** link; see [Cancel a job](#cancel-a-job).

### In effect for the next review

The settings the next review of this pull request will use:

| Line | Shows |
| - | - |
| **Depth** | **Auto**, **Quick**, **Standard** or **Deep** |
| **Focus** | **Bugs and logic**, which is always on, and the focus areas turned on: **Security**, **Docs, names and tests** |
| **Comments** | Which findings get a comment of their own: **Every severity**, **Medium and above** or **High and above** |
| **Merge block** | **Medium or worse open**, **High or worse open** or **Never**. On a GitLab repository with **Block merges** off, it reads **Never** |

A value the repository sets for itself, rather than taking the account's, is marked **set here**. When code review is off for the repository, the section says **Code review is off for this repository**. **Settings** opens the repository's code review settings; see [Code review settings](https://docs.ironbee.ai/code-review/settings.md).

***

## Review now

**Review now** asks IronBee to review the pull request again. It opens a menu with two choices:

| Choice | What it does |
| - | - |
| **Review what changed** | Reviews what changed since the last review, as a push would |
| **Full review** | Reads every file of the pull request again |

A review you ask for runs even when reviews are paused on the pull request. It spends the account's credits; see [Pricing](https://docs.ironbee.ai/console/pricing.md).

After you pick one, a message confirms what happened:

* **Review queued**: **IronBee reads the pull request and posts what it finds on GitHub.** The job appears at the top of the rail as **Review** with **asked · from the console**, and the band and the list's **Review** column read **Reviewing**.
* **A review is already queued**: the review already waiting covers your ask, and nothing more was queued.
* **A review is already running**: ask again once it has ended.

If the review can't start, **Couldn't start the review** says why: code review is off for the repository, the team's credits are used up, or too many reviews were started in a minute.

The button is disabled, with the reason on hover, when:

* the project is archived: **The project is archived**
* code review is off: **Code review is off for this repository**
* the team's credits are used up, with the date they reset
* a job is already running: **A job is already running on this pull request**

Owners, admins and members see **Review now**. Billing admins don't.

![The open Review now menu with Review what changed and Full review](https://mintcdn.com/ironbee/yXiHzqPAo_3Hu63x/images/console/code-review/review-now-menu-light.png?fit=max\&auto=format\&n=yXiHzqPAo_3Hu63x\&q=85\&s=92532026ed047ac421429b04132a359a)

![The open Review now menu with Review what changed and Full review](https://mintcdn.com/ironbee/yXiHzqPAo_3Hu63x/images/console/code-review/review-now-menu-dark.png?fit=max\&auto=format\&n=yXiHzqPAo_3Hu63x\&q=85\&s=46e9bcadae2b757403f50f4be87c536a)

***

## Cancel a job

A job that hasn't ended has a **Cancel** link in the rail. Click it to stop the job:

* **Cancel requested**: **The job stops at its next step.** Its status then reads **cancelled**.
* **The job had already ended**: it finished before the cancel reached it.

A job that is publishing its result can't be cancelled. Its link is disabled with **Not while publishing**, and the job ends when the delivery does.

Owners, admins and members see **Cancel**. Billing admins don't.

***

## Findings

The findings list on the right holds every finding of the pull request, grouped by what became of it. A group shows the number of findings in it and what it means:

| Group | It says | What's in it |
| - | - | - |
| **Withdrawn** | **taken back by IronBee** | Findings IronBee withdrew |
| **Addressed** | **fixed since; the threads resolved** | Findings the code has fixed since |
| **No longer applies** | **the code changed or went away** | Findings whose code changed or was removed |
| **Turned down** | **turned down by a person: a thumbs-down, a rejecting reply, a hidden comment or a resolved thread** | Findings a person turned down on the pull request. They no longer count as open. See [Replies, reactions and resolved threads](https://docs.ironbee.ai/code-review/on-github.md#replies-reactions-and-resolved-threads) |
| **Open** | **open, or standing after a reply** | Findings still open, including those IronBee kept after a reply on the thread |
| **Listed below the comment threshold** | **in the review body only; never block a merge** | Findings below the **Comment on findings of** setting, and low findings that read as a minor remark. They are listed in the review body, have no comment of their own, and never hold a merge |

The groups come in that order, and a group with nothing in it is left out. **Open** always shows, so an empty one says so. Each group's heading is a button that folds or opens its rows. **Listed below the comment threshold** starts folded and the other groups start open. A group that holds the finding open in the dialog stays open. Inside a group, the findings that changed most recently come first, then the rest by severity, worst first, and by file and line. A long group shows 20 findings at first. The buttons under it, such as **Show 20 more** and **Show all 45**, show the rest, and a count such as **20 of 45 shown** says how many you see.

![The rail with the jobs on the pull request and the settings in effect for the next review, beside the findings grouped as Addressed, No longer applies, Open and Listed below the comment threshold](https://mintcdn.com/ironbee/yXiHzqPAo_3Hu63x/images/console/code-review/pull-request-findings-light.png?fit=max\&auto=format\&n=yXiHzqPAo_3Hu63x\&q=85\&s=8e92a65b0611e8efaa9757b414af4285)

![The rail with the jobs on the pull request and the settings in effect for the next review, beside the findings grouped as Addressed, No longer applies, Open and Listed below the comment threshold](https://mintcdn.com/ironbee/yXiHzqPAo_3Hu63x/images/console/code-review/pull-request-findings-dark.png?fit=max\&auto=format\&n=yXiHzqPAo_3Hu63x\&q=85\&s=43a56afc78424c8508026cc0b40d9726)

### A finding's row

Each row shows:

* **The severity**: **Critical**, **High**, **Medium** or **Low**. If a later job rated the finding again, the row shows the new severity.
* **The category**: **Correctness**, **Security**, or **Docs, names and tests**, which has an info mark that explains it.
* **The file and line**, where the finding stands now.
* **The claim**: what IronBee says is wrong.
* **The state**: **open**, **stands**, **addressed**, **changed**, **gone**, **withdrawn** or **turned down**, with when it last changed. An addressed row is dimmed, with a check mark before **addressed**.

Click a row to open it in the [finding dialog](#the-finding-dialog).

### Filter the findings

* **Search claims, paths and rules** matches the claim, the file path, and the rules, memories and skills the finding cites.
* **Filter** opens a panel that narrows the list by **Severity**, **Category** and **State**, each option with its count, and to findings that **Cites a rule or memory**. **State** offers the row states and **listed below the threshold**.
* The count beside the button reads like **8 of 14 findings**. Each filter in force shows as a chip you can remove, and **Clear all** removes them all.

The filters and the open finding are kept in the page's address, so a copied link opens the same view.

With no findings, the list says **No findings on this pull request**: IronBee hasn't published a review, or it had nothing to say. When the filters hide every finding, it says **No finding matches these filters**.

***

## The finding dialog

The dialog shows one finding in full. Its first line gives the severity, the category, the state, and the file and line **at** the reviewed commit. **Open thread on GitHub** opens the finding's comment thread. Under it, the claim is the dialog's title.

The sections follow in this order. A section with nothing to show is left out.

1. **Happens when** and **Then**: what triggers the problem, and what happens next.
2. The diff: the part of the pull request's diff that holds the finding, with its lines marked. The header gives the file, how it changed, its added and removed lines, and **in this pull request's diff**. Click the header to fold it. When the diff can't be shown, a note says why, followed by the lines IronBee quoted:
   * **The file is not in the pull request's diff any more.**
   * **GitHub gives no diff for this file (binary, or too large).**
   * **The pull request changes more files than the console reads from GitHub.**
   * **The quoted lines are not in the diff any more.**
3. **Suggested fix**: the fix from the finding's comment, as a diff, with the lines it replaces, such as **replaces lines 12–14**. Its caption reads **Applied from the thread on GitHub with one click**. A note from the reviewer may follow. If the comment can't be read, the dialog says **The comment could not be read from GitHub.** or **The comment is no longer on GitHub.**
4. **How it happens**: a diagram of the order, state or path behind the finding. Folded until you open it.
5. **Where this rests**: other places in the code the claim relies on. Each links to the file at the reviewed commit, with its line, such as **Line 42 in a1b2c3d**, and the lines themselves.
6. **Cites**: the **Rule**, **Memory** and **Skill** entries the finding relies on. See [Rules and memories](https://docs.ironbee.ai/code-review/rules-and-memories.md).
7. **History**: what happened to the finding, in order:
   * **Posted by the review at a1b2c3d**.
   * Each later change: **Still open**, **Stands**, **Addressed**, **The code changed**, **The code went away**, **Withdrawn** or **Turned down**, with **after a reply on the thread** and the commit when they apply. IronBee's sentence about it follows. **Read the whole reply on GitHub** opens the reply, a line such as **now rated high** shows a new severity, and **the thread was resolved by someone else** says a person, not IronBee, resolved it.
   * How the thread stands now: **Thread open on GitHub**, **Thread resolved by IronBee**, **No comment on GitHub any more**, or **Listed in the review body; no comment of its own**.

**Suggested fix** and **How it happens** appear when the review wrote them; the **Suggested fixes** and **Diagrams** settings turn them on or off.

### Move between findings

The footer shows where the finding stands in the list, such as **3 of 14**, and the buttons **Previous** and **Next**. **Next** names the next finding's file and line. The order is the list's, with its filters.

Press `←` and `→` to move, and `Esc` to close. Inside the code, the arrow keys scroll it instead.

![A High finding in the finding dialog, with Happens when and Then, the marked diff of core/selector.py and the Suggested fix](https://mintcdn.com/ironbee/yXiHzqPAo_3Hu63x/images/console/code-review/finding-dialog-light.png?fit=max\&auto=format\&n=yXiHzqPAo_3Hu63x\&q=85\&s=16cd479abb7e9f9e9f316fdec4f272c6)

![A High finding in the finding dialog, with Happens when and Then, the marked diff of core/selector.py and the Suggested fix](https://mintcdn.com/ironbee/yXiHzqPAo_3Hu63x/images/console/code-review/finding-dialog-dark.png?fit=max\&auto=format\&n=yXiHzqPAo_3Hu63x\&q=85\&s=d693f4b52200d99f97bdfe207e5d495f)

***

## Who can see and do what

| Capability | Who can do it |
| - | - |
| View the pull request lists, the pull request page and the finding dialog | Everyone |
| **Review now** | Owner, Admin, Member |
| **Review** in the **Needs review** list | Owner, Admin, Member |
| **Cancel** a job | Owner, Admin, Member |

Billing admins see none of these buttons. On an archived project, **Review now** is disabled. See [Roles and permissions](https://docs.ironbee.ai/console/roles.md).

***

## What's next?

> [card] [Code review](https://docs.ironbee.ai/code-review/overview.md)
>
> How IronBee reviews a pull request.

> [card] [Code review on GitHub](https://docs.ironbee.ai/code-review/on-github.md)
>
> What IronBee posts on the pull request itself.

> [card] [Code review settings](https://docs.ironbee.ai/code-review/settings.md)
>
> Depth, focus areas, comments and the merge block.

> [card] [Rules and memories](https://docs.ironbee.ai/code-review/rules-and-memories.md)
>
> What a finding can cite, and how to manage it.


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