Configuring Notification Settings

Looking for something specific? Skip ahead:

How do I add a new notification method?

ControlShift supports a few different notification methods for activity on the platform, including email and Slack notifications.

For email notifications, admins can configure personal notifications and/or distribution list (listserv) notifications. The former is used when an admin wants to choose which notifications are emailed to their individual email address. The latter is used when notifications should be sent to an existing distribution list.

Notifications to an individual user's email address

If you'd like to receive notification emails to your individual email address, start by going to your My Account page (in the user dropdown, which is visible by clicking the down arrow next to your name in the header) and clicking the Notifications tab. From here, choose the notifications you'd like to subscribe to and click to Save. 

Admins can update their notification subscriptions at any time by returning to the Notifications tab.

Listserv or Distribution Lists 

If you'd prefer to send notifications to a distribution list, listserv, or some other email address that isn't associated with an existing admin account, you can do so by going to the admin homepage > Settings > Contact > Add New Notification Method.

After entering the new email address in the Email Address field, choose which notifications should be sent and click Save.

If you need to change the notifications associated with an email address on this page, click Edit. To delete a method, choose Delete.

Slack

Organizations using Slack can also have notifications about items in need of moderation sent to their Slack workspace. Slack notifications are configured by going to the admin homepage > Settings > Integrations. More information about the Slack integration.

Which notifications should I subscribe to?

The types of notifications that users should receive will depend upon the organization's structure and whether admins are assigned to a specific part of the toolset.

Organizations who assign org admins to different areas of the toolset may find the following breakdown helpful:

• For users working solely on petitions, you'll probably want to include all of the notifications in the petitions heading, as well as notifications about partnership emails, members deleting their accounts, and petition events being created or updated.
• For users working only on local groups, include notifications about group organizer requests — which will include users requesting to be organizers of existing groups and users requesting to start a new group — and events in local groups being created or updated.
• For users focusing on offline events, include all of the notifications in the events heading and notifications about members deleting their accounts.

Regardless of your organization's structure, we recommend ensuring that every type of notification is sent to at least one admin at your organization.

Notifications for Regional Admins

If the admin subscribing to notifications is part of a regional team, they'll only receive notifications about matching items in their region. For example, if the admin is subscribed to the petition created notification, they'll only receive a notification if a petition is created in their specific region.

However, if the user is part of a regional team and a non-regional team, the regional filtering of notifications will no longer apply. For example, if a user is in a regional team for moderation, but is also granted admin access to partnerships through a non-regional team (because partnerships are not region-specific), and the admin then subscribes to the petition created notification, they'll receive notifications about all newly-created petitions regardless of the petition's region.