Restrict access to taxonomy topics

[Filip Sroczy_sk]

Hello, 

I'd like to know how to implement content restriction in taxonomy Employee Center. I want to restrict one of the child topics of the taxonomy, so for example when I enter HR from "Mega Menu" some subtopics should be visible only for managers.

How do I do that?

[Rob Sestito]

Hey @Kannickal -

You would (you could) start from the Record Producer record level. So if you have a record producer for your "tuition/subsidy" service, you would go there. Then on the form towards the bottom, you have the related list tabs, and you should have Available For & Not Available for (if they are not there you can add them):

If you click Edit button on the right, then you are taken to your list of already created criteria. And you can add in the criteria based on your requirements for which employees should see the tuition service. If you do not have the proper criteria built out yet, then you can click on New to create some.

Here is Edit:

Here is New (takes you to your form to create new user criteria):

Does this help you out?

Let me know!

Thanks,

-Rob

[Kannickal]

Hi Rob,

Thanks very much for this quick reply. I do agree and understand the setting at record producer level. What if we need to totally hide, for example "HR General" from mega menu based on user or hr criteria? Is that possible? Thanks again for your valuable time.

Thanks/k

[Rob Sestito]

Hey K - 
When you say totally hide. Does that mean that the service, in this example let's stick with "HR General", needs to be hidden from everyone and not be used?

Overall however, if you need a service to be completely hidden from the mega menu, you could just disconnect it from the taxonomy as an item. But, the service will still remain as searchable within the employee center.

But if you want to hide the service from certain employees using hr / user criteria. I would then add a criteria that points to that particular group, and add it to the Not Available For tab from the record producer.

Otherwise, back to the first option. You would always disconnect an item from the taxonomy which removes it as a mega menu / topic item. But will still be searchable through the employee center to have the user land on the record producer to use that service.

If I look at your question a bit differently; If you have already tried adding user / hr criteria to a record producer and it is STILL showing in the mega menu for employees that should not see it, then you may have a cache issue. I ran into this issue a lot when dealing with the taxonomy and the mega menu. I would make changes and it would not show the changes on the employee center until after I ran a cache.do. So, if you are running into that scenario where you added criteria but still do not see the changes, try clearing the cache in your instance.

Does that make sense?

Let me know - and let me know if you have more questions regarding this. I want to make sure I am following your question(s) correctly.

Thank you,

-Rob

[Kannickal]

Hi Rob,

Thanks so much for your the time you took here to explain the various scenarios. 

I was asking in your example of mega menu, can we he control the access say by hiding the "topic - HR General"? My understanding here is for HR General there is no record producer as its simply a topic.  In other words, we want to have the HR General topic and sub-topics displayed based on a specific User/HR Criteria (say only available for HR agents) and rest of the users this will be hidden. Hope my question is clear and thanks again for your feedback.

Thanks/kannickal

[Rob Sestito]

Hey - 

If in your system 'HR General' in fact has no record producer involved. You can try creating a read ACL based on role(s) within the Topic table. I have not done/tried it this way, so I am not totally sure it will work.

If from your example to have HR General for HR Agents only is true, then you can simply just disconnect that HR General topic from the taxonomy, and your agents can just utilize the service from platform view (since hr agents normally live in the backend platform or Agent Workspace and not the employee center).

I did stumble upon this post: Ability to hide 3rd level categories from Mega Menu? 

It is close I think to what you and I are discussing here. Maybe this post can help also to achieve this in another way. I see they are using script/css to hide things from the mega menu. I know it says the 3rd level, but it may help.

Thanks,

-Rob