> For the complete documentation index, see [llms.txt](https://digitals-private-organization.gitbook.io/rizones45678.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digitals-private-organization.gitbook.io/rizones45678.org/web-portal-guide/communication.md).

# Communication

Announcements, events, newsletters, documents, greetings, web links, sub-groups and mass email.

Announcements, events, newsletters, documents, greetings, web links, sub-groups and mass email, all in one tab strip.

> **Screenshot slot:** the Communication tab strip, showing the Upcoming Events list.

## Events, Announcements, Newsletters, Documents and Web Links

These five all follow an identical Add, Edit and Delete pattern.

{% stepper %}
{% step %}

### Open Communication and pick the tab

Upcoming Events, Announcements, Newsletters, Documents or Web Links.
{% endstep %}

{% step %}

### Click + Add

{% endstep %}

{% step %}

### Fill in the required fields

**Title \*** is always required. The rest depends on the tab, see the table below.
{% endstep %}

{% step %}

### Set the Publish Date and Expiry Date

Where shown.
{% endstep %}

{% step %}

### Save

{% endstep %}
{% endstepper %}

| Tab                 | Also needs                                           |
| ------------------- | ---------------------------------------------------- |
| **Upcoming Events** | Date, Time, Location                                 |
| **Announcements**   | Description, and whether to alert members            |
| **Newsletters**     | A file or a link                                     |
| **Documents**       | A file, plus Access Type (View Only or Downloadable) |
| **Web Links**       | A URL, a YouTube link, or a PDF                      |

**Edit or delete:** use the three dots (⋮) menu on the entry's row.

> **Screenshot slot:** the Add Announcement form.

## Greetings

{% stepper %}
{% step %}

### Go to Communication, then Greetings

{% endstep %}

{% step %}

### Toggle the greetings on

**Enable Birthday Greeting** and **Enable Anniversary Greeting**.
{% endstep %}

{% step %}

### Edit the Subject and Message

For each one.
{% endstep %}
{% endstepper %}

Changes save immediately. Toggle off at any time to stop sending.

## Sub Groups

**Add:** go to **Communication**, then **Subgroups**, click **+ Add**, name the group, select its members, then **Save**.

**Edit or delete:** change the membership or delete the group from its menu.

## Mass Email

The send history, with delivery status per recipient.

> **Screenshot slot:** the Mass Email page, showing send history with delivery status.

{% stepper %}
{% step %}

### Go to Communication, then Mass Email

{% endstep %}

{% step %}

### Click + New Email

{% endstep %}

{% step %}

### Fill in the email

From Name **\***, Subject **\***, Email Body **\***, and choose Recipients: All Members, Select Members, or a Subgroup.
{% endstep %}

{% step %}

### Send

It appears in the list above with **Sent** or **Failed** status per recipient.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
There is no editing a sent email. Compose a new one each time. Mass Email draws on your club's **Wallet** email credits.
{% endhint %}


---

# 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://digitals-private-organization.gitbook.io/rizones45678.org/web-portal-guide/communication.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.