docs: update rollout policy from env to project (#972)

* update rollout policy from env to project

* update

* Update docs/change-database/environment-policy/rollout-policy.mdx

Co-authored-by: Copilot <[email protected]>

---------

Co-authored-by: Copilot <[email protected]>

Author: adela-bytebase

docs/change-database/environment-policy/rollout-policy.mdx

@@ -9,23 +9,28 @@ title: Rollout Permissions
   horizontal
 />
 
-Configure who can deploy database changes and what conditions must be met before rollout can proceed in each environment.
+Configure who can deploy database changes and what conditions must be met before rollout can proceed in Environment and Project.
 
-## Role-based rollout
+## Configure rollout policy in Environment
 
-### Default roles with permissions
+### Role-based manual rollout
 
-Users with the `bb.taskRuns.create` permission can perform rollouts. The following roles have this permission by default:
+**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 Releaser`.
 
-- Workspace Admin
-- Workspace DBA
-- 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.
 
-### Environment-specific roles
+### Automatic rollout
 
-If you want to use different roles to perform rollouts in different environments, you can specify environment-specific roles in the Environment policy settings. This allows you to control who can deploy changes to specific environments, such as having different teams responsible for staging versus production deployments.
+Enable automatic deployment when all checks pass by selecting the `automatic` option. This will automatically deploy changes when:
+
+- All required approvals are obtained (if "Require Issue Approval" is enabled)
+- Plan checks pass according to the configured enforcement policy
+
+<Note>
+Do not enable automatic rollout when using the GitOps workflow, as it can cause conflicts that result in failures.
+</Note>
 
-## Configurable rollout requirements
+## Configurable rollout requirements in Project
 
 Configure what conditions must be met before changes can be rolled out in each environment:
 
@@ -35,27 +40,12 @@ Ensures all changes are reviewed and approved before deployment to production en
 
 **Default**: Enabled
 
-### Plan check enforcement
+### Require plan check no error
 
-Controls how rollout behaves based on plan check results, including SQL Review policy violations and other validations:
+Controls how rollout behaves based on plan check results, including SQL Review policy violations and other validations. When enabled, rollout is blocked if checks return errors, but warnings still allow rollout.
 
-- **Block on errors only** (default): Rollout is blocked if checks return errors, but warnings still allow rollout
-- **Block on errors and warnings**: Rollout is blocked if checks return either errors or warnings
-- **Allow rollout regardless**: Rollout can proceed even if checks return errors or warnings
-
-**Default**: Block on errors only
+**Default**: Enabled
 
 <Note>
 Plan checks include [SQL Review policy](/sql-review/review-policy) violations and other automated validations configured for your environment.
-</Note>
-
-## Automatic rollout
-
-Enable automatic deployment when all checks pass by selecting the `automatic` option. This will automatically deploy changes when:
-
-- All required approvals are obtained (if "Require Issue Approval" is enabled)
-- Plan checks pass according to the configured enforcement level
-
-<Note>
-Do not enable automatic rollout for GitOps Workflow as it can cause conflicts that result in failures.
 </Note>