Security Masking
With SD 7 Plus beta I have a suggestion relating to masking.
While I appreciate that this is designed primarily as an internal tool, there are times wheren you want to quarantine information from one group of users vs another.
For example if you have a large company with different divisions, and you have proceedures on how to access say local proxy servers or local mail servers etc (in the knowledgebase) it would be good to be able to mask or set some permissions on accessing this content so you could define some content as public and some other based on some form of group membership etc.
Also for other data (eg: reports, etc etc) it would be good to be able to restrict certain users from being able to see data from other departments. You might want to give a manager rights to be able to run some reports for their own departments but they shouldn't be able to see other departmetns in other divisions.
I was thinking if you added a security field whicih you could populate with a table - then you could grant user and groups access to those records tagged wtih that security descriptor. Maybe you had a default descriptor "public" that all users were able to see.
In this way you could better tailor what people can see and when you expose a self service knowledgebase to users, they only see data relating to their department rather than being overwhelmed wtih data not relevant to them or their location.
Also having the ability for technicians to filter various views based on this descriptor would help them further refine what could otherwise be very large lists in some cases....
Any thoughts?
Thanks
While I appreciate that this is designed primarily as an internal tool, there are times wheren you want to quarantine information from one group of users vs another.
For example if you have a large company with different divisions, and you have proceedures on how to access say local proxy servers or local mail servers etc (in the knowledgebase) it would be good to be able to mask or set some permissions on accessing this content so you could define some content as public and some other based on some form of group membership etc.
Also for other data (eg: reports, etc etc) it would be good to be able to restrict certain users from being able to see data from other departments. You might want to give a manager rights to be able to run some reports for their own departments but they shouldn't be able to see other departmetns in other divisions.
I was thinking if you added a security field whicih you could populate with a table - then you could grant user and groups access to those records tagged wtih that security descriptor. Maybe you had a default descriptor "public" that all users were able to see.
In this way you could better tailor what people can see and when you expose a self service knowledgebase to users, they only see data relating to their department rather than being overwhelmed wtih data not relevant to them or their location.
Also having the ability for technicians to filter various views based on this descriptor would help them further refine what could otherwise be very large lists in some cases....
Any thoughts?
Thanks