My agency has left behind POP and IMAP protocols many years ago in favor of OWA and MAPI. Most contemporary (and unfortunately non-free) Service Desks do support native Exchange protocols. It would be amazing if these could be implemented in GLPI.

We use a reduce versión of the GUI for the final user. It´s posibble that dashboard plugin (https://forge.glpi-project.org/projects/dashboard/) come for default into the core for the final user?

I'm using GLPI and the project function for organizing our plan, but everyone who has the project permission can control or modify everything in project.

For more flexible managing, the GLPI provides  more specific permission configuration is a better choice.

Hi!

I would like to propose the addition of a feature that allows users to log in and register to the GLPI system using Azure AD B2C. This integration could significantly streamline the onboarding process for new users.

Benefits:

• Faster User Integration: By enabling Azure AD B2C integration, organizations can quickly onboard new users without the need for manual account creation. This can greatly speed up the process and reduce administrative overhead.

• Domain-Based User Validation: The system could validate new users based on the domain configured in the client’s entity. This ensures that only users from allowed domains can register and log in, enhancing security and control.

• SSO Configuration: This feature would facilitate the configuration of Single Sign-On (SSO) without the need to register an enterprise application for each client tenant. This can simplify the setup and maintenance of SSO across multiple client environments.

Why This Solution is Beneficial:

Current solutions require adding login buttons for each registered enterprise application through which users authenticate into GLPI. This means that every new user must select the button corresponding to their organization, potentially revealing the list of organizations with which we collaborate.

Integrating Azure AD B2C addresses this issue. Users can log in seamlessly using a unified method, without needing to see or select between different organizational buttons. This enhances both security and user experience by keeping organizational details concealed and simplifying the login process.

Implementing this feature would provide a more modern and efficient user management experience within GLPI, aligning with current best practices in identity management.

Marcin

In addition to the top view of the server room, the possibility of seeing a complete row of racks, like the simple view of a rack but with all the storage.

Importing assets directly from Intune (Microsoft Endpoint Manager) would be beneficial. A connector could grab this information via the MS Graph API. Intune has already lots of data about the asset like main user or serial number, hardware type and information like ram, disk etc. thx! 

I have not seen any tickets related to depreciation support. I really enjoy working with GLPI, but one of features that I think would be very useful is the incorporation of depreciation. Many ITSM projects incorporate some sort of straight line depreciation reporting. It looks like this was brought up in 2010 https://forum.glpi-project.org/viewtopic.php?id=21692

This would be a great feature in the Management field with either "Depreciation Rate" or set the rate based on asset type like "Computers - 5 year depreciation"

It would be nice to then pull reports on current assets values. Let me know if I'm missing some configuration, but based on my testing there is only currently Amortization support.

A computer (any type of asset) can be addressed through a unique url, something like http://localhost/glpi-9.2.4/front/computer.form.php?id=4150, where 4150 is the (unique, internal) id of the computer.

I'd like to use a url where the parameter is the inventory number (supposed unique)

It would be great to have possibility to fix a connection resource as default to users... now, first option is internalDB, but we use LDAP, so users have to change it manually (and some of them don't do it...).