What it does
Settings for turning inbound email into tasks and comments, and for the identity this workspace's outbound mail uses — plus how activity notifications get batched into digest emails instead of arriving one at a time.
Who needs it
Any admin who wants people to be able to create work by email, or who wants to control how often notification email lands in their team's inbox.
Why use it
The notification digest setting alone cuts down on inbox noise on an active workspace; the rest of the page is ready to configure ahead of when inbound mail goes live.
How it works
Admin > Email Integration configures how a workspace turns email into tasks and comments, and what its outbound mail looks like. As of now the mail-server side of this isn't wired up — the settings below all save, but sending an email to the generated address won't actually create a task yet. Configure it in advance so it's ready the moment inbound mail goes live.
- Enable email integration — the master switch for everything on this page.
- Email-to-task address — a unique, generated address (
tasks-<token>@your-slug.task.app). Generate creates it the first time; Regenerate replaces it with a new one, invalidating the old address. - Create tasks from inbound email — when on, an email to that address becomes a new task.
- Create comments from email replies — when on, a reply to a task notification email is posted back as a comment on that task.
- Default list for emailed tasks — which list new tasks created by email land in.
- Outbound "From" name and Reply-to address — the display name and reply address used on mail this workspace sends.
Below that, Combine notification emails within (minutes) controls the separate activity-notification digest: rather than emailing every comment, mention, assignment and task update the moment it happens, each person's pending notifications are batched into one email once the oldest one has been waiting this long. Set it to 0 to send each notification immediately, or raise it to cut down on inbox noise.