Knowledge permissions and roles mapping from BMC Helix ITSM to BMC Helix Knowledge Management by ComAround
How knowledge permissions are mapped from
to
The following image shows how knowledge permissions are mapped from
to
:
- Companies from
are mapped to a single portal in
. If a global company access is required, companies are also mapped to folders.
- Knowledge permissions in
are set by assignment groups and one or more additional visibility groups, if necessary.
- Knowledge articles from
are imported into folders in
based on the knowledge access permissions in
.
Folders are created infor each combination of a company with assignment groups or visibility groups, or both.
- User groups are assigned to the portal and folders in
, not to each knowledge article.
- Assignment groups and visibility groups in
are mapped to
user groups.
This mapping enables users to access articles that reside in theportal and folders based on the user group assignment in
.
- KCS roles are assigned per user group in
. Users from
are assigned to specific
user groups that match their highest-level KCS role in
. Learn how
determines a user's highest-level KCS role in Permission-mapping-overview-for-BMC-Helix-Knowledge-Management-by-ComAround.
How user roles in
are mapped to KCS roles in
The following image shows how user roles in are mapped to KCS roles in :
The following roles are legacy knowledge worker roles that aren't KCS certified. Therefore, they are mapped to the Candidate role in .
Legacy knowledge worker roles in | KCS roles in |
---|---|
Knowledge Admin | Candidate |
Knowledge Config | Candidate |
Knowledge Submitter | Candidate |
Knowledge User | Candidate |
To be mapped with advanced KCS roles in , these roles must be certified by KCS first.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*