Feature Requests

when we onboarded this platform we did not have a good understanding of how we wanted to go about with our naming convention. it is possible to rename "friendly name" however not "system". if we where to get the "system" name how we would prefer it to be, we would have to delete the record and re-add it, with a new name, and while doing so we will loose all historic on the record.please make it possible to rename the "system" field as well - introduce for your own sake a GUID or similar, instead of relying on the system name being hard coded :)with this option, it is possible for us to better clean up our dashboard, as well to view records within each inspector

Can you give us a report of potential duplicate Inspectors? You could make assumptions if they're duplicates & we can say if its true or not but at least we know

Ability to Add Attachments in Notes, to be able to share documents for more visibility.

Would like to see an option to see the total captured changes across ALL Environments in the dasboard just like we have for Alerts and Auto-Discovered Systems.

We would like to have the ability to create custom configuration types using the broad amount of data that the inspectors collect to better advance our MSP Documentation. For example: We could create a custom config type for our RDS Licensed Users and keep a configuration that records all the users in a specific AD group for Microsoft SPLA Licensing Audits.Another example, is my SQL team would like a custom configuration type using the SQL Inspector information to outline the SQL Advanced Parameters for specific servers and have it documented.

It would further secure access to our data. By limiting this we can ensure the integrity of our Liongard portal even if a password is stolen.

Would like to be able to use the system ID to get the dataprint JSON object that the UI has. I believe I can do something to get this data myself since the UI seems to be using some variety of an API route to get the data, but the auth seems to be different from the normal API so getting this route added to the existing API would be great

When a Metric or Actionable Alert is returning or taking action on a list of users, add the ability to scope the list of users by membership in a particular OU.

So I don't feel like a silhouette

We need a top-level permission level for Senior / Tier 3 techs so they can manage our customer environments, but not have access to our MSP account or User management. Global Environment Managers gives too many permissions, but it's not acceptable to have to individually make users Environment Admins of every customer, x however many techs you have.Furthermore, it would be nice to have a permission level for Junior / Tier 1-2 techs that gave them the ability to update equipment or stand up inspectors on customer environments. More than Reader, but less than Admin. An "Operator" level, perhaps?