Is it OK or not OK to associate more than 1 taxonomy to the Employee Center portal?

[Jacques Clement]

Hi - Listening and reading about Employee Center, I repeatedly heard that one can NOT associate more than 1 taxonomy to Employee Center.

However, in the Employee Center Portal configuration, I can see that this piece of configuration is modeled via a Related List. So my question is twofold:

1. Why not using a simple reference field if only one taxonomy is supported?
2. If the above is confirmed, why even managing multiple taxonomies? I am struggling to understand the use case.

Thanks in advance.

[Jacques Clement]

Thanks both for taking the time. I am still puzzled by this design though. If Employee Center is meant to become an Enterprise Service Portal supporting multiple departments, then IMHO it would make sense to have one taxonomy for each department.

If only one taxonomy is supported, then... it's the taxonomy of the whole enterprise and no need for a list of taxonomies. I understand we can have multiple levels of child topics but I still think there's something off from a data model standpoint.

Or I may just miss the point.

Thanks again.

[Community Alums]

Hi @Jacques Clement ,

If you want to see any enhancements or changes to be see on the product, feel free to raise a IDEA from here :https://community.servicenow.com/community?id=ideas_list&sysparm_module_id=enhancement_requests

Kindly mark the applicable answer as Correct & Helpful both such that others can get help.

Thanks,
Sandeep

[Community Alums]

This!  100% this!   If you can only implement security at the taxonomy level, and there can only be one taxonomy, then HR folks can mess with IT topics/content and vice versa.  Supporting multiple taxonomies would go miles to make this thing work as customers need it to.

[Sharad S]

Hi Jacques,

The best approach is to keep OOB taxonomy as is and clone the Employee taxonomy. Also even if you created multiple taxonomies, the system won't allow you to associate more than one taxonomy at the same time. 

 Even if EC becomes an enterprise portal, you still have the option to add the main topics map to a specific sub-department or BU. For ex, the main taxonomy related to your org, then underneath topic like IT, HR, Facilities etc become main topics and then you can again add sub-topics as required. Security-wise existing platform level criteria or roles will decide what user can or can't see!

As per my recent EC implementation experience so far don't see any major challenge with this model. 

Please mark as correct answer or helpful if the provided response resolved your query!