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

package/dist/ai/docs/nocobase/multi-app/multi-app/sub-app-api.md

@@ -0,0 +1,112 @@
+---
+pkg: '@nocobase/plugin-app-supervisor'
+title: 'Calling sub-app APIs'
+description: 'How to call sub-app APIs in multi-app: access sub-app APIs through the entry app and specify the target sub-app with a path prefix, request header, or query parameter.'
+keywords: 'multi-app,sub-app API,AppSupervisor,entry app,API call,NocoBase'
+---
+
+# Calling sub-app APIs
+
+In a multi-app setup, each sub-app has its own independent APIs. When calling a sub-app API, the entry app needs to know which sub-app the request should be routed to.
+
+For example, a main app API is usually:
+
+```bash
+GET /api/users:list
+```
+
+`/api` is the default API prefix and can be customized with the `API_BASE_PATH` environment variable.
+
+To call the same API in a sub-app, specify the sub-app name in the request.
+
+## Use a path prefix
+
+Use the `/api/__app/<appName>/` prefix to call sub-app APIs:
+
+```bash
+GET /api/__app/a_xxx/users:list
+```
+
+Where:
+
+- `a_xxx` is the sub-app name
+- `users:list` is the resource and action to call
+- `/api` is the current system's API base path
+
+Query parameters can be appended as usual:
+
+```bash
+GET /api/__app/a_xxx/users:list?page=1&pageSize=20
+```
+
+This approach is explicit and works well when sub-app APIs are accessed through the entry app in multi-environment deployments.
+
+## Specify the sub-app with a request header
+
+If the caller already uses a fixed `/api/...` address, specify the sub-app with the `X-App` request header:
+
+```bash
+curl \
+  -H "X-App: a_xxx" \
+  http://localhost:13003/api/users:list
+```
+
+This is suitable for backend service calls, or when a frontend request utility already centralizes API URLs and only needs an additional header.
+
+## Specify the sub-app with a query parameter
+
+You can also specify the sub-app with the `__appName` query parameter:
+
+```bash
+GET /api/users:list?__appName=a_xxx
+```
+
+If there are other query parameters, pass them together:
+
+```bash
+GET /api/users:list?__appName=a_xxx&page=1&pageSize=20
+```
+
+In general, the path prefix or request header is clearer because the target sub-app is more explicit.
+
+## API address in multi-environment deployments
+
+In multi-environment deployments, there is usually an entry app and multiple runtime environments.
+
+For example:
+
+- Entry app address: `http://localhost:13003`
+- Runtime environment address: `http://localhost:14000`
+
+When calling sub-app APIs, it is recommended to access them through the entry app:
+
+```bash
+GET http://localhost:13003/api/__app/a_xxx/users:list
+```
+
+The entry app routes the request to the corresponding sub-app according to the app configuration. If you clearly know which runtime environment to access, you can also call through that environment address.
+
+```bash
+GET http://localhost:14000/api/__app/a_xxx/users:list
+```
+
+## Sub-app custom domains
+
+If a sub-app has its own access domain, you can also call that sub-app's APIs directly through that domain:
+
+```bash
+GET https://app-example.example.com/api/users:list
+```
+
+If you want to go through the entry app uniformly, continue using the entry app's `/api/__app/<appName>/...` address.
+
+## Authentication
+
+When calling sub-app APIs, permission checks are still based on the target sub-app.
+
+This means:
+
+- A sign-in state or access token valid for the sub-app is required
+- The main app sign-in state does not automatically equal API permissions in the sub-app
+
+If the request does not carry valid authentication information, the sub-app returns an unauthenticated or unauthorized error according to its own authentication configuration.

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/all-in-one/installation.md

