> For the complete documentation index, see [llms.txt](https://docs.a-pay.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.a-pay.one/faq/a-pay-merchant-portal/interface/settings/my-notifications.md).

# My notifications

The **My notifications** table displays all notifications available for your project and allows you to manage them.

<details>

<summary><strong>Table columns</strong></summary>

* **Type** — notification type:
  * *Telegram* — notifications sent to Telegram chats.
  * *Internal* — notifications displayed in the personal account interface.
* **Is group** — indicates whether the Telegram ID belongs to a group.
* **Telegram username** — username or group name in Telegram.
* **Telegram id** — unique ID of the user or group in Telegram.
* **Categories** — notification categories.
* **Enabled** — indicates whether the notification is active.
* **Actions** — available actions for the notification.

</details>

### **Available actions**

* **View connected notifications** — see which notifications are enabled and where they are sent.
* **Enable/Disable a notification**
  1. Click the ⋮ (three vertical dots) icon in the Actions column for the desired notification.
  2. Select **Edit**.
  3. Check/Uncheck the Enabled box and click **Save changes**.\
     ![](/files/fvATBFvnEPfxqNc2Sc9e)
* **Change notification categories**
  1. Click the ⋮ icon in the Actions column.
  2. Select **Edit**.
  3. Update the Categories field.
* **Connect a new notification**
  1. Click **Connect new** in the top-right corner of the page.
  2. Follow the dialog with the bot to complete the connection.
* **Disconnect a notification**
  1. Click the ⋮ icon in the Actions column.
  2. Select **Disconnect** and confirm the action.
  3. The notification will be disabled and will no longer appear in the table.


---

# 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://docs.a-pay.one/faq/a-pay-merchant-portal/interface/settings/my-notifications.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.