K1000 Knowledge Base - User Console vs Administrator UI and Label Restrictions
Hi All-
We're exploring the K1000 Knowledge Base as an option for our internal help desk and administrator teams to allow them to create and share documentation on work flow processes. We've setup multiple labels for access restrictions; Service Desk, Networking, Infrastructure...etc...etc. We restrict who can access what due to some of the KBs having sensitive information in them and not being needed to be viewed by everyone. We noticed that when a user logs in to the Admin UI (https://kbox/admin), that the label restrictions don't seem to matter and they can view/edit any KBs regardless of the restrictions.
If they access it via the User console (https://kbox) then the label restrictions appear to function as intended but I've noticed that it's Read-Only. The users can't make any type of editing changes unless they are logged in to the Admin UI.
Is this a bug in the software or is this functional design? We're currently running 7.1 on our SMA.
Thank you.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
Nico_K
6 years ago
Users usually should only read the Knowledge Base. The admins should write them.
You can restrict the access to the adminui/ so they only can work with the service desk as they should (and don't see anything else)
userui/ is only for the pure user
You can restrict the access to the adminui/ so they only can work with the service desk as they should (and don't see anything else)
userui/ is only for the pure user
Comments:
-
I agree with the point about the /userui being used for pure users. It still is questionable to me regarding users being logged into the /adminui but being able to bypass all other label restrictions though. If I have an admin KB restricted to only my admin label, I'm not sure why a user (not in that label) would be able to still get to it. It makes separating out privileges to edit KBs for non-admin users very difficult - dtobias_keenan 6 years ago
