charleswitherspoon

Hey,

Thanks for the quick response.

Active users would be users who login within at least 90-120 days.

The main user screen would be great at at a glance if it was also possible to sort by that column. Overal an Excel with the values set properly in export would satisfy my request quickly. Wisful adds would be a report under the utilities section which could be scheduled on a frequency of my choosing along with a 30, 60, 90, 180 day metric as far as inactivity.

If we're talking wishful adds, knowing what vaults are most often used in comparison to those that are not woudl also be a good metric to have so unused shared vaults could be removed.

ood morning, Devolutions team,

I’m looking for a way to clean up our Devolutions environment by auditing user activity specifically, identifying users who have not logged in within a defined period (for example, >180 days).

We have the Devolutions Hub module installed, and I’m comfortable working with PowerShell. However, I haven’t been able to find any functions, methods, or properties that expose user login or audit data programmatically, even though this information is visible in the web UI.

Ideally, whether via PowerShell or the GUI, I’d like the ability to:

• Identify the most active users

• Identify users who were onboarded but no longer use the platform (inactive for 180+ days)

• Determine which features users are licensed for

• See when users last logged into the system

• Generate reports based on this data (GUI and/or PowerShell)

In our environment, some users are onboarded to Devolutions for specific projects. Once those projects end, their AD / Entra ID accounts may be disabled, but because licensing is based on directory headcount, those users can still consume a Devolutions license even though they’re no longer actively using the platform.

Being able to correlate licensing with actual usage would be extremely helpful for right sizing our cost.

Hey Michael,

Thanks for the quick. For this use case we would only like to allow specific sources. The use case for my organization right now is only Devolution hub / business. It would be beneficial to toggle on / off other sources though if we're talking about a community standard.

Additional nice to have -

It would be nice to have a migration path if other sources are "disallowed" to migrate the dataset from the disapproved source to the allowed source.

Was recommended to pop a feature request to disallow a specific datasource type.

Would like the ooportunity to only allow devolutions hub / business based datasources to ensure company data is kept on company approved solutions. Hiding the menu is an option, but doesnt allow the appropriate setup without considerable wait.

Would be beneficial to convert the PowerShell cmdlets into a resentful API that could be consumed by secure / Tier 0 servers without installing standard modifications.