> For the complete documentation index, see [llms.txt](https://docs.meeds.io/meeds-guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meeds.io/meeds-guides/admin-guide/setting-up-meeds/set-up-your-hub/notifications-settings.md).

# Notifications Settings

{% hint style="info" %}
This page applies to the **Business** and **Enterprise** plans.  [👉 Compare all plans](https://www.meeds.io/pricing)
{% endhint %}

### Specify the sender of notifications 

* From the administration site, go to the notification configuration
* Then, modify the sender's identity for notifications 
* You can change both the name and the address 

:warning: *Ensure to keep the same domain name in the email address suffix* 

### Allow notification channels 

You can allow or disallow the use of notifications for each channel. 

* Email notification 
* On-site notification 
* Notification for unread activity 

:bulb: For example, if you allow the use of email notifications, the user can choose to disable it if necessary. 

### Identify notifications by type, accessible to users 

* From the notification configuration 
* Specify for each notification type whether the user can activate or deactivate a particular notification channel 
* If you do not want to allow notifications at all for a type, you can disable the available channels. Then, this notification will not be offered to users. 

:bulb: Just like notification channels, each user can then [disable notifications at their convenience](/meeds-guides/user-guide/exploring-a-meeds-hub/navigating/updating-your-notifications.md) or specify the channel to use.


---

# 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.meeds.io/meeds-guides/admin-guide/setting-up-meeds/set-up-your-hub/notifications-settings.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.