Trelica attempts to match apps discovered in your organisation to profiles in our global library of applications. This has the benefit of prefilling all of the basic profile information for you (e.g. the type of application, business vs. home use, web links).
We're constantly monitoring, researching and adding new apps to Trelica's global app library. However, sometimes we're not able to identify an app that a Trelica customer has discovered. In most situations, the only information we will have is the app name and an ID from the Identity Provider - that's not always enough to verify what app is being accessed.
Trelica will 'query' any apps discovered in your account which we're unable to identify. There's a running count of these apps in the Actions section of your dashboard.
There's also a preset filter available in the application list (and in several other places where filters are used).
A common source of unidentified apps is OAuth tokens issued to your users for custom scripts or macros. They often have cryptic names such as 'project-xxxxxxx' or 'Recorded Macro [xxxxx]'. If we're reasonably confident it's a custom script, we will mark it accordingly in your inventory. If the reference is vague the app will be queried and marked as unidentified.
In most situations (most notably for customers using Google Workspace) it's just not practical for you to review all unidentified apps.
The Access Risk associated with an unidentified app can provide useful information by indicating what's been accessed (e.g. permissions for Google Sheets or Drive folders).
If you're able to identify one of these apps, you can use the Resolve option on the application profile and provide more information to help us categorise the app appropriately.