Module guide
Daily digest
What is waiting for you across your tools, on one shelf of cards.
Overview
Daily digest gathers what is waiting for you in the tools around Atlas and puts it on one shelf. A pull request wanting review, an email thread owed a reply, a mention in chat, a standup update to draft, a clash in the calendar, tasks that have run past their date, and a habit whose streak is about to break. Each is a card, so the answer to what needs me today is one screen instead of five tabs. Where a card comes from another tool, it is a pointer to the work rather than a copy of it: acting happens in the tool that owns it.
Highlights
The capabilities worth knowing before you dive in.
- One shelf covering pull requests, email threads, chat mentions, standup drafts, calendar clashes, overdue tasks and habits at risk
- Each card names its kind, so a glance says what sort of attention it wants
- Loading, ready, empty and failed states are all distinct, so a digest that could not be read never looks like a quiet day
- Built from the tools you have already connected, so nothing has to be configured twice
Important to know
Limits, permissions, and sharp edges to keep in mind.
- A card is a pointer, not a copy. Acting on a pull request or an email happens in the tool that owns it.
- The digest can only see what is connected. A missing lens is usually a connector that is not set up rather than a quiet day.
- An empty digest and a digest that failed to load are different, and the screen says which one you are looking at.
- It is your digest. It reflects what is waiting for you, not for your team.
How to use it
The primary workflow, start to finish.
- Open Daily digest at the start of the day.
- Read the cards. Each one names the kind of attention it wants.
- Follow a card into the tool that owns the work and act there.
- If a lens you expected is missing, check Integrations. A connector that is not set up produces no lens.
FAQ
- Can I reply to an email or approve a pull request here?
- No. A card points at the work; acting happens in the tool that owns it, which is what keeps Atlas from holding a second stale copy of your inbox.
- My digest is empty. Is it broken?
- Possibly not. An empty digest and a failed read are shown differently. If it says it could not be read, that is a failure; if it is simply empty, nothing was waiting.
- Why is a tool I use missing?
- Because it is not connected. The digest reads what Integrations has set up and cannot see anything else.
- Does my team see the same digest?
- No. It is built from what is waiting for you specifically.
Automate this module