Published at: 2026-10-15
Configure Backend Positions and Roles
- Management Backend → Application List > Knowledge Base > Role Settings.
- Assign the Knowledge Base Administrator role; grant backend entries.
❗
Only Knowledge Base Administrator remains an effective backend role. Operator/entry staff are covered by frontend permissions.
Overview
Confirm the backend roles and permission boundaries of Knowledge Base 2.0. Only the knowledge base administrator remains an effective backend role; the other legacy roles no longer apply.
Current rules
In Knowledge Base 2.0, only the knowledge base administrator remains an effective backend role. Knowledge operations personnel and knowledge entry personnel have been mapped to the new front-end permission logic; for both new and existing users, these two backend roles no longer take effect.
| Legacy role | Status in 2.0 | How 2.0 handles it |
|---|---|---|
| Knowledge base administrator | Still effective | Handles necessary system settings and existing 1.0 custom backend configurations. |
| Knowledge operations personnel | No longer effective | Grant front-end space or folder manage/edit resource permissions according to responsibility. |
| Knowledge entry personnel | No longer effective | Grant front-end space or folder edit resource permissions according to responsibility. |
Important: the role migration rule applies to both new and existing users. Do not continue to assign the knowledge operations or knowledge entry backend roles to members.
Where knowledge maintenance and permission management happen
- Knowledge creation, editing, publishing, retirement and daily operations are done in the front end of the knowledge base.
- Whether a member can view, download, edit or manage knowledge is decided by the front-end space and folder resource permissions.
- Category permissions in backend AI knowledge entries no longer take effect.
- Visibility permissions in backend enterprise knowledge spaces no longer take effect.
- Backend roles cannot replace or override front-end resource permissions.
When to enter the backend
The knowledge base administrator enters the backend only in the following scenarios:
- Handle product activation, application entry or other system-level settings.
- Maintain custom configurations already built on Knowledge Base 1.0.
- Check integrations, publishing channels or historical configurations that still require the backend.
If the enterprise has no Knowledge Base 1.0 custom configurations, it is not recommended to keep maintaining knowledge in the backend.
Configure front-end permissions
- Enter the knowledge space or folder to authorize.
- Open permission settings.
- Configure resource permissions for members, departments, roles or user groups.
- Use a test account to check lists, search, knowledge Q&A and Agent scope.
Expected results and verification
- Confirm the knowledge base administrator can enter the necessary backend settings.
- Confirm knowledge maintainers complete their work through front-end resource permissions.
- Confirm the operations and entry backend roles are no longer used as permission basis.
- Confirm knowledge visibility is based on front-end space and folder permissions.