> For the complete documentation index, see [llms.txt](https://help.hippoly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hippoly.com/using-hippoly/notifications/notification-types.md).

# Notification types

<table data-header-hidden data-full-width="false"><thead><tr><th width="319">Notification type</th><th width="213">Sent to</th><th width="115">Urgency</th><th>Delivery</th></tr></thead><tbody><tr><td><strong>Notification type</strong></td><td><strong>Sent to</strong></td><td><strong>Urgency</strong></td><td><strong>Delivery</strong></td></tr><tr><td>Invitation to workspace</td><td>Invited user</td><td>High</td><td>A P M</td></tr><tr><td>Meeting shared</td><td>Meeting participants</td><td>Normal</td><td>A P</td></tr><tr><td>Meeting invitation</td><td>Meeting participants</td><td>Normal</td><td>A P M</td></tr><tr><td>Meeting agenda shared</td><td>Meeting participants</td><td>Normal</td><td>A P M</td></tr><tr><td>Meeting agenda updated</td><td>Meeting participants</td><td>Normal</td><td>A P M</td></tr><tr><td>Meeting minuets shared</td><td>Meeting participants</td><td>Normal</td><td>A P </td></tr><tr><td>Meeting minutes review started</td><td>Minutes reviewers</td><td>High</td><td>A P M</td></tr><tr><td>Meeting minutes review comment added</td><td>Meeting secretary and reviewers</td><td>Normal</td><td>A P</td></tr><tr><td>Meeting minutes review comment resolved</td><td>Meeting secretary and reviewers</td><td>Normal</td><td>A P</td></tr><tr><td>Meeting minutes reviewer has completed review</td><td>Meeting secretary and other reviewers</td><td>Normal</td><td>A P M</td></tr><tr><td>Meeting minutes signed</td><td>Meeting participants</td><td>Normal</td><td>A P M</td></tr><tr><td>New Direct Message</td><td>Receiver(s) of message</td><td>High</td><td>A P M*</td></tr><tr><td>New post</td><td>All workspace members</td><td>Normal</td><td>A P M*</td></tr><tr><td>New comment on your post</td><td>Author of the post</td><td>Normal</td><td>A P M*</td></tr><tr><td>New comment on post</td><td>All workspace members</td><td>Normal</td><td>A P M*</td></tr><tr><td>File signing completed</td><td>Initiator of the signing and signatories</td><td>Normal</td><td>A P</td></tr><tr><td>File signing rejected</td><td>Initiator of the signing</td><td>High</td><td>A P</td></tr><tr><td>Action assigned</td><td>Assigned user</td><td>Normal</td><td>A P</td></tr><tr><td>Action completed by someone else</td><td>Assigned user</td><td>Normal</td><td>A P</td></tr><tr><td>Action due today</td><td>Assigned user</td><td>High</td><td>A P</td></tr><tr><td>Action over due</td><td>Assigned user</td><td>High</td><td>A P</td></tr></tbody></table>

*Delivery methods: A = In app, P = Push on mobile, M = Mail,  M\* = Mail notification is sent after 5 minutes if user has not viewed/read the message from where the notification origin from.*&#x20;


---

# 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://help.hippoly.com/using-hippoly/notifications/notification-types.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.