Is there any way to associate Categories with specific User Roles (i.e. restrict access based on rol

Archived Ruslan H. ● ago

I would like to control the access to specific categories. Ideally, I would like to see a checkbox for each category that I create on the "Edit Role" screen. That way I can create User Groups that will only have access to specific categories. Is this currently possible?

Replies (4)

Stas K. ●

Hello Ruslan,

Currently it's not possible to distribute visibility permissions of categories per role, nor it's planned.

Though, you can use built-in private or public categories and set visibility permissions to roles.

Ruslan H. ●

I used that and I have two categories - one public and one private (with corresponding User Roles), but I would like to have more categories and roles.

Given that this is not planned, is it possible to write a custom module to that adds this feature? If it is, how would one go about doing this? Also, is there a list of features/changes in 3.0; will 2.0 custom modules be compatible in 3.0?

Stas K. ●

The list of core features in 3.0 is available in our official announcement.

As per custom module.. We can write it for you for 2.3.x release, but this module won't work when you migrate to 3.x as we've changed system completely including core. This is the most significant release since 1.0.

Maurice B. ●

This is exactly the feature we would need in order for us to be able to use Useresponse. The issue we face is that we want to use the system for 3 specific target groups: the general public, account holders and internal. We have specific knowledge for our internal organisation (for that we are able to use the private option). For account holders we have specific knowledge that must not be publicly available. It would be great to be able to set specific user roles to knowledge base categories. What I would like to be able to do is to specify visibility for specific user roles as part of the category settings. As in the provided screenshot.

Is it possible for you to add such a feature?
In case this is not a possibility: How much work would it be to add this as a module/feature ourself?
How did Ruslan solve this?

Files:

Stas K. ●

We still don't have plans to integrate new layer of visibility. The only solution here will be using 2 versions of system on 2 different locations.

This would be more convenient and cost effective, as development of new layer with selecting visibility for specific roles will take much time and would be 2-3 times more expensive than development of custom module for that.

Also, we can build module for you that will limit access to specific users that have license or whatever parameter you want to consider to restrict visibility, but it would be applied to the whole Knowledge Base, but not specific articles. So we can apply it to the whole module if it will work for you. That way, in custom module, we need to connect to your database where you store account holders and check if this user is an account holder so that when he is logged in, he will see and use Knowledge Base. That way Knowledge Base will be seen to all support agents and those users that have account in your db to make it dynamic.

I've sent you estimation on this custom module.