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

# Rollout Permissions

<Card title="Tutorial: Deploy Schema Change with Rollout Policy" icon="graduation-cap" href="/tutorials/deploy-schema-migration" horizontal />

Configure who can deploy database changes and what conditions must be met before rollout can proceed in Environment and Project.

## Configure rollout policy in Environment

### Role-based manual rollout

**Default roles with permissions**: Users with the `bb.taskRuns.create` permission can perform rollouts. The following roles have this permission by default: `Workspace Admin`, `Workspace DBA`, `Project Owner`, `Project Releaser`.

**Environment-specific roles**: If you want to use different roles to perform rollouts in different environments, you can specify environment-specific roles. This allows you to control who can deploy changes to specific environments, such as having different teams responsible for staging versus production deployments.

### Automatic rollout

Select the `automatic` option to deploy changes without a manual rollout step. Changes then deploy automatically as soon as the [configured rollout requirements](#configurable-rollout-requirements-in-project) (approval and plan checks) are satisfied.

<Note>
  Do not enable automatic rollout when using the GitOps workflow, as it can cause conflicts that result in failures.
</Note>

## Configurable rollout requirements in Project

Configure what conditions must be met before changes can be rolled out in each environment:

### Require issue approval before creating rollout

The issue must be approved before creating a rollout.

**Default**: Enabled

### Require plan checks to pass before creating rollout

Plan checks must pass without error before creating a rollout. Warnings don't block — only errors do.

**Default**: Enabled

<Note>
  Plan checks include [SQL Review policy](/sql-review/review-policy) violations and other automated validations configured for your environment.
</Note>