Published at: 2026-10-15

Legacy Knowledge Base Upgrade Instructions

This document explains the changes and check items after upgrading from Knowledge Base 1.0 to 2.0.

Main Changes

| Knowledge Base 1.0 | Knowledge Base 2.0 | |—|—| | Scattered maintenance entries | Unified homepage: new, upload, import, search, AI Q&A, task center | | Unclear progress | Task center shows upload/parse/generate/re-ingest progress | | Simple publish status | Draft, publishing, published, publish failed, unpublished | | Editing published content affects use | Official version continues; unpublished edits save as draft | | Permissions scattered | Space/folder resource permissions run through lists, search, AI | | Scattered source entries | Sources enter default-space source folders | | Entry/permissions depend on backend | Entry, maintenance, permissions move to frontend | | Operator/entry staff as backend roles | No longer effective; switch to frontend resource permissions |
Knowledge Base 2.0 homepage

Role and Permission Changes

  • Knowledge Base Administrator remains an effective backend role.
  • Knowledge operators and knowledge entry staff are mapped to the new frontend permission logic; neither role is used for new or existing users.
  • Permission settings for backend AI knowledge items and enterprise knowledge spaces no longer take effect; actual permissions follow the frontend space/folder resource permissions.
  • Enterprises without custom configuration based on Knowledge Base 1.0 are advised not to continue maintaining knowledge in the backend.

Legacy Data Handling

  1. Historical first-level folders are automatically migrated to frontend spaces.
  2. External data (network disk, CRM, shared notes, training assistant courses) is mapped to source folders in the default knowledge space.
  3. Existing permissions remain unchanged; on next edit, they are saved under the current resource’s independent permission model.
  4. Data sources with syncing enabled stay enabled; sources that were off stay off.

Post-Upgrade Check

  1. Check enterprise spaces, default knowledge spaces and source folders are complete.
  2. Spot-check visibility of spaces, folders and knowledge.
  3. Confirm published knowledge still participates in search and AI.
  4. Check sync status/logs of system data sources.
  5. Confirm only knowledge base administrators retain backend roles.
Submit Feedback