@nocobase/plugin-ai 2.1.0-alpha.45 → 2.1.0-alpha.46

package/dist/ai/docs/nocobase/ai-dev/capabilities.md

@@ -18,7 +18,7 @@ Here is a list of everything AI can currently help you do. Each capability comes
 
 :::warning Note
 
-- NocoBase is migrating from `client` (v1) to `client-v2`, and `client-v2` is still under development. The client code generated by AI development is based on `client-v2` and can only be used under the `/v2/` path. It is available for early access and experimentation, but is not recommended for production use.
+- NocoBase is migrating from `client` (v1) to `client-v2`, and `client-v2` is still under development. The client code generated by AI development is based on `client-v2` and can only be used under the `/v/` path. It is available for early access and experimentation, but is not recommended for production use.
 - AI-generated code may not be 100% correct. We recommend reviewing it before enabling. If you encounter issues at runtime, send the error message to AI and let it investigate and fix -- it usually takes just a few rounds of conversation to resolve.
 - We recommend using GPT or Claude series models for development, as they produce the best results. Other models can also work, but generation quality may vary.
 

package/dist/ai/docs/nocobase/ai-dev/index.md

@@ -33,7 +33,7 @@ Your browser will automatically open the visual configuration page, guiding you
 
 :::warning Note
 
-- NocoBase is migrating from `client` (v1) to `client-v2`, and `client-v2` is still under development. The client code generated by AI development is based on `client-v2` and can only be used under the `/v2/` path. It is available for early access and experimentation, but is not recommended for production use.
+- NocoBase is migrating from `client` (v1) to `client-v2`, and `client-v2` is still under development. The client code generated by AI development is based on `client-v2` and can only be used under the `/v/` path. It is available for early access and experimentation, but is not recommended for production use.
 - AI-generated code may not be 100% correct. We recommend reviewing it before enabling. If you encounter issues at runtime, send the error message to AI and let it investigate and fix -- it usually takes just a few rounds of conversation to resolve.
 - We recommend using GPT or Claude series models for development, as they produce the best results. Other models can also work, but generation quality may vary.
 

package/dist/ai/docs/nocobase/ai-dev/watermark-plugin.md

@@ -34,7 +34,7 @@ Make sure you have:
 
 :::warning Note
 
-- NocoBase is migrating from `client` (v1) to `client-v2`, and `client-v2` is still under development. The client code generated by AI development is based on `client-v2` and can only be used under the `/v2/` path. It is available for early access and experimentation, but is not recommended for production use.
+- NocoBase is migrating from `client` (v1) to `client-v2`, and `client-v2` is still under development. The client code generated by AI development is based on `client-v2` and can only be used under the `/v/` path. It is available for early access and experimentation, but is not recommended for production use.
 - AI-generated code may not be 100% correct. We recommend reviewing it before enabling. If you encounter issues at runtime, send the error message to AI and let it investigate and fix -- it usually takes just a few rounds of conversation to resolve.
 
 :::

package/dist/ai/docs/nocobase/api/cli/config/delete.md

@@ -18,14 +18,17 @@ nb config delete <key>
 
 | Parameter | Type | Description |
 | --- | --- | --- |
-| `<key>` | string | Configuration key: `license.pkg-url`, `docker.network`, or `docker.container-prefix` |
+| `<key>` | string | Configuration key: `locale`, `update.policy`, `license.pkg-url`, `docker.network`, `docker.container-prefix`, `bin.docker`, `bin.git`, or `bin.yarn` |
 
 ## Examples
 
 ```bash
+nb config delete locale
+nb config delete update.policy
 nb config delete license.pkg-url
 nb config delete docker.network
 nb config delete docker.container-prefix
+nb config delete bin.git
 ```
 
 ## Related Commands

package/dist/ai/docs/nocobase/api/cli/config/get.md

@@ -18,14 +18,17 @@ nb config get <key>
 
 | Parameter | Type | Description |
 | --- | --- | --- |