@@ -0,0 +1,181 @@
+---
+title: "All-in-One Business Suite - Installation"
+description: "Install the All-in-One Business Suite: one-click restore of the .nbdata backup file via Backup Manager. Requires NocoBase v2.1.0-alpha.40 or above and PostgreSQL 16; DB_UNDERSCORED must not be true."
+keywords: "all-in-one business suite installation, All-in-One, backup restore, Backup Manager, nbdata, PostgreSQL, NocoBase"
+---
+
+# Installation
+
+The All-in-One Business Suite covers six modules: **CRM, Sales Management, Help Desk, Project Management, IT Asset Management, and HR**. Use NocoBase's built-in **Backup Manager** plugin to restore the `.nbdata` backup file in one click and get the complete dataset.
+
+:::tip Prerequisites
+
+- A working NocoBase environment. For the main installation, see the [official installation docs](https://docs.nocobase.com/welcome/getting-started/installation)
+- NocoBase **v2.1.0-alpha.40 or above** (the Backup Manager plugin is open source since this version, available in the Community Edition)
+- The backup file downloaded: [nocobase_all_in_one_backup_260521.nbdata](https://static-docs.nocobase.com/nocobase_all_in_one_backup_260521.nbdata)
+
+:::
+
+:::warning Note
+
+- The solution is built on **PostgreSQL 16** — your environment must use PostgreSQL 16
+- **`DB_UNDERSCORED` must not be `true`** — check your `docker-compose.yml`; restore will fail if it is set to `true`
+- **Restore overwrites ALL data in the target app** — if the target already has data, back up the current app first and run the restore carefully
+
+:::
+
+The current release is deployed via **backup restore**. Future releases will switch to incremental migration to make integration with existing NocoBase systems easier.
+
+---
+
+## Steps
+
+### Step 1: Start the app with the `full` image
+
+Use the `full` Docker image. It bundles the database client and other companion tools, so no extra configuration is needed:
+
+```bash
+docker pull nocobase/nocobase:alpha-full
+```
+
+Then start NocoBase from this image.
+
+:::tip
+
+Without the `full` image, you may need to install the `pg_dump` client inside the container manually — a tedious and brittle process.
+
+:::
+
+### Step 2: Enable the Backup Manager plugin
+
+1. Sign in to NocoBase
+2. Open **Plugin Manager**
+3. Find and enable **Backup Manager**
+
+### Step 3: Restore from the local backup file
+
+1. After enabling the plugin, refresh the page
+2. From the left menu, go to **System Management / Backup Manager**
+
+   ![Backup Manager main UI](https://static-docs.nocobase.com/202510302154966.png)
+
+3. Click **Restore from local backup** in the top right
+4. Drag the downloaded `nocobase_all_in_one_backup_260521.nbdata` file onto the upload area
+
+   ![Restore from local backup file (upload dialog)](https://static-docs.nocobase.com/202510302155602.png)
+
+5. Click **Submit** and wait for the restore to complete — typically tens of seconds to a few minutes
+
+---
+
+## Notes
+
+- **Database compatibility** — PostgreSQL version, character set, and case sensitivity must match the backup source; the `schema` name in particular must be identical
+- **Commercial plugin match** — every commercial plugin used in the backup must be installed and enabled locally first, or the restore will be interrupted. The All-in-One solution uses commercial plugins such as Email Manager, Audit Log, and AI Employees. On the Community Edition, the entry points for missing plugins simply do not appear and the other modules are unaffected
+
+---
+
+## Post-install configuration
+
+The system is usable once the restore finishes, but two settings still point at our demo environment and need to be switched to your own.
+
+### 1. File storage engine (OSS / local)
+
+The demo backup ships with a storage engine pointing at our Alibaba Cloud OSS. The Access Key is not public, so any attachment field, print template, or AI employee avatar upload will fail.
+
+Local storage is usually enough; switch to your own OSS only when you need CDN acceleration or large-file workloads.
+
+**Switching steps:**
+
+1. Open **Plugin Manager / File Manager** (or go to `/admin/settings/file-manager`)
+
+2. **Option A — use local storage** (simplest, suited for self-hosted deployments):
+
+   - Find the auto-created **Local Storage** entry
+   - Click **Edit**, check **Set as default storage engine** at the bottom of the config panel, then submit
+
+   ![Storage engine common config (the "Set as default storage engine" toggle at the bottom)](https://static-docs.nocobase.com/20240529115151.png)
+
+   :::warning Note
+
+   For Docker deployments, local storage lives inside the container; deleting the container loses the files. In production, mount a volume or use cloud storage.
+
+   :::
+
+3. **Option B — use your own OSS / S3 / COS**:
+
+   - Click **Add new**, choose the matching type (Alibaba Cloud OSS / Amazon S3 / Tencent Cloud COS / S3 Pro)
+   - Fill in Access Key, Bucket, Region, domain, and other parameters, check **Set as default storage engine**, then submit
+
+   ![Alibaba Cloud OSS storage engine config example](https://static-docs.nocobase.com/20240712220011.png)
+
+4. Delete or disable the demo-preset OSS entry to avoid accidental use
+
+See [Storage engine overview](../../file-manager/storage/index.md) for parameter details.
+
+### 2. AI Employees LLM service keys
+
+The demo backup preloads several LLM service entries (OpenAI, Claude, Gemini, DeepSeek, Qwen, Kimi, etc.) using our own API keys, which **will not work for you**. The AI Employees features are unusable until you swap them out.
+
+**Configuration steps:**
+
+1. Open **System Settings / AI Employees / LLM service** (or go to `/admin/settings/ai/llm-services`)
+
+   ![Opening the LLM service config page](https://static-docs.nocobase.com/00_QuickStart_cn-2025-09-29-15-40-47.png)
+
+2. The preloaded service list supports drag-to-reorder and an **Enabled** toggle
+
+   ![LLM service list (enable toggle + sorting)](https://static-docs.nocobase.com/ai-employees/2026-02-14/llm-service-list-enabled-and-sort.png)
+
+3. For each service you plan to use:
+
+   - Click **Edit**
+   - Replace **API Key** with your own (from the matching provider account: OpenAI, Anthropic, Google AI Studio, DeepSeek, Qwen, Kimi, etc.)
+   - Adjust **Base URL** if you use a proxy or a regional relay
+   - In **Enabled Models**, keep the models you need and remove the rest
+
+   ![Editing an LLM service (API Key, Base URL, Enabled Models)](https://static-docs.nocobase.com/00_QuickStart_cn-2025-09-29-15-45-27.png)
+
+4. Click **Test flight** at the bottom to check connectivity, then **Submit** to save
+
+   ![Test flight connection check](https://static-docs.nocobase.com/00_QuickStart_cn-2025-09-29-16-18-25.png)
+
+5. For services you do not plan to use, just toggle **Disabled** — no need to delete
+
+See [Configure LLM service](../../ai-employees/features/llm-service.md) for the full configuration.
+
+:::tip
+
+These two are the only must-change items after restoring the demo. Other settings (site logo, SMTP, Enterprise plugins, etc.) can be tuned as needed.
+
+:::
+
+---
+
+## FAQ
+
+### Will it work on the Community Edition? Any errors?
+
+Yes, it works out of the box with no errors. Backup Manager has been open source since `v2.1.0-alpha.40`, so the Community Edition can install it. The demo does use some Enterprise plugins (Email Manager, Audit Log, AI Employees, etc.); on the Community Edition, the entry points for those features simply do not appear, but other modules are unaffected. For example, the Audit Log entry disappears, while CRM, Sales, Help Desk, Project, Asset, HR, and other core modules work normally.
+
+### Which version should I use after restore?
+
+Use the latest `alpha-full` image (`nocobase/nocobase:alpha-full`). The `full` image bundles the database client and other dependencies, avoiding restore failures caused by missing tools.
+
+### The logo does not display after restore?
+
+The logo in the official online demo has a domain restriction and cannot load on a local domain. Open **System Settings** and upload your own logo.
+
+### File upload fails (OSS key error)?
+
+The demo backup's preset storage engine points at our own OSS, and the key is not public. Open **Plugin Manager / File Manager**, set **Local Storage** as the default storage, save, and uploads will work again.
+
+See the [File storage engine](#1-file-storage-engine-oss--local) section above for details.
+
+### How do I switch languages?
+
+The All-in-One solution ships with localization for 20+ languages (under the `nb_demo` namespace). After restore, the default language is Chinese; switch via **System Settings / enable the target language**.
+
+### What about incremental upgrades?
+
+Today the upgrade path is a full replacement, which means custom changes are overwritten. Always back up before upgrading. An incremental migration plan is in the works.

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_260406.nbdata](https://static-docs.nocobase.com/nocobase_crm_v2_backup_260406.nbdata) - For Method 1
-  - **SQL file**: [nocobase_crm_v2_sql_260406.zip](https://static-docs.nocobase.com/nocobase_crm_v2_sql_260406.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_260327.sql`:
-
-  ```bash
-  # Copy the sql file into the container
-  docker cp nocobase_crm_v2_sql_260327.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_260327.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.