Overview answers one operational question: what needs action now?

The product label is Overview. The queue is Needs attention, with For me and For the space views. Some Slack digest copy still says “Today” and opens Overview.

For me

Rows are attributable to the signed-in person and grouped from five sources:

1. Review requests.
2. Changes requested and actionable comments.
3. Failing checks.
4. Deployment approvals.
5. Rule violations on the person’s pull requests.

Each row carries the repository/PR reference, why it needs attention, age, and a path to the full event. See all in Events opens the broader activity feed.

For the space

The space view shows outstanding delivery attention across governed repositories. It helps an owner see where review, checks, deployment approval, or rule findings are holding work — without pretending every row belongs to them.

Customize

Overview › Needs attention › Customize controls two member-owned concerns:

• Which attention sources appear for that person.
• Their optional personal_digest: weekday cadence, local time, and Slack Messages or account email.

The digest is a dated snapshot of For me. Overview stays live. An administrator cannot enable or inspect another member’s personal digest.

Movement, not a vanity dashboard

Overview also surfaces current delivery movement such as merged/opened PRs, deployments, failures, and review timing. Full breakdowns and trend series live in Metrics; saved populations live in Reports.

Same evidence elsewhere

Honesty

An empty queue is a success state. A failed dependency does not produce a partial personal digest. Identity or destination gaps remain visible rather than silently routing a message to the wrong person.