Knowledge permissions and roles mapping from BMC Helix Business Workflows to BMC Helix Knowledge Management by ComAround
How knowledge permissions are mapped from BMC Helix Business Workflows to BMC Helix Knowledge Management by ComAround
The following image shows how knowledge permissions are mapped from BMC Helix Business Workflows to BMC Helix Knowledge Management by ComAround:
- Companies from BMC Helix Business Workflows are mapped to a single portal in BMC Helix Knowledge Management by ComAround.
- Knowledge permissions in BMC Helix Business Workflows are assigned for a knowledge set. Knowledge sets are defined for companies, lines of business and support groups.
- Knowledge articles from BMC Helix Business Workflows Knowledge Management are imported into folders in BMC Helix Knowledge Management by ComAround based on the knowledge set permissions in BMC Helix Business Workflows.
Folders are created in BMC Helix Knowledge Management by ComAround for each combination of a line of business with a knowledge set assigned to a knowledge article in BMC Helix Business Workflows. - User groups are assigned to the portal and folders in BMC Helix Knowledge Management by ComAround, not to each knowledge article.
- Support groups in BMC Helix Business Workflows are mapped to BMC Helix Knowledge Management by ComAround user groups.
This mapping enables users to access articles that reside in the BMC Helix Knowledge Management by ComAround portal and folders based on the user group assignment in BMC Helix Knowledge Management by ComAround. - KCS roles are assigned per user group in BMC Helix Knowledge Management by ComAround. Users from BMC Helix Business Workflows are assigned to specific BMC Helix Knowledge Management by ComAround user groups that match their highest-level KCS role in BMC Helix Business Workflows. For more information about how BMC Helix Knowledge Management by ComAround determines the user's highest-level KCS role, see How KCS roles are defined for BMC Helix Business Workflows users.
Apex Global has categorized its financial knowledge articles into the following knowledge sets: Apex Global (general for the company), Accounts, and Benefits. The use of knowledge articles in the Accounts and Benefits knowledge sets is limited to specific user groups. The knowledge publisher in this company has the following permissions in BMC Helix Business Workflows to create and publish articles:
- Accounts support group
- Benefits support group
- Apex Global company
As an administrator of Apex Global, you want to make sure that the knowledge publisher continues to have access to articles for Apex Global (general for the company), Accounts, and Benefits categories after mapping the permissions. The following image shows the permissions assigned to the knowledge publisher after mapping them with BMC Helix Knowledge Management by ComAround:
- Apex Global Publisher user group
- Apex Global Accounts Publisher user group
- Apex Global Benefits Publisher user group
How KCS roles are defined for BMC Helix Business Workflows users
To grant a KCS role to a user, administrators assign to the user a specific IS Persona that is defined for the com.bmc.dsm.knowledge application. For more information about IS Personas and how to assign them to users, see Functional-role-overview and Creating-and-assigning-functional-roles.
BMC Helix Knowledge Management by ComAround determines the user's KCS role not only by the IS Persona defined for the com.bmc.dsm.knowledge application but also by other assigned IS Personas that depend on the KCS roles. The KCS roles for IS Personas are selected under the Knowledge Management functional roles in BMC Helix Innovation Studio > Administration > Server settings > Application permissions > Functional roles. BMC Helix Knowledge Management by ComAround identifies the user's role as the highest-level permission role out of all selected roles.
The user is assigned seven IS Personas. Two IS Personas determine the user's KCS role—the Document Manager and Case Business Analyst. The Document Manager Persona is defined for the com.bmc.dsm.knowledge application, and the Case Business Analyst Persona depends on the KCS roles.
The following KCS roles are selected for these Personas:
Document Manager Persona—The Document Manager role.
KCS role selected for Document Manager under Knowledge Management functional roles
Case Business Analyst Persona— The Knowledge Contributor, Knowledge Candidate, and Document Manager roles.
KCS roles selected for Case Business Analyst under Knowledge Management functional roles
The user's role is identified as Knowledge Contributor because it is the highest-level permission role out of all the ones selected.
How KCS user roles in BMC Helix Business Workflows are mapped to KCS roles in BMC Helix Knowledge Management by ComAround
The following image shows how KCS user roles in BMC Helix Business Workflows are mapped to KCS roles in BMC Helix Knowledge Management by ComAround:
