refactor: reorganize change database settings and navigation (#860)

* refactor: reorganize change database settings and navigation

- Moved Settings group from UI-Driven Workflow to top-level "General" group
- Combined issue.mdx and transaction-mode.mdx into single settings.mdx file
- Moved schema-template to Change group under UI-Driven Workflow
- Simplified and clarified content in settings page
- Removed unnecessary screenshots

This improves navigation structure and makes settings more discoverable.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

* fix: update broken links to new settings page

- Update link in custom-approval.mdx from /change-database/issue/#self-approval to /change-database/settings#self-approval
- Update links in troubleshoot.mdx from /change-database/issue/#postgres-database-tenant-mode to /change-database/settings#postgres-tenant-mode

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

---------

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

Author: d-bytebase

mintlify/administration/custom-approval.mdx

@@ -16,7 +16,7 @@ Custom Approval allows you to create multi-stage approval workflows based on cha
 <Tip>
 **Best Practices:**
 - Custom Approval works best with [UI workflow](/change-database/change-workflow/#ui-workflow). For [GitOps workflow](/change-database/change-workflow/#gitops-workflow), configure approvals in your PR/MR process instead.
-- By default, users cannot self-approve their own issues. You can [change this setting](/change-database/issue/#self-approval) in project settings if needed.
+- By default, users cannot self-approve their own issues. You can [change this setting](/change-database/settings#self-approval) in project settings if needed.
 </Tip>
 
 ## How It Works

mintlify/change-database/issue.mdx

@@ -0,0 +1,36 @@
+---
+title: Settings
+---
+
+Customize how database changes work in your projects. Navigate to **Project** → **Settings** to access these options.
+
+## Transaction Mode
+
+<Note>
+Supported databases: MySQL, PostgreSQL, Oracle, SQL Server, TiDB, Redshift
+</Note>
+
+By default, Bytebase wraps SQL statements in a transaction for safety - if something goes wrong, changes can be rolled back.
+
+Some DDL statements can't run inside transactions. To disable transaction wrapping, add this comment before your SQL:
+
+```sql
+-- txn-mode=off
+ALTER TABLE t ALTER COLUMN a TYPE VARCHAR(255);
+```
+
+## Postgres Tenant Mode
+
+Perfect for multi-tenant PostgreSQL setups where each database has its own owner.
+
+When enabled, Bytebase automatically switches to the database's OWNER role before executing changes, ensuring proper permissions.
+
+**Location:** Project → Settings → Issue Related
+
+## Self Approval
+
+By default, issue creators can't approve their own changes.
+
+To allow self-approval, enable **Allow self approval** in your project settings.
+
+**Location:** Project → Settings → Issue Related

mintlify/change-database/settings.mdx

@@ -26,7 +26,7 @@ Following permission errors are likely to happen if either conditions meet:
 
 ### ERROR: permission denied to set role xxx (SQLSTATE 42501)
 
-This could happen if you turn on [Postgres database tenant mode](/change-database/issue/#postgres-database-tenant-mode).
+This could happen if you turn on [Postgres database tenant mode](/change-database/settings#postgres-tenant-mode).
 
 You need to grant the database owner permission to the Bytebase user configured in your PostgreSQL instance.
 
@@ -44,7 +44,7 @@ If you use AlloyDB, the database owner must NOT be created via [Cloud IAM](https
 
 ### ERROR: must be owner of table xxx (SQLSTATE 42501)
 
-This could happen if you turn on [Postgres database tenant mode](/change-database/issue/#postgres-database-tenant-mode).
+This could happen if you turn on [Postgres database tenant mode](/change-database/settings#postgres-tenant-mode).
 
 For some sophisticated setup where database owner and table owner are different, this causes problem.
 Because only table owner can alter that table schema, and if the database owner is not a member of

mintlify/change-database/transaction-mode.mdx

@@ -97,6 +97,7 @@
                   "change-database/synchronize-schema",
                   "change-database/stored-procedure",
                   "change-database/schema-editor",
+                  "change-database/schema-template",
                   "change-database/online-schema-migration-for-mysql"
                 ]
               },
@@ -133,16 +134,6 @@
                 "group": "Monitor",
                 "pages": ["change-database/drift-detection"]
               },
-              {
-                "group": "Settings",
-                "pages": [
-                  "change-database/webhook",
-                  "change-database/risk-center",
-                  "change-database/issue",
-                  "change-database/transaction-mode",
-                  "change-database/schema-template"
-                ]
-              },
               "change-database/troubleshoot"
             ]
           },
@@ -152,6 +143,14 @@
               "gitops/overview",
               "gitops/release"
             ]
+          },
+          {
+            "group": "General",
+            "pages": [
+              "change-database/webhook",
+              "change-database/risk-center",
+              "change-database/settings"
+            ]
           }
         ]
       },