-| `<key>` | string | Configuration key: `license.pkg-url`, `docker.network`, or `docker.container-prefix` |
+| `<key>` | string | Configuration key: `locale`, `update.policy`, `license.pkg-url`, `docker.network`, `docker.container-prefix`, `bin.docker`, `bin.git`, or `bin.yarn` |
 
 ## Examples
 
 ```bash
+nb config get locale
+nb config get update.policy
 nb config get license.pkg-url
 nb config get docker.network
 nb config get docker.container-prefix
+nb config get bin.git
 ```
 
 ## Related Commands

package/dist/ai/docs/nocobase/api/cli/config/index.md

@@ -8,9 +8,27 @@ keywords: "nb config,NocoBase CLI,configuration,defaults"
 
 Manage CLI configuration defaults. Supported keys:
 
+- `locale`
+- `update.policy`
 - `license.pkg-url`
 - `docker.network`
 - `docker.container-prefix`
+- `bin.docker`
+- `bin.git`
+- `bin.yarn`
+
+## Common Keys
+
+| Key | Default | Description |
+| --- | --- | --- |
+| `locale` | current CLI locale resolution | Override the CLI locale |
+| `update.policy` | `prompt` | Startup update behavior: `prompt`, `auto`, or `off` |
+| `license.pkg-url` | `https://pkg.nocobase.com/` | Package registry for commercial packages |
+| `docker.network` | `nocobase` | Default Docker network used by CLI-managed Docker apps |
+| `docker.container-prefix` | `nb` | Default container prefix used by CLI-managed Docker apps |
+| `bin.docker` | `docker` | Override the Docker executable path |
+| `bin.git` | `git` | Override the Git executable path |
+| `bin.yarn` | `yarn` | Override the Yarn executable path |
 
 ## Usage
 
@@ -31,8 +49,11 @@ nb config <command>
 
 ```bash
 nb config list
+nb config get update.policy
+nb config set update.policy auto
 nb config get docker.network
 nb config set docker.network nocobase
+nb config set bin.git /usr/bin/git
 nb config delete docker.container-prefix
 ```
 

package/dist/ai/docs/nocobase/api/cli/config/set.md

@@ -6,7 +6,7 @@ keywords: "nb config set,NocoBase CLI,configuration"
 
 # nb config set
 
-Set a CLI configuration value. Supported keys are `license.pkg-url`, `docker.network`, and `docker.container-prefix`.
+Set a CLI configuration value. Supported keys are `locale`, `update.policy`, `license.pkg-url`, `docker.network`, `docker.container-prefix`, `bin.docker`, `bin.git`, and `bin.yarn`.
 
 ## Usage
 
@@ -18,21 +18,28 @@ nb config set <key> <value>
 
 | Parameter | Type | Description |
 | --- | --- | --- |
-| `<key>` | string | Configuration key: `license.pkg-url`, `docker.network`, or `docker.container-prefix` |
+| `<key>` | string | Configuration key: `locale`, `update.policy`, `license.pkg-url`, `docker.network`, `docker.container-prefix`, `bin.docker`, `bin.git`, or `bin.yarn` |
 | `<value>` | string | Configuration value; must not be empty |
 
 ## Examples
 
 ```bash
+nb config set locale zh-CN
+nb config set update.policy auto
 nb config set license.pkg-url https://pkg.nocobase.com/
 nb config set docker.network nocobase
 nb config set docker.container-prefix nb
+nb config set bin.docker /usr/local/bin/docker
+nb config set bin.git /usr/bin/git
+nb config set bin.yarn yarn
 ```
 
 ## Notes
 
 When setting `license.pkg-url`, the CLI normalizes the URL so it ends with `/`.
 
+`update.policy` supports `prompt`, `auto`, and `off`. The default is `prompt`.
+
 ## Related Commands
 
 - [`nb config get`](./get.md)

package/dist/ai/docs/nocobase/api/cli/self/update.md

@@ -21,6 +21,7 @@ nb self update [flags]
 | `--channel` | string | Release channel to update to, default `auto`; options: `auto`, `latest`, `beta`, `alpha` |
 | `--yes`, `-y` | boolean | Skip update confirmation |
 | `--json` | boolean | Output JSON |
+| `--skills` | boolean | Also refresh the globally installed NocoBase AI coding skills |
 | `--verbose` | boolean | Show detailed update output |
 
 ## Examples
