...
To view the table in full, please expand it and scroll using the scroll bar at the bottom of the table: Notifications for attendees
Notification | What triggers the notification and when is it triggered? e.g. (a setting or by the system) | What happens after receiving the notification? |
---|---|---|
A user is notified that they’ve been added to an event: You have been added to %{event_name}. It takes place on %{event_date} at %{event_time}. If the user has a registered email address, they also receive a matching email in their inbox: | This notification is triggered if an a user is added to an event in the admin screen for the event: This notification is also triggered if a user registers by clicking the Register button on the homepage for the event without needing approval to attend and there are enough spaces available: | The user is added to the event as an attendee. |
An attendee is notified that an event is happening in a set amount of time: %{event_name}' is happening in %{amount_of_time} | This notification is triggered if the event creator selects the following options in the Notifications section when configuring the event:
| The user is notified that the event is due to take place. |
A user has been removed from the event and is no longer an attendee: If the user has a registered email address, they also receive a matching email in their inbox: | An event admin has removed the user from the event by clicking the Remove user button in the Applicants tab on the admin screen for the event. | The user is removed from the event and is no longer a registered attendee. |
The user has been added to the waitlist for an event that is currently full to capacity: You have been added to %{event_name} waitlist. We'll notify you if you get added to the event If the user has a registered email address, they also receive a matching email in their inbox: | This notification is triggered if the user has applied to attend an event that is currently full to capacity (reached the maximum number of attendees). If an event has a limited number of spaces and the maximum capacity is reached, the user can opt to join the waitlist by clicking Join waitlist on the homepage of the event. If a space becomes free and the user is at the top of the waitlist, they may be automatically added as an attendee, or if they must be approved and added manually, they will need to wait to be added by an approver, their manager, the event creator, or an event admin, depending on the configuration. | The user must wait until a space becomes available, for example, a current attendee is removed from the event or an attendee withdraws from the event themselves. The user on the waitlist is either manually added to the event by an event admin, or they are added automatically by the system if a space is freed up and they are at the top of the waitlist. |
Details of the event have been updated: This event has been updated: %{event_name} If the user has a registered email address, they also receive a matching email in their inbox: | This notification is triggered if a change is made to an event occurrence, including when the time, date or location of the event has been altered by an event admin. | All registered attendees receive a notification stating that the event has been updated. The user can then click the link to the event in the notification and check event for any changes. |
The user is moved from the waitlist to the attendees list: Congratulations! You're no longer on the waitlist for %{event_name}, you're attending the event! If the user has a registered email address, they also receive a matching email in their inbox: | The following settings can trigger this notification, depending on how the event settings are configured:
| The user is moved from the waitlist and added to the event as an attendee. |
An event is shared with a user or a user is invited to an event by an event admin: | This notification is triggered if an event admin:
| The user is notified and receives a link to the event in they notification. If they click the link, they are taken to the landing page for the event where they can register to attend. |
A message is sent by an event admin to all attendees: User %{initiator_name} sent you a message regarding participation request for %{event}: %{request_subject} %{request_message} If the user has a registered email address, they also receive a matching email in their inbox: | This notification is triggered if an event admin clicks the Notify users button in the Applicants tab of the admin screen for the event, and then enters a message and clicks Notify. | All registered attendees receive a notification containing the message from the event admin. |
A specific attendee receives a personal message from an event admin: User %{initiator_name} sent you a message regarding participation request for %{event}: %{request_subject} %{request_message} If the user has a registered email address, they also receive a matching email in their inbox: | This notification is triggered if the an event admin clicks the Notify bell next to a specific user in the Applicants tab on the admins screen for the event, and then enters a message and clicks Notify. | All specified attendees receive a notification containing the message from the event admin. |
A user’s manager has added them to an event: %{manager_name} has added you to the waitlist for %{event_name} If the user has a registered email address, they also receive a matching email in their inbox, which includes the optional message to the reportee from the manager: | The user’s manager clicks the Add reporttees button on the homepage for the event, selects their reportee, and clicks Add: | The reportee is added to the event as an attendee. |
The user’s application to attend an event has been declined: %{participant} has applied for the event %{event} If the user has a registered email address, they also receive a matching email in their inbox: | During the creation and configuration of the event, the creator has specified that applicants must be approved by a manager, specified approver, or event creator, or all three, before they can attend the event, in the The user’s manager, specified approver, or event creator then declines the user’s application to attend, by opening the application request notification, clicking Decline, and then entering a message to the user explaining the reason for declining their request: | The user’s application to attend the event is decline. |
A user has applied to attend an event and is awaiting approval: You have been added to %{event_name} %{occurrence_starts_at} and your approval is pending. The approver has been notified of your request. If the user has a registered email address, they also receive a matching email in their inbox: | A user clicks the Register button on an event that requires attendees to be approved. | The user’s application is sent to the relevant approvers such as a specified approver, the user’s manager, or the event creator via notification, where it must be approved or declined. |
You missed the event %{event_name} on %{event_date} %{event_time}. If the user has a registered email address, they also receive a matching email in their inbox: | This notification is triggered when the event host specifies that an attendee did not attend the event. This is done by clicking the Take attendance button the homepage of the event, and then clicking the cross (x) next to the attendee's name in the Attended? column: | The attendee is marked as having not attended the event. |
Notifications for event creators
...