> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/all-applications.md).

# All Applications

* Available from IZ Suite Server **26.3.1** under **`IZ Eye`** → **`All Applications`** .
* The view shows the applications of every application type your roles give you access to, across all organizations and environments

**`All Applications`** is a single grid over every scanned application of a module, regardless of application type. In IZ Eye it combines Mule applications, Exchange APIs, API Manager instances, Azure Logic Apps, Azure API Management, Azure Function Apps, Salesforce Apex and the AWS services (Lambda, CloudFormation, Step Functions, API Gateway, ECS, RDS, Load Balancer, Secrets Manager, CloudFront, DynamoDB, SQS, SNS, EventBridge, CodePipeline, CodeBuild and CodeDeploy) in one list; in IZ Scan it combines all scanned repositories and projects. Use it to find an application without knowing its type, to compare quality gate results across types, or to export a consolidated list.

1. Navigate to **`IZ Eye`** → **`All Applications`** .
2. Each row is one application version (IZ Eye) :

| Column                             | IZ Eye                                                                            | IZ Scan                                           |
| ---------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------- |
| **`Application`**                  | Name of the application                                                           | Name of the repository or project                 |
| **`Version`** / **`Branch / PR`**  | Deployed version                                                                  | Branch or pull request scanned                    |
| **`App Type`**                     | Mule, API, API Instance, Logic App, API Management, Function App, Apex, and so on | Mule, API, Python, C#, Kubernetes, and so on      |
| **`Total Issues`**                 | Issues found by the latest scan                                                   | Issues found by the latest scan                   |
| **`Quality Gate`**                 | Result of the latest scan against the active quality gate                         | Same                                              |
| **`Status`** / **`Code Coverage`** | Runtime status of the application                                                 | Code coverage reported with the scan              |
| **`Created`**                      | When the application was first seen                                               | When the branch or pull request was first scanned |
| **`Last Scan`**                    | Time since the latest scan                                                        | Time since the latest scan                        |

3. Additional columns can be enabled from the column settings in the toolbar: **`Source`**, **`Organization`**, **`Environment`**, **`Scan Scheduled?`**, **`Is Deleted?`**, **`Has Custom Setting?`**, **`Uses Custom Setting?`**, **`Report Default?`** and **`Can Scan?`**.

#### Filters <a href="#filters" id="filters"></a>

* **`Name / Version`** (IZ Eye) or **`Name / Branch / PR`** (IZ Scan) - Inline search on application name, version, branch or pull request.
* **`Organizations`** and, for IZ Eye, **`Environments`**
* **`App Type`**
* **`Quality Gate Status`** - Passed, Failed or Free
* **`Severity`** and **`Category`** - Show applications that have issues of the selected rule severity or category
* **`Rule`** - Show applications that violate the selected rules. Search rules by name, id or tag.
* **`Is Report Default`**

#### Actions <a href="#actions" id="actions"></a>

| Action                    | Description                                                                                                                                                                                                                                       |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **`View Dashboard`**      | Opens the application dashboard for this application. See [Application Dashboard](https://file+.vscode-resource.vscode-cdn.net/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/application-dashboard.md).                          |
| **`View Issues`**         | Opens the issues of the latest scan, grouped by file. Available once the application has been scanned. See [Application Issues](https://file+.vscode-resource.vscode-cdn.net/product-guides/integral-zone/iz-suite/iz-eye/application-issues.md). |
| **`View Previous Scans`** | Opens the scan history of the application.                                                                                                                                                                                                        |

Use **`Download`** in the toolbar to export the current view, and **`Reload`** to refresh it.

<br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/all-applications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.