--- title: Digest Emails slug: digest-emails createdAt: 2026-05-04T01:29:39.620Z --- Digest email functionality in Activate helps reduce email volume by grouping eligible notification emails instead of sending each one separately. This is useful when users receive a large number of notifications and do not need every message to arrive immediately. ## What digest email does When digest email is used, Activate groups eligible notification emails and sends them through the notification process instead of sending each message individually as soon as it is generated. This helps to: - reduce inbox clutter - make notifications easier to review - improve the experience for users who receive frequent workflow notifications ## Where digest email is used Digest email applies to notify-style workflow emails. These are the standard notification messages sent by workflow notify actions, such as general status updates, reminders, and informational messages. Approval emails should be treated as immediate unless digest behaviour has been specifically confirmed for your implementation. ## When to use digest email Digest email is best suited to messages that are informative rather than urgent. Common examples include: - general workflow notifications - reminder emails - informational updates - high-volume notifications sent to operational teams Digest email is generally not suitable for messages that require immediate attention. ## How digest email is controlled Digest behaviour can be controlled at two levels. ### Task-level default A task can be configured so that notify messages use digest delivery by default. This is useful when most notifications for that task should be grouped rather than sent immediately. ### Message-level setting A specific notify message can also be configured to use digest delivery or immediate delivery. This makes it possible to: - use digest delivery for routine notifications - send important messages immediately when needed ## Disabling digest delivery for a task To disable digest delivery by default for all notify messages in a task, set the task parameter: `` `SendNotifiesAsDigest = False` `` ## Send time and queued delivery Notify messages can also be configured with a send time. This is separate from digest delivery, but both options use the same notification handling process. In practice, this means a message can be sent immediately, queued for later, or included in digest-style delivery depending on how the workflow is configured. ## Message content Digest-capable notify messages can still include the same message content used for other Activate notifications, including: - recipients - subject - body - from address - templates - CC recipients - attachments ## Customising digest email content The digest email layout can be customised by editing the summary email template. The template is stored at: //Resources/Configuration/Email/Email.Summary.Template ### What you can customise You can use the summary template to change how the digest email is presented, including: - the overall layout of the email - the columns shown in the digest table - the labels and headings used in the digest - additional row values drawn from the information already available to the template For sites that want to show more information on each digest row, this is the main place to make that change. ### Adding more information to each row You can extend the digest email by updating the summary template to show additional values in each row. A common approach is to add extra columns to the digest table for information that is already available to the digest, such as job-related details or other notification values. Some values can also be added using expressions in the template, but these should be used carefully to avoid making the digest harder to read or maintain. ### What to watch out for When extending the digest rows: - prefer values that are already available to the template - use expression-based values sparingly - avoid adding too many extra columns, as this can make the digest harder to read - test the output with realistic notification volumes before publishing the change ### What administrators can change Administrators can: - update the digest layout in `//Resources/Configuration/Email/Email.Summary.Template` - add extra columns where suitable values are already available to the template - use expressions in the template where appropriate If the information you want to show is not already available in the digest template, further implementation work may be required. ## Recommended approach When setting up digest email, start by identifying which messages are useful to group and which should still be sent immediately. A good approach is to use digest delivery for routine notification traffic and immediate delivery for messages that need fast action. For example: - use digest delivery for reminders and status updates - use immediate delivery for urgent or time-sensitive messages ## Managing expectations When digest email is enabled, users may receive fewer individual emails. This is usually a benefit, but administrators should make sure users understand that some notifications are being grouped rather than delivered one by one. ## Troubleshooting If digest notifications are not behaving as expected: 1. Confirm the workflow is using a notify action. 2. Check whether digest delivery is enabled for the relevant task or message. 3. Review whether the message has been configured to send immediately instead. 4. Check whether a send time has been applied. 5. Confirm the notification process is handling queued messages as expected. If approval emails are still being sent immediately, review the workflow design and any implementation-specific configuration. ## Summary Digest email in Activate is designed to reduce email volume by grouping eligible notify-style workflow messages instead of sending each message separately. It is best used for routine notifications that do not require immediate action. Administrators can control digest behaviour through workflow configuration, using task-level defaults and message-level settings to decide which notifications should be grouped and which should be sent immediately.