At the moment, I’m struggling/obstructed to roll-out Guru to other departments because I cannot do it in a scalable way in order to protect sensitive information.
Currently, in my software collection, we have numerous folders and subfolders containing crucial resources such as installation guides, work instructions, and best practices across our software ecosystem. To ensure scalability, it is easier to grant reader access to the entire collection. However, there is a need to restrict certain cards or folders to specific reader groups or software team members. For instance, instructions on setting up a database connection with our ERP system should only be accessible to the relevant team members.
The challenge arises when granting readers access to the entire collection, as it becomes difficult to manage and organize information across multiple departments. As an example, within the HR collection, we want to provide employees with reader-level access to a wealth of knowledge while protecting sensitive information like job descriptions and related salary scales.
To address this, I suggest implementing more granular access controls within Guru. This would allow us to specify access permissions at the card or folder level, ensuring that only authorized individuals or groups can view certain sensitive information. By providing the right level of access to the right people, we can strike a balance between accessibility and data protection.
I believe implementing these access controls will greatly improve the usability and security of our knowledge base, enabling efficient collaboration while safeguarding sensitive information.