Logo StartupKit
EN

Your Daily Digest

One email each morning with everything waiting on you across hiring, security reports, and outreach — and the rules that keep it quiet when there's nothing to say.

Why It Matters

Work arrives in three places at once: candidates waiting on a review, a vulnerability report inching toward its SLA, a prospect who replied yesterday. Checking three screens every morning is how things get missed. The daily digest is one email that answers “what needs me today” — and, just as importantly, stays silent on the days the answer is “nothing”.

When It Arrives

9am, in your own time zone. Not the account’s, not the server’s — yours, from the Time zone field on your profile. If you never set one, Kit uses the platform clock (UTC) instead, so it’s worth setting.

You get one digest per account, per day. If you belong to two Kit accounts, you get two emails, each containing only that account’s work — they never mix.

What’s In It

Rows are grouped by urgency — Critical, then Time-sensitive, then For review — most urgent first inside each group. Every row links straight into Kit, at the filtered list it counts.

Area Rows you may see
Hiring Overdue decisions, code assignments about to expire, reviews assigned to you, candidates going quiet, offers expiring, applications waiting on screening
Security Reports assigned to you: SLA breached or at risk, stalled, awaiting triage, waiting on your reply, a reply drafted but unsent, a bounty proposal open
Outreach Replies waiting on a human, drafts pending approval

Only areas your account has turned on appear, and only the ones you have access to. A member with no Security access never sees a security row, whatever the account has enabled.

It’s Your Queue, Not the Account’s

The digest is always your personal queue — this is the one place where being an admin changes nothing. The home page shows admins the whole account by default; the digest never does.

That has a deliberate consequence: account-wide alarms that belong to nobody in particular are not in the digest. They stay on your home page, where whoever looks first can pick them up:

  • An on-call rotation with nobody covering it
  • A failed bounty payout
  • Bounty dismissal appeals waiting on a decision
  • Open reports with no assignee
  • Job postings that still need setup, and hiring payouts waiting to be released

Hiring rows are limited to jobs you’re on the team of (plus reviews assigned to you personally, wherever they are). Security rows are limited to reports assigned to you. Outreach rows cover the campaigns you can see.

The Three Days Kit Stays Quiet

A digest that arrives every morning saying the same thing is a digest people stop opening. So Kit skips the send entirely when:

  1. Nothing is waiting on you. No email — not an empty one.
  2. It’s the weekend. Saturday and Sunday in your own time zone.
  3. Nothing has changed. Same rows carrying the same numbers as the last digest you received — including a number that went down, which counts as a change and does send.

Important

One exception overrides rules 2 and 3: anything in the Critical group. A breached SLA or an overdue decision gets its email on a Saturday, and gets it again tomorrow even if nothing about it moved. If a critical row is present, the digest sends.

Rule 3 compares against the last digest you actually received, which may be several days back — so a Monday digest is compared against Friday’s, not against a weekend that never sent.

What the Email Is Allowed to Name

The digest is email: it lands in an inbox, gets forwarded, and sits in backups. So it is deliberately narrow about what it prints.

Named in the email Never in the email
The title of a security report you can open Candidate names
The title of a job posting Prospect and researcher names
Counts, ages, and amounts Email addresses, report bodies, notes

A restricted report or job posting you do have access to is still counted in its row’s number, but its title is never printed — the row keeps its generic label instead. Anything you can’t access isn’t counted at all.

New Since Yesterday

A row is tagged New since yesterday when it wasn’t in your previous digest at all, or when its number has grown since. Rows that shrank or held steady carry no tag. Your very first digest carries none — there’s nothing to compare it against yet.

Turning It Off

The digest has its own category, separate from every per-area one:

  1. Go to Account SettingsEmail Preferences
  2. Toggle Daily digest off
  3. Click Save

It’s on by default. Because it’s independent:

  • Muting Security program activity, Hiring activity, or Outreach activity does not mute the digest.
  • Muting the Daily digest does not stop those categories’ individual emails.

The unsubscribe link in the digest footer, and your mail client’s one-click Unsubscribe button, both affect the digest alone. See Email & Notification Preferences for how the categories work.

Holiday Mode

Holiday Mode pauses the digest completely — no digests while you’re away, and none waiting for you when you get back. Each morning’s email is built from scratch at send time, so the first one after you return describes the queue as it is that morning, not the backlog of mornings you missed.

Quick Checklist

  • Set your Time zone on your profile so 9am means your 9am
  • Check that Daily digest is on under Email Preferences
  • Expect silence on weekends and on days nothing changed — that’s the design, not a failure
  • Use your home page, not the digest, for account-wide alarms like on-call coverage and unassigned reports
  • Turn on Holiday Mode before you leave rather than unsubscribing

Type to search...