- Document management: Upgrade from “knowledge notebook” to “Folder” for easier document management
- Knowledge Base templates: One-click save and reuse, helping team members create documents efficiently
- Efficiency upgrade: Sub-documents inherit parent document permissions by default for efficient authorization
- Feature upgrade: Permissions management supports adding and removing access. Set important team documents to be visible only to designated users
- Security upgrade: Strengthened security watermarks covering the entire Knowledge Base interface for more comprehensive information protection
01 Knowledge management upgrade: Efficient document management with what-you-see-is-what-you-get
Effective enterprise and organizational document management goes beyond storing and classifying organizational knowledge. It must also cover the full lifecycle of internal knowledge production, distribution, and consumption. This release introduces three major feature upgrades for efficient knowledge management: document management, mind map view, and team templates.1. Document management: Upgrade from “knowledge notebook” to “Folder” for easier document management
A new “Folder” concept lets you organize documents into folders. You can also choose to display all documents in a single tree structure. Custom logos and cover images are also supported, so each space can express its own identity.2. Knowledge Base templates: One-click save and reuse, helping team members create documents efficiently
To improve document efficiency and consistency, admins can save frequently used meeting, proposal, and report documents as team templates. Knowledge Base users can then apply a team template with one click, making document creation in the Knowledge Base both efficient and standardized.02 Permissions management upgrade: More secure documents and more efficient permission settings
Secure document management within teams and organizations is a core need for enterprise customers. This release brings three major permission management upgrades to the Knowledge Base: default permission inheritance, private documents, and security watermarks.1. Efficiency upgrade: Sub-documents inherit parent document permissions by default for efficient authorization
| #### Before | #### After the upgrade | #### Example 🌰 |
|---|---|---|
| Each sub-document had to be authorized individually. If a folder contained many sub-documents, this required many repetitive actions. | Once a document or folder is authorized, sub-documents inherit permissions by default and can also be modified individually. | Previously, Xiao Ding from operations had to grant document permissions to their manager every time they wrote a weekly report. Now, granting permissions to the weekly report folder once is enough. |
2. Feature upgrade: Permissions management supports adding and removing access. Set important team documents to be visible only to designated users
| #### Before | #### After the upgrade | #### Example 🌰 |
|---|---|---|
| Document permissions in the Knowledge Base supported only adding access, not removing it, making permissions management inflexible. | Document permissions can be set flexibly, with access freely added or removed, and can be set to be visible only to designated users. | When Xiao Ding moved from product to operations, their manager needed to remove their view permission for some documents. Previously, removal was not supported. After the upgrade, document permissions can be flexibly adjusted and updated. |
3. Security upgrade: Strengthened security watermarks covering the entire Knowledge Base interface for more comprehensive information protection
| #### Before | #### After the upgrade | #### Example 🌰 |
|---|---|---|
| The original security watermark appeared only on the document content page and did not cover the Knowledge Base structure or user information pages. | The watermark now covers the entire Knowledge Base interface, including the table of contents tree and the user management page. | Sales managers often note customer names in document titles for easy lookup. After the upgrade, watermarks cover document structures and Knowledge Base information to safeguard data security. |
03 Public publishing: Helps organizations securely publish information externally
The Knowledge Base “public publishing + approval” feature lets DingTalk users share documents externally with contacts and customers outside the organization. Documents can also be published as external links, allowing viewers to access content without logging in. This greatly improves the efficiency of enterprise information flow. Also launched is the innovative “manager approval” feature — the first document product in China to develop and release such a capability. It safeguards content security and control while improving content publishing review efficiency. This delivers a milestone innovation when sharing and publishing DingTalk Docs externally, truly achieving both “efficiency” and “security.” How to enable public publishing: Open DingTalk Docs, select a Knowledge Base, then click Share. Example — Equipment manuals: Department managers can upload equipment user guides and maintenance records to the Knowledge Base and publish them externally. The system generates a QR code that can be attached to equipment, so workshop staff can scan it to view information whenever an issue arises. Content updates require manager approval to prevent information leaks. Example — Product guides: Create product user guides to help users quickly understand product features. DingTalk itself uses DingTalk Docs and public publishing to build its own help guide, which users can view directly in a browser — easy and convenient, with no engineer required to build the page.How to use the Knowledge Base
- PC entry point: Open DingTalk — Click the left navigation to enter “DingTalk Docs” — Click “Knowledge Base”.
- Mobile: Open the DingTalk app — Tap “More” in the bottom menu — Open “Docs” — Tap “Knowledge Base” — Tap [+] to create.