@@ -28,6 +29,7 @@ nb self update [flags]
 ```bash
 nb self update
 nb self update --yes
+nb self update --skills
 nb self update --channel alpha --json
 ```
 

package/dist/ai/docs/nocobase/get-started/installation/env.md

@@ -294,7 +294,7 @@ Log print format. Default is `console` in development and `json` in production.
 LOGGER_FORMAT=json
 ```
 
-Reference: [Log Format](/log-and-monitor/logger/index.md#log-format)
+Reference: [Log Format](/log-and-monitor/logger/index.md#log-formats)
 
 ### CACHE_DEFAULT_STORE
 
@@ -375,8 +375,10 @@ Supported formats:
 Used to append preset local plugins. The value is the package name (the `name` parameter in `package.json`), with multiple plugins separated by commas.
 
 :::info
+
 1. Ensure the plugin is downloaded locally and can be found in the `node_modules` directory. For more details, see [Plugin Organization](/plugin-development/project-structure).
 2. After adding the environment variable, the plugin will appear on the plugin manager page only after an initial installation (`nocobase install`) or upgrade (`nocobase upgrade`).
+
 :::
 
 ```bash
@@ -388,8 +390,10 @@ APPEND_PRESET_LOCAL_PLUGINS=@my-project/plugin-foo,@my-project/plugin-bar
 Used to append built-in plugins that are installed by default. The value is the package name (the `name` parameter in `package.json`), with multiple plugins separated by commas.
 
 :::info
+
 1. Ensure the plugin is downloaded locally and can be found in the `node_modules` directory. For more details, see [Plugin Organization](/plugin-development/project-structure).
 2. After adding the environment variable, the plugin will be automatically installed or upgraded during the initial installation (`nocobase install`) or upgrade (`nocobase upgrade`).
+
 :::
 
 ```bash
@@ -472,7 +476,7 @@ yarn cross-env \
 
 ### WORKFLOW_SCRIPT_MODULES
 
-Workflow JavaScript node available modules list. For details, see "[JavaScript Node: Using External Modules](/workflow/nodes/javascript#using-external-modules)".
+Workflow JavaScript node available modules list. For details, see "[JavaScript Node: Using External Modules](/workflow/nodes/javascript#unsafe-mode-module-support)".
 
 ### WORKFLOW_LOOP_LIMIT
 

package/dist/ai/docs/nocobase/integration/embed/index.md

@@ -10,12 +10,12 @@ This plugin is used to embed NocoBase pages into other websites or applications.
 
 ## Installation
 
-This is a commercial plugin. For detailed activation instructions, please refer to: [Commercial Plugin Activation Guide](https://www.nocobase.com/en/blog/nocobase-commercial-license-activation-guide)
+Enable the "Embed NocoBase" plugin in the plugin manager to use it.
 
 
 ## User Guide
 
-After activating the interface configuration, click "Copy embedded link" in the page's configuration menu (top right corner).
+After enabling the plugin, click "Copy embedded link" in the page's configuration menu (top right corner).
 
 
 ![](https://static-docs.nocobase.com/f11bd6d5e88d38731d7cd3cb149022c8.png)
@@ -27,4 +27,4 @@ After clicking, you will get a link that can be opened separately, for example,
 ![](https://static-docs.nocobase.com/9d847805a00fd07372a474665ec0e968.png)
 
 
-If you want to embed NocoBase pages into other websites or applications, user authentication is required, and the `token` needs to be appended to the link, for example, `https://example.com/embed/qs087rz4o2b?token=xxx`.
+If you want to embed NocoBase pages into other websites or applications, user authentication is required, and the `token` needs to be appended to the link, for example, `https://example.com/embed/qs087rz4o2b?token=xxx`.

package/dist/ai/docs/nocobase/plugin-development/build.md

@@ -44,6 +44,10 @@ yarn build @my-project/plugin-hello --tar
 
 Upload and extract the `.tar.gz` file to the target application's `./storage/plugins` directory. For detailed steps, see [Install and Upgrade Plugins](../get-started/install-upgrade-plugins.mdx).
 
