This determines whether the service is a web-based application or a local application.

This distinction impacts if Substly tracks and presents usage data; in the case of selecting web-based application, Substly will track and present any relevant usage data, whilst for local application, Substly will not attempt to track usage and thus not present usage data.

​This determines if Substly should calculate and present potential savings for a specific service. Potential savings is based on usage (unused services) in relation to cost.

This allows you to establish Substly’s approach towards determining users’ access and sanctioned usage of a specific service.

When set to 'Unmanaged', Substly establishes connections between the service and users through usage data. Alternatively, when set to 'Managed', you have the ability to define these connections yourself, allowing Substly to identify unsanctioned usage.

Manually defining these connections can be done by following our guide on how to complete a license audit

This determines a threshold for a set number of days a user’s activity should be recorded before displaying in Substly as Shadow IT. The exception for this is when Shadow IT is discovered via Workspace, Entra ID, or Substly-verified tracking URLs, displaying directly upon the detection of usage.

If no usage has been logged for the selected period of time, unsanctioned usage for that user will not be displayed until new activity is detected. The purpose of this feature is to remove unsanctioned usage status if the service is no longer being used.

​The number of days before a service for a user is shown as unused. The purpose of this feature is to provide you the option of determining thresholds for separate services, since some services require regular usage and some irregular.