Access levels in a knowledge base

It is natural that different areas of corporate knowledge are accessible to different people. Of course, an intern will have access to different resources than a board member.

Therefore, it's worthwhile to consider this at the design stage of the knowledge base.

If from the very beginning you know that certain data should only be available to specific people, include this in your knowledge base design.

CogniVis Docs allows you to freely manage access to selected shelves, books, chapters, or pages. For example, you can create a "Manager" role that will have access to the entire knowledge base and a "Team Member" role that will have access to all the knowledge except for shelves dedicated to managers.

You can also create a "Board Member" role, which alone will have access, for example, to the "Financial Reports" shelf.

The access management system in CogniVis Docs is very flexible, and you can freely adjust it to your needs.

However, if you are just starting out with building a corporate knowledge base, it is definitely best to focus initially on creating a base with knowledge that is to be available to the entire team. To make this challenging task easier, you can initially forget about restricted knowledge for managers or board members and focus entirely on creating a knowledge base accessible to the entire company.



Michal Szymanski
About author
Michal Szymanski

Co Founder at MDBootstrap , CogniVis AI and AIFor.Biz / Listed in Forbes „30 under 30" / EOer / Open-source and AI enthusiast / Dancer, nerd & bookworm.

Author of hundreds of articles on AI, programming, UI/UX design, business, marketing and productivity. In the past, an educator working with troubled youth in orphanages and correctional facilities.