Environment Policy

Configure and manage your database environments including policies, permissions, and lifecycle operations.

​

Environment tier

​

Environment color

You can configure any color for an environment either by inputting in HEX tab or choosing one in the palette. SQL Editor then displays the configured color tab.

​

Production indicator

Once you mark an environment as a production environment, Bytebase will attach a shield icon 🛡️ besides the environment name.

​

Rollout policy

Control who can deploy changes to each environment and whether deployments happen automatically or require manual approval.

​

SQL Review policy

Configure automated SQL validation rules for each environment to ensure code quality and compliance. Different environments can have different strictness levels - for example, production might enforce stricter rules than development.

​

Statement execution

Whether a user can run DDL and DML statements directly in SQL Editor is governed by the bb.sql.ddl and bb.sql.dml database permissions carried by their granted roles — the built-in SQL Editor User role includes both. The environments where DDL/DML may run directly are part of the permission itself, selected when granting the role. Without the permission on a database’s environment, SQL Editor directs the user to create a database change plan and follow the change workflow instead. There is no environment-level statement execution setting.

​

Delete an environment

To permanently delete an environment:

1. Navigate to the environment page
2. Click Delete this environment at the bottom of the page
3. Confirm the deletion