Work through your Inbox
Clear your Inbox once a week, so the Librarian’s good suggestions join your Library and the rest get turned down with a reason.
Before you start
Section titled “Before you start”- Permissions: anyone in your organization can accept, snooze or turn down a card, because every member has write access to the Library. Only admins can open Nightly insights.
- Data you need: a Library your team has been asking questions in. Most cards come from the nightly pass, new data and those questions, so a brand-new Library may have only a few.
- Credits this uses: reading, snoozing and turning down cards cost nothing. Discuss, Chat about these and Accept with edits each start a Librarian chat, which uses a credit. The exception is Accept with edits on a Worth watching card, which opens a form instead.
1. Pick a time each week
Section titled “1. Pick a time each week”Cards pile up when nobody looks, and on the default setting the nightly pass runs every night for your first week, then weekly for as long as someone keeps reading the Inbox. A regular slot, like Monday morning, keeps the list short. The badge on Inbox in the rail counts what’s waiting.
At the top, the digest counts cards by kind, such as “2 changes that need you · 3 questions worth a view”, and chips filter the list.
Admins also get the digest email after each scheduled nightly pass that leaves something waiting, with alerts first. Treat it as the nudge to open the Inbox, not a replacement for it.
2. Read the card, not just the title
Section titled “2. Read the card, not just the title”Every card lays out the same parts:
- Why it matters: what would change. Show all opens longer text.
- Who’s been asking, such as “asked by 3 people, 7 times, in the last 30 days”. “nobody asked this in the last 30 days” is a reason to slow down.
- Accepting adds: exactly what accepting puts in your Library, and in which workspace.
- Evidence, folded at first.
Open Evidence before you accept anything that adds a view or a KPI. Where the numbers come from names the sources and how they join, with the share of rows that match. Does it use the tables you’d use? A low match share means the answer leaves rows out. Then skim the sample rows and The query that ran.
3. Decide
Section titled “3. Decide”| Button | Use it when |
|---|---|
| Add … | The card is right as it stands. The button names what it adds, like Add question + view + KPI |
| Accept with edits | The idea is right but a detail isn’t, like the date range. It opens Librarian chat and asks for the change first. On a Worth watching card it opens a form for the monitor’s name, breakdown and email list |
| Snooze 30d | Not now. The card comes back in 30 days |
| Not useful | It’s wrong or doesn’t matter. Add a reason, then click Confirm |
| Discuss | You’re not sure. It opens Librarian chat to talk it through, and the card stays |
After you accept, an Added to your Library note links to each new item. A new view builds in the background, so its link appears when it’s ready.
4. Give a reason when you turn one down
Section titled “4. Give a reason when you turn one down”The reason is optional. Write one anyway. The Librarian won’t bring the card back unless something changes, and if it does come back, the card quotes your reason and says why it returned. “We count revenue from paid invoices, not orders” helps whoever reads it next. A blank doesn’t.
5. Slow down on five kinds of card
Section titled “5. Slow down on five kinds of card”- Metric to track: the Librarian chose the definition, and it may not match how your business counts. Read the query in Evidence, and use Accept with edits if it’s off. A few KPIs you trust beat many you don’t. See Choose the KPIs to track.
- Cleanup: “N collections cover ’…’ and overlap” moves everything onto one collection and deletes the others. The other version, about views that answer no question, only attaches them.
- Can’t answer this yet: accepting records a fact. It doesn’t build a view or connect anything. The real fix is the data. See Decide what to connect first.
- Worth watching: a KPI moved in a way its own history says is unusual, and accepting sets up a monitor on it. Would you act if it moved like that again? If not, choose Not useful. To split it by region or store, use Accept with edits. See Worth watching cards.
- Something changed: an alert from a monitor, with Acknowledge instead of an accept button. See Monitors and alerts.
6. Act on review verdicts
Section titled “6. Act on review verdicts”Below the cards are verdicts from the latest review of your team’s questions, usually last night’s. Each one covers a group of similar questions. These four show first, because each one waits for a person:
| Verdict | What it means | Button |
|---|---|---|
| build recommended | A view is worth building for these questions | Create this view |
| retire recommended | These views duplicate each other | Retire these |
| gap | The data to answer these questions isn’t in the Library | Connect the data |
| error | The review of this group failed | Retry this cluster |
Reviewed folds away the settled ones: built, retired, covered, kept and skip. A covered verdict has Open the covering view.
Say Curio’s operations team keeps asking about on-time delivery by carrier, in slightly different words. The review groups those questions, and because the view On-time delivery rate by carrier answers them, the verdict is covered. Without that view, it would be build recommended, and nothing would be built until someone clicked Create this view.
Only the newest run shows, so act on those four before the next run replaces them. A view that other views or projects use is never retired.
7. Look for more
Section titled “7. Look for more”When the list is clear, Find new questions at the top of the Inbox asks the Librarian for questions nobody has asked yet, starting from gaps in your KPI coverage.
Admins can also start Run discovery under Build and clean up on Nightly insights. Check the mode first. With Require confirmation, its verdicts wait in the Inbox. With Auto-build, it builds views itself. The mode is saved per browser, so it may not be the one you last picked.
Check your work
Section titled “Check your work”- The badge on Inbox counts only what you chose to leave.
- Everything you accepted is linked from its Added to your Library note, and new views read READY on the Views tab.
- No verdict above Reviewed is waiting without a decision.
- Every card you turned down has a reason.
Troubleshooting
Section titled “Troubleshooting”Accept is turned off on a card. It came back after someone turned it down. Read why, tick I’ve read why this came back, and then accept.
The badge counts an alert you acknowledged. The badge updates after you accept, snooze or turn down a card, but not after Acknowledge. Reload the page.
A card says it was already handled. Someone else acted on it first, and the list refreshes.
Discuss took you out of the Inbox. Discuss and Accept with edits send a Librarian chat straight away and open it. Accept with edits on a Worth watching card is the exception: it opens a form on the card. Come back to the Inbox when you’re done.
The Inbox is nearly empty. The nightly pass may be off or out of credits. An admin can check How often and Nightly credit budget on Nightly insights.
Next steps
Section titled “Next steps”- Inbox: every card kind and button.
- How the Library learns: where the suggestions come from.
- Nightly insights: the pass that files most cards.
- Choose the KPIs to track: what to do with Metric to track cards.