Notify is a simple, lightweight module for sending e-mail notifications about new content and comments posted on a Drupal web site.

Submit bug reports and comments via the project's issues queue on drupal.org.

If you enable node revisions node revisions, the notification e-mail will also mention the name of the last person to edit the node.

## Requirements

This module requires a supported version of Drupal and cron to be running.

## Permissions

To set up permissions for Notify navigate to: Administration » People » Permissions.

There are three permissions:

1. access notify – to subscribe to and receive notifications when there is new content
2. administer notify – to administer general notify settings, default settings, and users
3. administer notify queue – to administer the notify queue operations and skip flags

The access notify permission will enable a tab (Notification settings) on the users My account-page where the user can view and change personal notofication settings. This permission is suitable for all users.

Note that you must also enable access notify for the anonymous user role if you want notification enabled by default for new users.

The two permissions to administer notify should only be given to trusted users. They give access to various parts of the Notify administration GUI (described in the next section).

## Configuration

The administrative interface is at: Administration » Configuration » People » Notification settings.

There are five tabs:

1. Settings: All the main options for this module.
2. Queue: Queue: Operations on the notification queue.
3. Skip flags: Inspect the notification queue and flag postings to skip.
4. Defaults: Default settings for new users.
5. Users: Review and alter per-user settings.

### Settings

The Settings tab gives the administrator access to the general settings for the module.

It can be use to specify how often notifications are sent, the hour to send them (if the frequency is one day or greater), the number of failed sends after which notifications are disabled, and the maximum number of users to process out per cron.

When setting how often notifications are sent, note that e-mail updates can only happen as frequently as the cron is set to run.

To reset the count of failed sends to zero, look at the notification settings in the user's profile and save it by pressing “Save settings” (there is no need to change anything).

If you check “Include updated posts in notifications”, any change to a node or content will cause it to be included in the next notification. Note that even minor changes, such as correcting a trivial typo or setting or unsetting the “sticky” attribute for the node will flag it as updated, so use this option with caution, or in combination with skip flags (see below) in order to avoid excess notificatons.

If you check “Exclude contents from unverified authors from user notifications”, notify will not notify about postings from unverified (i.e. anonymous) authors. You need only care about this setting if you permit postings from anonymous authors. Even if you have spam protection in the shape of CAPTCHA or other measures, you may experience that some spammers still manage to post contents on your site. By checking this setting, you will at least save your subscribers from being notified about spam. As with most of these settings, it doesn't apply to administrators. Even when checked administrators will be notified, in order to intervene and delete the spam before it gets much exposure. Note that if you check this setting, there is currently no way to keep track of the content that is excluded due this setting. If you use it, your users will never receive any notification email about new content from unverified authors. That's not a bug, it is a feature.

If you check “Administrators shall be notified about unpublished content”, users belonging to roles with the “administer nodes” and “administer comments” permissions granted will receive notifications about unpublished content. This is mainly to make the module useful to manage moderation queues.

If you've set up a multilingual site, there should also be three radio buttons that allow you to filter notifications about new nodes against the user's language setting (it may be set by editing the user profile). The first setting (“All contents”) will notify a user about all content on the site the user subscribes to. If a piece of contents exists in more than one language, all versions will be notified about. The setting “Contents in the user's preferred language + contents not yet translated” will notify about subscribed content in the user's preferred language and also about subscribed content that is in some other language if no translation of it exists. The last setting, “Only contents in the user's preferred language”, will only notify about subscribed contents in the user's preferred language. However, please note that contents that are marked as “language neutral” will always be included in notifications. The multilingual settings do not apply to administrators. Administrators will always be notified about all new contents. Note that if you use the second setting, contents that is not in the user's preferred language will be excluded from the notification if some translation of exists, even if that translation is not to the user's preferred language. To avoid this having unexpected effects, when you provide translation of a node, you should translate it to all langauages the site supports.

The “Watchdog log level” setting lets you specify how much to log. The setting “All” will make a log record of every notification mail sent. The setting “Failures+Summary” will only log failed notification attempts. It will also insert a summary of how many sent and how many failures at the end of each batch. The “Failures” setting will omit the summary. The “Nothing” setting will turn of logging for Notify.

The “Weight of notification field in user registration form” setting lets you specify the weight that determines the position of the notification field group when it appears in the user registration form. The number is relative to the row weights that can be inspected on Administer » Configuration » People » Account settings. Pick a higher (heavier) weight to make the field group positoned below a specific field, and vice versa.

### Queue

The Queue tab gives access to notification queue operatons and the notification queue status panel.

The radio buttons below the heading “Process notification queue” has the following meanings:

- Send batch now: Force sending a notification batch without waiting for the next cron run. Note that if the number of notifications queue exceeds the maximum number of users to process out per cron run, only the maximum number of users are processed. The rest will be queued for the next cron run or the next manual send batch (whatever happens first).
- Truncate queue: Truncate the queue of pending notifications without sending out any notifications.
- Override timestamp: Change the value of the last notification timestamp. To resend postings that has already been sent, set pick a value before the oldest posting you want to resend.

The text field “Last notification timestamp” can be used to override the value of the last notification timestamp. This value is only used to override of the operation “Override timestamp” is selected.

The Status panel at the bottom of the page gives the administrator a rough overview of the current state of the notification queue. Its main use is for debugging.

### Skip flags

The Skip flags tab will show a list of all the postings that are candidates for being sent in the next notification. Each has a checkbox that can be checked to exclude the posting from all notification emails, including the one sent to the administrator.

### Defaults

The checkbox under “Notification default for new users” is used as the default value for the notification master switch on the new user registration. Note that this setting has no effect unless you grant the anonymous user role the right to access notify.

The “Initial settings panel” let you set up the initial settings that will apply to new users registering, and to users that are enrolled in notifications with batch subscription. These settings have no effect on users that already have the master switch set to “Enabled”.

The final section under the Settings tab let you set up notification subscriptions by node type. Having nothing checked defaults to making all content types available for subscription.

### Users

The Users tab is to review and alter per-user settings for those users that have the master switch for notifications set to Enabled.

If you tick the box “Bulk subscribe all users”, all non-blocked users that do not already subscribe to notifications will be subscribed with the initial settings set under the deafult tab.