TL;DR: In GLPI, access permissions for assets have traditionally been tied mainly to entities. That works well in clean structures, but in reality, responsibility, ownership, and organizational hierarchy do not always follow the same lines. With GLPI 11, group-based permissions are extended from Tickets to all asset types, and together with the new multi-select group…
Read MoreIn organizations using Confluence Cloud as a knowledge‑base, documentation hub or collaboration platform, you often see pages or spaces created with restrictions (visible only to certain users/groups). In these situations an administrator may need to access content they don’t have permission to view. To address this, Atlassian provides the admin key feature. But like any powerful…
Read MoreA very important, fast-evolving area during the latest NetEye releases has been multi-tenancy. In a system with many tenants, the most complex aspect is probably the proper and orderly management of user permissions. To help administrators in this task, we have introduced the concept of tenant role in NetEye 4.29. The tenant role is a…
Read MoreOne of the features introduced in the 4.15 NetEye release is the Command Orchestrator. The aim of this newly introduced feature module is to allow limited-access NetEye users to execute predefined commands on hosts, without needing full access to the targeted device. Within the Command Orchestrator, the NetEye administrator defines which commands can be executed,…
Read MoreNetEye 4 Log Manager, as already presented in this blog post, allows you to easily manage the collection, navigation, visualization and analysis of large numbers of logs. For many reasons, I as a user may want to limit log access to a subset of users. For example a network administrator should only see the logs…
Read More