Limitations related to mapping permissions between BMC applications and BMC Helix Knowledge Management by ComAround

A user's support group in your BMC application is not mapped to any user group created in BMC Helix Knowledge Management by ComAround.

The user cannot search for and view BMC Helix Knowledge Management by ComAround articles in the BMC application. Also, the user cannot open BMC Helix Knowledge Management by ComAround from your BMC application.

Best practice: We recommend that you always map support groups from your BMC application to user groups in BMC Helix Knowledge Management by ComAround to enable your users to search for knowledge articles and open BMC Helix Knowledge Management by ComAround from your BMC application.

No user groups that can be mapped with a user's support group from your BMC application exist in BMC Helix Knowledge Management by ComAround.

The user cannot search for and view BMC Helix Knowledge Management by ComAround articles in the BMC application. Also, the user cannot open BMC Helix Knowledge Management by ComAround from your BMC application.

Best practice: We recommend that you ask your BMC administrator to create user groups in BMC Helix Knowledge Management by ComAround and assign them to folders. Then, you can map the user's support group with the created user group.

A user is not assigned to a support group in your BMC application.

Important: Users are always assigned to companies in your BMC application. You can map the user's company to a user group in BMC Helix Knowledge Management by ComAround. For more information, see Permission-mapping-overview-for-BMC-Helix-Knowledge-Management-by-ComAround.

The user cannot search for and view BMC Helix Knowledge Management by ComAround articles in the BMC application. Also, the user cannot open BMC Helix Knowledge Management by ComAround from your BMC application.

A user has different KCS roles in your BMC application and the respective support groups are mapped from your BMC application to the corresponding user groups in BMC Helix Knowledge Management by ComAround.

The user is granted the highest-permission KCS role out of the assigned ones while opening BMC Helix Knowledge Management by ComAround from your BMC application. And while working with content in BMC Helix Knowledge Management by ComAround.

A BMC Helix Business Workflows user is assigned multiple Innovation Studio (IS) Personas, and these Personas have different KCS roles. The KCS roles are selected as 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 Knowledge Management functional roles selected for multiple IS Personas.

For example, the user is assigned seven IS Personas. Two IS Personas (the Document Manager and Case Business Analyst Personas) have KCS roles defined through the Knowledge Management functional roles. 

The following KCS roles are selected for these Personas:

• Document Manager Persona—The Document Manager role.

  KCS role selected for Document Manager in Knowledge Management functional roles

  

• Case Business Analyst Persona— The Knowledge Contributor, Knowledge Candidate, and Document Manager roles.

  KCS roles selected for Case Business Analyst in 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. 

For more information about how user roles in BMC Helix Business Workflows are mapped to KCS roles in BMC Helix Knowledge Management by ComAround, see Knowledge permissions and roles mapping from BMC Helix Business Workflows to BMC Helix Knowledge Management by ComAround. 

A user doesn't have a KCS role assigned in your BMC application.

The Reader role is assigned to the user in BMC Helix Knowledge Management by ComAround.

A user is assigned the Reader role in BMC Helix Knowledge Management by ComAround.

In BMC Helix ITSM, the user cannot view BMC Helix Knowledge Management by ComAround articles because the user cannot open BMC Helix Knowledge Management by ComAround from BMC Helix ITSM.

In BMC Helix Business Workflows, the user can search for and preview BMC Helix Knowledge Management by ComAround articles in the BMC application. However, the user cannot open BMC Helix Knowledge Management by ComAround from BMC Helix Business Workflows.

A user has unrestricted access to multiple companies. 

Important: Only users with unrestricted knowledge permissions can have the Manager role while opening BMC Helix Knowledge Management by ComAround from your BMC application.

After the companies that a user has unrestricted access to and their support groups are mapped to user groups in BMC Helix Knowledge Management by ComAround, the user is assigned to all user groups from both the company level and the support group level in BMC Helix Knowledge Management by ComAround. For more information, see How unrestricted access works in BMC Helix Knowledge Management by ComAround.

A user doesn't have the highest KCS role in your BMC application. The user's company or support group is mapped from your BMC application to a user group for a higher KCS role in BMC Helix Knowledge Management by ComAround.

The user can search for knowledge articles that the mapped user group with the highest KCS role is entitled to view. However, the user cannot view these articles while opening BMC Helix Knowledge Management by ComAround from your BMC application.

Example: A user with the Candidate role belongs to a company or a support group that is mapped from your BMC application to a user group for the Publisher role in BMC Helix Knowledge Management by ComAround. The user with the Candidate role can search for knowledge articles that are accessible by users with the Publisher role only. However, the user cannot view these articles while opening BMC Helix Knowledge Management by ComAround from your BMC application.