> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/client-profile/groups/notification-settings-for-group.md).

# Notification Settings for Group

Establishes notification rules for the group

This feature allows administrators to set default notification configurations for new users and provides the option to update settings for all existing users.&#x20;

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2F7OWooiKJGXa2HqgdXVWd%2FGroup%20956.png?alt=media&amp;token=f381a636-2a57-4bb3-b2de-f6f61ab0c9c3" alt=""><figcaption></figcaption></figure>

The system provides two delivery methods **In-App and Email** for the following categories:

* **General Notifications:** Notifications for events such as a new user signing up, or someone uploading files or new versions.
* **Collection Notifications:** Alerts when someone adds assets to collections.
* **Task Notifications:** Updates on work status, deadlines, or when you are assigned a new task.
* **Template Approval Notifications:** Notifications regarding the Template Approval process.
* **Approval Notifications:** Notifications for events relevant Approval such as When an asset or asset version has been approved.
* **Consent Notifications:** Alerts when a consent expires, or when a consent request has been approved or rejected.
* **Status Notifications:** Updates when an asset's status changes (e.g., archived, marked as sensitive, etc.).

### How to set up notifications for groups

🔹 **Step 1: Select General Configuration Options**

* **Update Existing Users With These Settings:** By checking this box, all changes you make will be applied immediately to all current active users in the group.
* **Disable users from overriding these settings:** If selected, users will be unable to change their personal notification settings. You will have sole control over these configurations.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FjN2CXFDq26L2Ys1MH1lR%2FGroup%20955.png?alt=media&amp;token=b0206e14-76b4-4577-83b9-dec87274421b" alt=""><figcaption></figcaption></figure>

🔹 **Step 2: Choose Delivery Method**

* Check the corresponding **In-App or Email** column for each event description you wish to trigger a notification.
* **Note: Verify Permissions and Requirements**
  * **Permissions:** Note that some users may not receive a notification if they lack the required permissions for that specific action, even if the notification is enabled.
  * **Email Verification:** To receive email notifications, a user's email address must be verified.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FErmuoYHFfA62EFJrDpAO%2Fimage%2011.png?alt=media&amp;token=8d7a1e40-e8a2-4351-b89b-d8f99cfa5390" alt=""><figcaption></figcaption></figure>

🔹 **Step 3: Save Changes**

* Once configured, these actions will be recorded in the Group History section to ensure full transparency.

If you have any questions, don't hesitate to ask, we're always here to help!


---

# 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://support.hivo.co/client-profile/groups/notification-settings-for-group.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.
