> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/modules/discover/app-catalog.md). # App Catalog The App Catalog is where every application Discover has spotted — and how it's classified — lives. It's the source of truth that feeds [Application Usage](/modules/discover/application-usage.md) and [Discover Compliance](/modules/discover/discover-compliance.md). ## Discovered apps vs. the master list By default, the App Catalog shows the applications **discovered** for the tenant you're viewing (or for **All Companies**). Use the toggle at the top right to switch to the **Master List**, which shows Augmentt's full preset catalog of apps and their default classifications — useful when you want to see how an app is classified before it's ever shown up in a customer's traffic. You can search either list by application name or URL. ## The catalog list Discovered applications are listed with: | Column | Description | | ---------------- | --------------------------------------------------------- | | Application Name | The app | | Category | Its classification (e.g. Productivity, AI, Collaboration) | | Approval Status | Approved / Restricted / Pending Review | | Risk | Low / Medium / High | | Productivity | Low / Medium / High | ## Total Web Traffic — unclassified apps Any traffic Discover has picked up that hasn't yet been matched to a known catalog entry shows up in the **Total Web Traffic** section below the main list, with: * URL * Visit count * Last visited date Use the **+ (Add SaaS Application)** button on an entry here to promote it into the catalog so it starts appearing in Application Usage reporting. Until you do this, that traffic is visible but won't be reflected as a tracked "application" elsewhere in Discover. {% hint style="info" %} Traffic sitting in Total Web Traffic and never getting classified is one of the most common reasons an app a customer clearly uses (per their own systems) doesn't show up in their Application Usage report. If a partner says "we know they use X but it's not showing," check here first. {% endhint %} ## Editing classification: per-tenant vs. all companies Every catalog entry can be edited for the single tenant you're viewing, or globally for **All Companies** — switch the company selector before clicking Edit. Editing at the All Companies level saves you from having to reclassify the same app for every client individually. {% hint style="warning" %} Field reports show two rough edges here worth flagging to a partner before they rely on this workflow: (1) the Edit screen's Category dropdown has, in some cases, shown no selectable options, effectively blocking a category change; and (2) a classification set under "All Companies" hasn't always been observed to propagate down and stick on individual company records. Neither behavior is expected — if you hit either, report it to Augmentt support with a screenshot rather than assuming you're missing a step. {% endhint %} ## Handling multiple URLs for one app Some SaaS products are reachable through more than one domain (a common example: a chat/AI product's authentication domain differing from its main app domain). If you manually add an app from Total Web Traffic under one URL and the same product later shows up again under a different URL, you can end up with duplicate-looking entries for what's really one product. {% hint style="warning" %} There isn't a confirmed self-serve way to merge two catalog entries or attach multiple URLs to a single existing app record — some partners have found the "Edit URL" option greyed out once an entry exists. If you hit this, treat it as a support question rather than assuming there's a hidden setting; don't guess at a workaround that might create further duplicates. {% endhint %} ## Unclassifiable or ambiguous traffic Occasionally a URL shows up in Total Web Traffic that doesn't correspond to anything a user would recognize as "an app they visited" — for example, an authentication or API domain used behind the scenes by another integrated service. Augmentt won't always have more detail on what's calling that URL; if a partner needs to track it down, they'll typically need to correlate it with what other tools/integrations are configured for that user or company. ## What's next * Report on usage across the catalog in [Application Usage](/modules/discover/application-usage.md) * Check compliance posture (SSO, MFA, breach history, regulatory frameworks) per app in [Discover Compliance](/modules/discover/discover-compliance.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://helpdesk.augmentt.com/modules/discover/app-catalog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.