AConfiguring Edit Access
Feature released in SummitAI Service Management (Knowledge Management, Alps)
Problem Statement
Earlier, Knowledge Base (KB) Approvers and Publishers could not edit the Knowledge Records (KRs) and only Authors could make changes to the KRs. If any change was required in a KR, the Approver or Publisher had to refer back the KR to the Author. After the Author made the changes to the KR, it used to follow the regular approval cycle (Author > Authorizer > Approver > Publisher), which used to increase the overall time taken to publish the KRs. Only the published KRs are available to the End Users and Analysts. Due to this, many of the KRs were stuck in the approval cycles.
What is Happening Now?
Now, by default, the KR Authorizer, who is the Workgroup Owner, can edit the KRs. Additionally, the Administrators can also provide access to the Approvers and Publishers to edit the fields in Knowledge Record, thereby, eliminating the recurrent refer back process of modifying KRs. All the changes made to the KR are captured in the Change History.
Note:
Even if the Administrator provides edit access to the KB Approvers and Publishers, they cannot edit the following fields of a KR: Department, Workgroup, Owner, and Active.
For more information, see Knowledge Management, Authorizing Knowledge Records, Approving Knowledge Records, and Publishing Knowledge Records.
Configuration
On the TENANT page (Admin > Basic> Infrastructure > Tenant > Select a Tenant > Click CONFIGURE DETAILS on the ACTIONS panel > Select KNOWLEDGE MANAGEMENT from MODULES), two new check boxes, Allow Editing for Approver and Allow Editing for Publisher are added. For more information, see Configuring Knowledge Management Module.
Confluence Cloud Migration Alert: Please refer to known issues you may encounter in Confluence Cloud: https://eitdocs.atlassian.net/wiki/x/wDGwAQ