Has anyone else run into this issue, where Knowledge Blocks do not apply their security settings properly when a User has contribute rights to the knowledge base. I.e. They can view all blocks no matter if they are placed on the can not view list.
If a member of L1 is on the contribute list for the knowledge base they can read the knowledge block even if you specify that you do not want them to see it. Is this a flaw in the knowledge blocks? I attempted the manual ACL of the Knowledge blocks and was still unable to get the results I desired.
Is there a process to setting these up manual in a way that prevents those with contribute access from seeing the knowledge blocks if they are not allowed too? Note L1's require contribute access due to we want them to always be able to create articles even from cases.
Hi LeChara,
This property is overriding contribute access at article level, but we are not using any user criteria at article level we are using at knowledge base level. Do we have any property which can override contribute access at knowledge base level.
