Application status
An explanation of each of the statuses you can assign to an application in your Trelica inventory.

What is an application status and why is it important?

Every app in your Trelica inventory has an associated status - it’s clearly displayed in the inventory list view and on each app profile.
Statuses help you:
  • organise your inventory into sensible groupings, as not all apps you discover need the same kind of attention
  • track the lifecycle of the key apps you want to actively manage i.e. from onboarding through to end of life
You will see 'status' as an option in reports and filters.

Status definitions

The default status for all discovered apps is ‘new’. The ‘managed’ status should be assigned to apps that you want to actively manage in terms of assigning business owners, tracking license information and renewals etc. As it's very unlikely that you will want to actively manage all of the apps you discover, there is a range of additional statuses between ‘new’ and ‘managed’ to account for different outcomes as you review apps.
New - default state for all newly discovered or manually added apps.

Transition states

Transition states are optional - apps can be moved straight from ‘new’ to any of the end states
In review - app is in review, either as part of initial onboarding or post-discovery when verifying if the app should be part of your inventory, or closed out.
Plan to close - app usage is due to be discontinued, either as part of an offboarding process or post-discovery if access is going to be blocked. This transition state accounts for situations where apps can’t be moved straight to ‘closed’ given practicalities around steps to engage with users or the vendor.

End states

Managed - app is key to your business and should be actively managed.
Managed apps have a special meaning in Trelica and the system will flag any information gaps for an app in this state e.g. missing business owner, expired/no license, integration not enabled
Accepted - you don’t have concerns about the app being used given the current level of usage, spend, or risk. However, you don’t need to formally manage the app (i.e. assign a business owner, capture license details, track renewals etc).
Closed - use of the app is discontinued. This state archives the information you’ve collected, but apps in this state are hidden by default in all inventory views.
Ignored - app is miscellaneous and doesn't require attention in terms of spend, licensing, user engagement or risk. Ignored apps are hidden by default in all inventory views. Typical examples would be one-off custom scripts that are picked up in discovery.
Copy link
Outline
What is an application status and why is it important?
Status definitions
Transition states
End states