> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/applications/defining-business-applications/manage-criteria-via-the-tenant-ui.md).

# Manage Criteria via the tenant (UI)

You can view and manage existing configurations in the criteria inventory table: 

* Navigate to **Modules → Application Security → Application Management → Criteria**.

  The criteria table displays all existing criteria with the following information.

| **Property**      | **Description**                                                                      |
| ----------------- | ------------------------------------------------------------------------------------ |
| Name              | The display name of the criteria                                                     |
| Type              | The criteria type: Code (VCS-based) or Cloud (tag-based)                             |
| Application Count | The number of applications generated by the criteria                                 |
| Asset Count       | The total number of assets grouped across all applications generated by the criteria |
| Refresh Status    | The current processing state: In Progress or Done                                    |
| Created By        | The user who created the criteria                                                    |
| Created At        | The timestamp when the criteria was created                                          |

### Supported actions

The criteria table supports the following actions:

* **Create Criteria** : Select **New Criteria** to open the criteria creation wizard
* **Delete**: Remove a criteria and all applications generated by the criteria: select a criteria row, then select **Delete**


---

# 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://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/applications/defining-business-applications/manage-criteria-via-the-tenant-ui.md?ask=<question>&goal=<endgoal>
```

`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.