+### Enable a Plugin by Default
+
+After uploading, the plugin is not activated automatically — it appears in the Plugin Manager and must be enabled manually. If you are maintaining your own NocoBase application and want the plugin to be enabled by default along with the application, you can use the `APPEND_PRESET_BUILT_IN_PLUGINS` (append built-in plugins) environment variable. See [Make a Plugin Preset or Built-in by Default](./write-your-first-plugin.md#make-a-plugin-preset-or-built-in-by-default-optional) for usage.
+
 ## Custom Build Configuration
 
 In most cases, the default build configuration is sufficient. If you need to customize it — such as modifying the bundle entry, adding aliases, adjusting compression options, etc. — you can create a `build.config.ts` file in the plugin root directory:
@@ -84,3 +88,4 @@ Key points:
 - [Dependency Management](./dependency-management.md) — Plugin dependency declarations and global dependencies
 - [Plugin Development Overview](./index.md) — Overall introduction to plugin development
 - [Install and Upgrade Plugins](../get-started/install-upgrade-plugins.mdx) — Upload packaged files to target environments
+- [Environment Variables](../get-started/installation/env.md) — Environment variable configuration for preset and built-in plugins

package/dist/ai/docs/nocobase/plugin-development/client/appendix/faq.md

@@ -38,11 +38,11 @@ If client code changes don't hot reload, try refreshing the browser first.
 
 ### Registered page route is not accessible
 
-NocoBase v2 routes automatically add a `/v2` prefix. For example, if you registered `path: '/hello'`, the actual URL is `/v2/hello`:
+NocoBase v2 routes automatically add a `/v` prefix. For example, if you registered `path: '/hello'`, the actual URL is `/v/hello`:
 
 ```ts
 this.router.add('hello', {
-  path: '/hello', // actual URL -> /v2/hello
+  path: '/hello', // actual URL -> /v/hello
   componentLoader: () => import('./pages/HelloPage'),
 });
 ```
@@ -285,7 +285,7 @@ NocoBase's build system maintains an [external list](../../dependency-management
 ## Related Links
 
 - [Plugin](../plugin) — Plugin entry and lifecycle
-- [Router](../router) — Route registration and the `/v2` prefix
+- [Router](../router) — Route registration and the `/v` prefix
 - [FlowEngine Overview](../flow-engine/index.md) — FlowModel basics
 - [FlowEngine - Block Extension](../flow-engine/block) — BlockModel, TableBlockModel, filterCollection
 - [FlowEngine - Field Extension](../flow-engine/field) — FieldModel, bindModelToInterface

package/dist/ai/docs/nocobase/plugin-development/client/component/index.md

@@ -118,7 +118,7 @@ const msg = ctx.t('Save success', { ns: '@my-project/plugin-hello' });
 Use `ctx.router.navigate()` for page navigation:
 
 ```tsx
-ctx.router.navigate('/some-page'); // -> /v2/some-page
+ctx.router.navigate('/some-page'); // -> /v/some-page
 ```
 
 Get current route parameters:

package/dist/ai/docs/nocobase/plugin-development/client/ctx/common-capabilities.md

@@ -316,7 +316,7 @@ Navigate between pages in components via `ctx.router.navigate()`:
 
 ```tsx
 const ctx = useFlowContext();
-ctx.router.navigate('/hello'); // -> /v2/hello
+ctx.router.navigate('/hello'); // -> /v/hello
 ```
 
 ### Route Information (ctx.route)
@@ -351,7 +351,7 @@ interface RouteOptions {
 ```tsx
 const ctx = useFlowContext();
 
-console.log(ctx.location.pathname); // '/v2/hello'
+console.log(ctx.location.pathname); // '/v/hello'
 console.log(ctx.location.search);   // '?page=1'
 console.log(ctx.location.hash);     // '#section'
 ```

package/dist/ai/docs/nocobase/plugin-development/client/ctx/index.md

@@ -85,7 +85,7 @@ async load() {
 ```tsx
 // In component: page navigation
 const ctx = useFlowContext();
-ctx.router.navigate('/hello'); // -> /v2/hello
+ctx.router.navigate('/hello'); // -> /v/hello
 ```
 
 ## Common Capabilities Provided by Context

package/dist/ai/docs/nocobase/plugin-development/client/router.md

@@ -15,7 +15,7 @@ Route registration is typically done in the plugin's `load()` method. See [Plugi
 
 :::warning Note
 
-For NocoBase v2 plugins, registered routes automatically get a `/v2` prefix. You need to include this prefix when accessing the routes.
+For NocoBase v2 plugins, registered routes automatically get a `/v` prefix. You need to include this prefix when accessing the routes.
 
 :::
 
@@ -25,9 +25,9 @@ NocoBase has the following default routes registered:
 
 | Name           | Path                  | Component           | Description               |
 | -------------- | --------------------- | ------------------- | ------------------------- |
-| admin          | /v2/admin/\*          | AdminLayout         | Admin pages               |
-| admin.page     | /v2/admin/:name       | AdminDynamicPage    | Dynamically created pages |
-| admin.settings | /v2/admin/settings/\* | AdminSettingsLayout | Plugin settings pages     |
+| admin          | /v/admin/\*          | AdminLayout         | Admin pages               |
+| admin.page     | /v/admin/:name       | AdminDynamicPage    | Dynamically created pages |
+| admin.settings | /v/admin/settings/\* | AdminSettingsLayout | Plugin settings pages     |
 
 ## Page Routes
 
@@ -55,7 +55,7 @@ class MyPlugin extends Plugin {
   async load() {
     this.router.add('hello', {
       path: '/hello',
-      // Lazy loading: the module is loaded only when /v2/hello is visited
+      // Lazy loading: the module is loaded only when /v/hello is visited
       componentLoader: () => import('./pages/HelloPage'),
     });
   }
@@ -103,12 +103,12 @@ class MyPlugin extends Plugin {
 
     // Child route, using componentLoader for lazy loading
     this.router.add('root.home', {
-      path: '/', // -> /v2/
+      path: '/', // -> /v/
       componentLoader: () => import('./pages/HomePage'),
     });
 
     this.router.add('root.about', {
-      path: '/about', // -> /v2/about
+      path: '/about', // -> /v/about
       componentLoader: () => import('./pages/AboutPage'),
     });
   }
@@ -121,7 +121,7 @@ Route paths support dynamic parameters:
 
 ```tsx
 this.router.add('root.user', {
-  path: '/user/:id', // -> /v2/user/:id
+  path: '/user/:id', // -> /v/user/:id
   componentLoader: () => import('./pages/UserPage'),
 });
 ```
@@ -176,7 +176,7 @@ export class HelloPlugin extends Plugin<any, Application> {
 }
 ```
 
-After registration, the access path is `/admin/settings/hello`. When there is only one page under the menu, the top tab bar is automatically hidden.
+After registration, the access path is `/v/admin/settings/hello`. When there is only one page under the menu, the top tab bar is automatically hidden.
 
 ### Multi-Tab Settings Page
 
@@ -194,7 +194,7 @@ class HelloPlugin extends Plugin<any, Application> {
       icon: 'ApiOutlined',
     });
 
-    // Tab 1: General settings (key 'index' maps to /admin/settings/hello)
+    // Tab 1: General settings (key 'index' maps to /v/admin/settings/hello)
     this.pluginSettingsManager.addPageTabItem({
       menuKey: 'hello',
       key: 'index',
@@ -202,7 +202,7 @@ class HelloPlugin extends Plugin<any, Application> {
       componentLoader: () => import('./settings/GeneralPage'),
     });
 
-    // Tab 2: Advanced settings (maps to /admin/settings/hello/advanced)
+    // Tab 2: Advanced settings (maps to /v/admin/settings/hello/advanced)
     this.pluginSettingsManager.addPageTabItem({
       menuKey: 'hello',
       key: 'advanced',

package/dist/ai/docs/nocobase/plugin-development/write-your-first-plugin.md

@@ -118,6 +118,33 @@ After activation, create a new "Modern page (v2)" page. When adding blocks, you'
 
 ![20250928174529](https://static-docs.nocobase.com/20250928174529.png)
 
+### Make a Plugin Preset or Built-in by Default (Optional)
+
+The steps above describe manually enabling a single plugin. If you are maintaining your own NocoBase application and want certain plugins to be automatically ready after running `nocobase install` (first-time installation) or `nocobase upgrade` (upgrade), you can use two environment variables to control a plugin's default state:
+
+- **`APPEND_PRESET_LOCAL_PLUGINS` (append preset local plugins)** — Adds the plugin to the preset local plugin list. After installation it appears in the Plugin Manager but is not activated by default; you need to enable it manually.
+- **`APPEND_PRESET_BUILT_IN_PLUGINS` (append built-in plugins)** — Adds the plugin to the built-in plugin list. It is automatically activated on installation and, as a built-in plugin, **cannot be disabled or deleted from the Plugin Manager**.
+
+The value for both variables is the plugin package name (the `name` field in `package.json`); separate multiple plugins with commas. Configure them in `.env` like this:
+
+```bash
+# Preset: appears in the Plugin Manager list but is not activated automatically
+APPEND_PRESET_LOCAL_PLUGINS=@my-project/plugin-hello,@my-project/plugin-hello-world
+
+# Built-in: automatically installed and activated, and cannot be disabled from the UI
+APPEND_PRESET_BUILT_IN_PLUGINS=@my-project/plugin-hello,@my-project/plugin-hello-world
+```
+
+For day-to-day local development and debugging, `yarn pm enable` (described above) is usually sufficient. These two variables are better suited for "out-of-the-box" distribution scenarios — for example, when you are shipping a NocoBase application bundled with a fixed set of plugins and want those plugins to be ready immediately after initialization.
+
+:::tip Note
+
+- The plugin must already be downloaded locally and resolvable in `node_modules`. See [Project Structure](./project-structure.md) for details.
+- After configuring, you need to re-run `nocobase install` or `nocobase upgrade` for the changes to take effect.
+- For the full list of environment variable options, see [Environment Variables](../get-started/installation/env.md#append_preset_local_plugins).
+
+:::
+
 ## Step 4: Build and Package
 
 When you're ready to distribute the plugin to other environments, you need to build and package it first:
@@ -158,4 +185,5 @@ Upload and extract the package file to the target application's `./storage/plugi
 - [Install using create-nocobase-app](../get-started/installation/create-nocobase-app) — One of the NocoBase installation methods
 - [Install from Git source](../get-started/installation/git) — Install NocoBase from source code
 - [Install and Upgrade Plugins](../get-started/install-upgrade-plugins.mdx) — Upload packaged plugins to other environments
+- [Environment Variables](../get-started/installation/env.md) — Environment variable configuration for preset and built-in plugins
 

package/dist/ai/docs/nocobase/solution/crm/changelog.md

@@ -8,7 +8,6 @@ This page documents the update history for the CRM solution. New entries are add
 
 **Backup files**:
 - [nocobase_crm_v2_backup_260406.nbdata](https://static-docs.nocobase.com/nocobase_crm_v2_backup_260406.nbdata)
-- [nocobase_crm_v2_sql_260406.zip](https://static-docs.nocobase.com/nocobase_crm_v2_sql_260406.zip)
 
 **Changes**:
 - Fixed table Summary aggregation display issue
@@ -24,7 +23,6 @@ This page documents the update history for the CRM solution. New entries are add
 
 **Backup files**:
 - [nocobase_crm_v2_backup_260327.nbdata](https://static-docs.nocobase.com/nocobase_crm_v2_backup_260327.nbdata)
-- [nocobase_crm_v2_sql_260327.zip](https://static-docs.nocobase.com/nocobase_crm_v2_sql_260327.zip)
 
 **Changes**:
 
@@ -52,7 +50,6 @@ This page documents the update history for the CRM solution. New entries are add
 
 **Backup files**:
 - nocobase_crm_v2_backup_260223.nbdata
-- nocobase_crm_v2_sql_260223.zip
 
 **Changes**:
 - Initial release of CRM 2.0

package/dist/ai/docs/nocobase/solution/crm/installation.md

@@ -2,15 +2,13 @@
 
 > The current version is deployed via **backup and restore**. In future versions, we may switch to **incremental migration** to make it easier to integrate the solution into your existing systems.
 
-To help you deploy the CRM 2.0 solution smoothly to your own NocoBase environment, we provide two restoration methods. Please choose the one that best suits your edition and technical background.
+> **The Backup Manager plugin is now open-source**: The "[Backup Manager](https://docs-cn.nocobase.com/handbook/backups)" plugin needed to restore the solution is now open-source and available to all editions (including the Community Edition). We recommend restoring directly via this plugin.
 
 Before you begin, please ensure:
 
 - You have a basic NocoBase running environment. For main system installation, please refer to the [official installation documentation](https://docs-cn.nocobase.com/welcome/getting-started/installation).
 - NocoBase version **v2.1.0-beta.2 or above**.
-- You have downloaded the corresponding CRM system files:
-  - **Backup file**: [nocobase_crm_v2_backup_260523.nbdata](https://static-docs.nocobase.com/nocobase_crm_v2_backup_260523.nbdata) - For Method 1
-  - **SQL file**: [nocobase_crm_v2_sql_260523.zip](https://static-docs.nocobase.com/nocobase_crm_v2_sql_260523.zip) - For Method 2
+- You have downloaded the CRM system backup file: [nocobase_crm_v2_backup_260523.nbdata](https://static-docs.nocobase.com/nocobase_crm_v2_backup_260523.nbdata)
 
 **Important Notes**:
 - This solution is built on **PostgreSQL 16**. Please ensure your environment uses PostgreSQL 16.
@@ -18,9 +16,9 @@ Before you begin, please ensure:
 
 ---
 
-## Method 1: Restore Using Backup Manager (Recommended for Pro/Enterprise Users)
+## Restore Using Backup Manager
 
-This method uses NocoBase's built-in "[Backup Manager](https://docs-cn.nocobase.com/handbook/backups)" (Pro/Enterprise Edition) plugin for one-click restoration. It is the simplest operation but has certain requirements for the environment and edition.
+This method uses NocoBase's built-in "[Backup Manager](https://docs-cn.nocobase.com/handbook/backups)" plugin for one-click restoration. It is the simplest operation. This plugin is now open-source and available to all editions (including the Community Edition).
 
 ### Key Characteristics
 
@@ -28,9 +26,8 @@ This method uses NocoBase's built-in "[Backup Manager](https://docs-cn.nocobase.
   1. **Convenient operation**: Completed within the UI, allowing for full restoration of all configurations including plugins.
   2. **Complete restoration**: **Able to restore all system files**, including print template files and files uploaded via file fields in collections, ensuring full functional integrity.
 * **Limitations**:
-  1. **Pro/Enterprise Edition only**: "Backup Manager" is an enterprise-level plugin available only to Pro/Enterprise users.
-  2. **Strict environment requirements**: Requires your database environment (version, case sensitivity settings, etc.) to be highly compatible with the environment where the backup was created.
-  3. **Plugin dependency**: If the solution includes commercial plugins not present in your local environment, the restoration will fail.
+  1. **Strict environment requirements**: Requires your database environment (version, case sensitivity settings, etc.) to be highly compatible with the environment where the backup was created.
+  2. **Plugin dependency**: If the solution includes commercial plugins not present in your local environment, the restoration will fail.
 
 ### Steps
 
@@ -69,69 +66,6 @@ Then use this image to start your NocoBase service.
 
 ---
 
-## Method 2: Direct SQL File Import (Universal, Better for Community Edition)
-
-This method restores data by directly operating on the database, bypassing the "Backup Manager" plugin, and therefore has no Pro/Enterprise Edition restrictions.
-
-### Key Characteristics
-
-* **Advantages**:
-  1. **No edition restrictions**: Suitable for all NocoBase users, including Community Edition.
-  2. **High compatibility**: Does not rely on the `dump` tool within the application; as long as you can connect to the database, you can operate.
-  3. **High fault tolerance**: If the solution includes commercial plugins you do not have, the related features will not be enabled, but it will not affect the normal use of other features, and the application can start successfully.
-* **Limitations**:
-  1. **Requires database operation skills**: Users need basic database operation skills, such as how to execute a `.sql` file.
-  2. **System file loss**: **This method will lose all system files**, including print template files and files uploaded via file fields in collections.
-
-### Steps
-
-**Step 1: Prepare a clean database**
-
-Prepare a brand new, empty database for the data you are about to import.
-
-**Step 2: Import the `.sql` file into the database**
-
-Obtain the downloaded database file (usually in `.sql` format) and import its content into the database you prepared in the previous step. There are several ways to execute this, depending on your environment:
-
-* **Option A: Via server command line (using Docker as an example)**
-  If you use Docker to install NocoBase and the database, you can upload the `.sql` file to the server and then use the `docker exec` command to perform the import. Assuming your PostgreSQL container is named `my-nocobase-db` and the filename is `nocobase_crm_v2_sql_260523.sql`:
-
-  ```bash
-  # Copy the sql file into the container
-  docker cp nocobase_crm_v2_sql_260523.sql my-nocobase-db:/tmp/
-  # Enter the container and execute the import command
-  docker exec -it my-nocobase-db psql -U nocobase -d nocobase -f /tmp/nocobase_crm_v2_sql_260523.sql
-  ```
-* **Option B: Via a remote database client (Navicat, etc.)**
-  If your database port is exposed, you can use any graphical database client (such as Navicat, DBeaver, pgAdmin, etc.) to connect to the database, then:
-  1. Right-click the target database.
-  2. Select "Run SQL File" or "Execute SQL Script".
-  3. Select the downloaded `.sql` file and execute.
-
-**Step 3: Connect to the database and start the application**
-
-Configure your NocoBase startup parameters (such as environment variables `DB_HOST`, `DB_PORT`, `DB_DATABASE`, `DB_USER`, `DB_PASSWORD`, etc.) to point to the database where you just imported the data. Then, start the NocoBase service normally.
-
-### Notes
-
-* **Database permissions**: This method requires you to have an account and password that can directly operate on the database.
-* **Plugin status**: After a successful import, although the data for commercial plugins included in the system exists, if you have not installed and enabled the corresponding plugins locally, the related features will not be displayed or usable, but this will not cause the application to crash.
-
----
-
-## Summary and Comparison
-
-| Feature | Method 1: Backup Manager | Method 2: Direct SQL Import |
-| :-------------- | :--------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------- |
-| **Applicable Users** | **Pro/Enterprise Edition** users | **All users** (including Community Edition) |
-| **Ease of Use** | ⭐⭐⭐⭐⭐ (Very simple, UI operation) | ⭐⭐⭐ (Requires basic database knowledge) |
-| **Environment Requirements** | **Strict**, database and system versions must be highly compatible | **General**, requires database compatibility |
-| **Plugin Dependency** | **Strong dependency**, plugins are validated during restoration; missing any plugin will cause **restoration failure**. | **Features strongly depend on plugins**. Data can be imported independently, and the system will have basic functionality. However, if corresponding plugins are missing, related features will be **completely unusable**. |
-| **System Files** | **Fully preserved** (print templates, uploaded files, etc.) | **Will be lost** (print templates, uploaded files, etc.) |
-| **Recommended Scenarios** | Enterprise users with controlled, consistent environments needing full functionality | Missing some plugins, seeking high compatibility and flexibility, non-Pro/Enterprise users, or those who can accept the loss of file features |
-
----
-
 ## FAQ
 
 ### Can Pro Edition users install this? Will it cause errors?
@@ -146,10 +80,6 @@ We recommend the latest `beta-full` image (e.g., `nocobase/nocobase:beta-full`).
 
 The demo's logo is configured with a domain restriction and cannot load on local domains. Go to **System Settings** and re-upload your own logo.
 
-### File upload error (OSS Key error)?
-
-After SQL import, file uploads may fail with an OSS-related error. Solution: go to **Plugin Manager → File Manager**, set **Local Storage** as the default storage, and save. Uploads will work normally after this.
-
 ### What about incremental upgrades?
 
 Currently, version upgrades are full replacements — your custom modifications will be overwritten. Always back up before upgrading. An incremental migration solution is being planned and will prioritize Pro/Enterprise editions. Community edition support is more difficult due to the lack of the migration management plugin.