> 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-core/notifications.md).

# Notifications

### Subscription

Users can subscribe to the events listed below through any of the supported channels, such as Email, Slack, or Web.

### License Notification Events

Notifications related to License Modules and Validity

| Event                     | Description                                                               |
| ------------------------- | ------------------------------------------------------------------------- |
| On License Expired        | Event which will be triggered on IZ Suite license expiry.                 |
| On License Quota Exceeded | Event which will be triggered when any of the allotted quota is exceeded. |

### Organization Notification Events

Notifications related to Organization

| Event                                     | Description                                                                                |
| ----------------------------------------- | ------------------------------------------------------------------------------------------ |
| IZ Eye - On Org On Board                  | Event which will be triggered when a new Organization or Business Group is on boarded.     |
| IZ Eye / Scan - On Mule App Scan          | Event which will be triggered when a Mule application is scanned.                          |
| IZ Eye / Scan - On Mule Quality Gate Fail | Event which will be triggered when Quality Gate of a Mule application being scanned fails. |
| IZ Eye / Scan - On API App Scan           | Event which will be triggered when an API application is scanned.                          |
| IZ Eye / Scan - On API Quality Gate Fail  | Event which will be triggered when Quality Gate of an API application being scanned fails. |

### Application Notification Events

Notifications related to Application

| Event                                     | Description                                                                                |
| ----------------------------------------- | ------------------------------------------------------------------------------------------ |
| IZ Eye - On Org On Board                  | Event which will be triggered when a new Organization or Business Group is on- boarded.    |
| IZ Eye / Scan - On Mule App Scan          | Event which will be triggered when a Mule application is scanned.                          |
| IZ Eye / Scan - On Mule Quality Gate Fail | Event which will be triggered when Quality Gate of a Mule application being scanned fails. |
| IZ Eye / Scan - On API App Scan           | Event which will be triggered when an API application is scanned.                          |
| IZ Eye / Scan - On API Quality Gate Fail  | Event which will be triggered when Quality Gate of an API application being scanned fails. |

### See Also

* [Creating an Agent](/product-guides/integral-zone/iz-suite/iz-core/agent/create-agent.md)
* [Updating an Agent](/product-guides/integral-zone/iz-suite/iz-core/agent/update-agent.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 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-core/notifications.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.
