> ## 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.

# Verify access and billing

> Which platforms support CodeRabbit Verify, which permissions it uses, and what it costs during the beta.

GitHub Cloud (Verify is available on GitHub Cloud. GitHub Enterprise Server is not supported.) GitLab.com (Verify is available on GitLab.com. GitLab self-managed is not supported.) Bitbucket Cloud (Verify is available on Bitbucket Cloud. Bitbucket Data Center is not supported.) | Cloud Only (This feature is available on CodeRabbit Cloud only. It is not available on self-hosted CodeRabbit deployments.) Open Beta (Verify is in beta and free during the beta.)

## Platform support

Verify runs on CodeRabbit Cloud for these Git providers:

| Platform | Verify |
| - | - |
| GitHub Cloud | Supported |
| GitLab.com | Supported |
| Bitbucket Cloud | Supported |
| GitHub Enterprise Server | Not supported |
| GitLab self-managed | Not supported |
| Bitbucket Data Center | Not supported |
| Azure DevOps | Not supported |
| Self-hosted CodeRabbit | Not supported |

Some parts of Verify differ by platform:

* The **Run CodeRabbit Verify to test the changes in this pull request.** checkbox in the walkthrough appears on GitHub only.
* Automatic pull request runs skip public GitHub repositories. Start runs on them with `@coderabbitai verify`.

Where Verify isn't available, **Verify** doesn't appear in the CodeRabbit app's sidebar, and `@coderabbitai verify` does nothing.

## Permissions

Verify has no permissions of its own. It uses the Coding Agent permissions from your organization's [roles](https://docs.coderabbit.ai/management/roles.md):

| Permission | What it allows in Verify |
| - | - |
| Coding Agent read | View repositories, runs, user journeys, schedules, bugs and blockers, and evidence. |
| Coding Agent write | Add repositories, change their settings, create and edit user journeys, start and stop runs, manage schedules, and create tickets. |

By default, the Admin and Member roles have both permissions. Users with the Billing Admin role can't use Verify. [Custom roles](https://docs.coderabbit.ai/management/custom-roles.md) can grant or withhold the **Coding Agent** resource like any other.

For users with read but not write access, the controls that change things, such as **Add repository** or the run buttons, are hidden or disabled.

Some tasks depend on more than these permissions:

* **Creating and preparing environments** is limited to organization admins with an assigned Review seat or an active trial. See [Coding environments](https://docs.coderabbit.ai/code/environments.md).
* **Starting a pull request run** with `@coderabbitai verify` requires write access to the repository in your Git provider. On GitLab, Verify also checks your membership in the GitLab organization. On GitHub, if the repository's configuration sets [`chat.allow_non_org_members`](https://docs.coderabbit.ai/reference/configuration#param-chat-allow-non-org-members) to `false`, you must also be a member of the GitHub organization.

### When you don't have access

If a Verify page needs a permission you don't have, it shows **Access needed for Verify setup** with the reason, such as "User does not have Coding Agent permissions.", and asks you to have a workspace administrator check your Verify permissions and repository access. Select **Copy access request** to copy a request you can send them, and **Check access again** after they've updated your access.

## Billing during the beta

Verify is free during the beta. While it is:

* Verify runs don't need the CodeRabbit Agent add-on.
* Verify runs aren't charged, and no Agent minutes are billed for them.
* The Agent [monthly spend cap](https://docs.coderabbit.ai/code/access-and-billing.md#monthly-spend-cap) doesn't apply to Verify runs.

The CodeRabbit app shows **Free during beta** next to **Verify** in the sidebar, and the banner "Verify is free during beta." on the repository list, the Activity page, and most repository pages until you dismiss it. Some screens, such as the dialog that turns on automatic runs, say that runs use Agent minutes; during the beta, Verify runs aren't charged for them.

The free beta covers Verify only. [Runtime verification](https://docs.coderabbit.ai/security/runtime-verification.md#usage-and-billing) in CodeRabbit Security uses the same environments but is billed as described on its page.

## What's next

> [card] [Set up Verify](https://docs.coderabbit.ai/verify/setup.md)
>
> Prepare an environment, add a repository, and choose when Verify runs.

> [card] [Roles](https://docs.coderabbit.ai/management/roles.md)
>
> See and change which role each person in your organization has.

> [card] [Troubleshooting](https://docs.coderabbit.ai/verify/troubleshooting.md)
>
> Fix access problems and runs that don't start.


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