> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/features-new-ui/tools/get-alerts/create-channel/view-configured-channels.md).

# View Configured Channels

View alert channels that have been configured in JFrog Connect.

You can see a list of all the channels that have been configured with information about them.

To see a summary of the channels, in the left navigation tree, go to **Alerts** > **Configuration** **tab** > **Channels**.

<div align="left"><figure><img src="https://1679291640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOX8HIrQ8f257lv49Od1Z%2Fuploads%2FRuAegn402FdwXiu0uLOh%2Fview-configured-channels-01-nui.png?alt=media&amp;token=38eed2a3-3c8e-40f5-9303-71df36793e52" alt=""><figcaption></figcaption></figure></div>

You can view and do the following in the table:

* **ID**: The UUID identifier of the channel.
* **Type**: The type of channel. The icon indicates whether the channel type is email or webhook.
* **Name**: The user given name of the channel.
* **Configuration**: Shows the email address or webhook URL.
* **Trigger Condition**: The circumstance in which an alert will be sent, for example, when the alert is triggered or when the alert has finished.
* **Enabled**: Use the toggle to enable or disable the channel.
* **More**: At the end of each row in the table, hover your mouse and you can see the three dots. Click the three dots to open the menu.
  * **Edit**: Click **Edit** to modify the channel configuration.
  * **Delete**: Click **Delete** to delete the channel from the table.

## What's Next?

Learn how to [create a monitored process](/features-new-ui/tools/get-alerts/create-monitored-process.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://docs.connect.jfrog.io/features-new-ui/tools/get-alerts/create-channel/view-configured-channels.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.