Feature Requests

For example, if we want to exclude certain mailboxes from the mailQuotaExceeded_r metric, the recommendation was to add the account to a security group and do something like: Users[?mailQuotaExceeded_r == true && !contains(MemberOfStr, RoarExclude )] However, this means creating the group for all customer environments, and creating separate exclusion groups per metric/rule. Is there a way to do this from LionGard itself?

Currently, when SSO enforcement is enabled in Liongard, users can still access the standard login screen and enter their username and password. Although authentication is ultimately redirected to the Identity Provider (IdP) — confirming that SSO enforcement is functioning correctly — this workflow creates a misleading user experience. Users perceive that their credentials are being used for authentication, even though the process is actually verified via SSO. This can cause confusion and concern, particularly for partners with strict security policies requiring exclusive SSO access. Proposed Enhancement: Modify the login UX to detect when SSO enforcement is enabled. When a user attempts to log in manually (via username and password) under enforced SSO, display a clear message or redirect that explains: “This account is configured for Single Sign-On. Please sign in via your Identity Provider.” Optionally, disable the manual credential fields entirely when SSO enforcement is active to prevent any confusion. Business Value / Impact: Increases transparency and trust for security. Prevents confusion or misinterpretation of the login process. Aligns the UX with expected authentication behavior and security standards.

Pull data about threats blocked, Threat Category, Threat Score, and Sessions for use in Visual Insights

Would be extremely helpful to allow access for reports/report templates created in the GUI via the API.

This is an alternative DNS tool to Umbrella used by many MSP. Please add an inspector for this product. Thanks!

Liongard already gives good information on M365 licensing but it would be helpful to also have the dates each license type expires and through what purchase channel it was purchased.

We have groups and mailboxes, but there's not a clean way identify which mailboxes are shared. They typically don't have a license applied and thus do not have a quota. It would be good to add Members that can access the shared mailbox as well. (Per Karl Bickmore)Can a type and members column be added to the Mailboxes table?

Capture and allow alerting on changes to mailbox access permissions to allow monitoring of unauthorized backend access.

Have Fortimanager run as a parent inspector to discover all other Fortinet products