Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions mintlify/docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@
]
},
{
"tab": "Features",
"tab": "Database CI/CD",
"groups": [
{
"group": "Database CI/CD",
Expand Down Expand Up @@ -148,7 +148,12 @@
},
"change-database/troubleshoot"
]
},
}
]
},
{
"tab": "SQL Editor",
"groups": [
{
"group": "SQL Editor",
"pages": [
Expand Down
4 changes: 2 additions & 2 deletions mintlify/introduction/what-is-bytebase.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ It's a unified platform specifically built for your **developer, security, DBA,

## 🚀 Managing Schema Changes at Scale

This section covers how Bytebase makes all database changes safer and more efficient. By providing a structured process, it also enhances security by **eliminating the need for engineers to make direct changes against databases**. Bytebase supports two distinct workflows for schema changes:
This section covers how Bytebase makes all database changes safer and more efficient. By providing a structured process, it also enhances security by **eliminating the need for engineers to make direct changes against databases**. Learn more in the [Database CI/CD](/change-database/change-workflow) section. Bytebase supports two distinct workflows for schema changes:

**UI-driven Workflow**: Provides a complete, console-based process with built-in risk analysis and multi-step approvals, offering a secure and self-contained way to manage schema changes.

Expand All @@ -26,7 +26,7 @@ In addition to these workflows, the platform provides overarching capabilities f

## 🛡️ Governing Data Access at Scale

This workflow governs how your database data is accessed, replacing the need for disparate SQL clients and shared credentials.
This workflow governs how your database data is accessed, replacing the need for disparate SQL clients and shared credentials. Explore the full capabilities in the [SQL Editor](/sql-editor/overview) section.

**Centralized Access Control:** Grant data query permissions based on role, not on sharing database passwords. This provides a single place to manage who can see what across your entire environment.

Expand Down