Configure email settings and the weekly digest

You need a whole-portal administration grant to open Emails. Group administration does not include portal-wide email settings. Each member separately chooses whether to receive the weekly digest.

The sender is managed by Zentrik: no-reply@updates.zentrik.ai. These messages are outbound-only. Replies are not monitored; the message directs people back to the portal. Do not set up a team reply inbox as a prerequisite for this workflow.

1. Open Emails → Sender and schedule in portal administration.
2. Review Sending identity and the outbound-only notice.
3. Select Enable weekly digest when the program is ready for recurring updates.
4. Choose the day, time and timezone. Confirm the timezone before interpreting the local send time.
5. Select Save email settings. Use Discard changes if you want to return to the saved configuration.

Turning on a digest establishes the next eligible roundup; it does not replay all old community content. The digest includes posts explicitly approved for it, not every new draft or published item.

Open the relevant published post and review its digest controls. Check the current revision and audience before approving it. If the content changes, review it again rather than assuming an old approval applies.

Only members who opted into the digest and remain eligible may receive it. Current enrollment, audience, pause and global/topic opt-outs still apply at dispatch. A member who declines a weekly digest may still choose research invitations or announcements independently.

An immediate announcement and a digest are separate delivery choices. Review the existing history and inclusion controls to avoid assuming the same item should be sent again. An empty eligible roundup is not a reason to invent or resend content.

Open Emails → Delivery activity to inspect bounded history by type, status and period. The item-specific controls remain the place to review and send an invitation, Study request or announcement.

Check the saved schedule and an eligible member’s actual preferences. Then inspect the resulting delivery activity. A configured schedule alone does not prove that a message was generated, accepted or delivered.

See Send and schedule emails for item-specific review and Email delivery states and contact rules for interpreting the history.