Files

Files is a browsable record of every deliverable a coworker has ever produced for you — reports, spreadsheets, decks, source data — searchable in the console instead of buried in old messages.

​

Why this matters

A coworker’s real output is a file: a competitor report, a cleaned-up spreadsheet, a client deck. When you get it back by reply, that’s convenient in the moment — but three weeks later, “which email had that file again?” is the wrong way to spend your time. Files exists so the answer is always “open the console and look.”

​

How it actually works

Every file lands in two places at once: as an attachment on the email or WhatsApp reply your coworker sends you, and in your console’s Files view. The console version isn’t a live scan of some shared drive — it’s built from your task history directly, so it’s always fast and never shows something that isn’t actually there. Files are grouped by what they genuinely are, not by which coworker made them, so you’re browsing by “spreadsheet” or “presentation,” not hunting through a per-person folder.

​

Concrete examples

• “Find the market research Hannah sent me last month” — search or browse by type rather than scrolling your inbox.
• “Download the dashboard Alex built for the Q3 review” again, without asking him to resend it.
• “What data did I originally give Alex for that chart?” — open the task and see the raw input alongside the output.
• “Pull everything from that competitive teardown” — including the source spreadsheet, the finished report, and any supporting files, all attached to one task.

​

What’s in the library

Click into any task and you can also see the raw inputs it was given — the files you originally sent in, right alongside what came back, so you can always trace a result back to its source.

​

What this is not

Files isn’t a general-purpose cloud drive — you don’t upload arbitrary documents here to store them; it only holds what a coworker has actually produced or been given as part of a task. For material you want a coworker to draw on as ongoing background context rather than a one-off deliverable, see how sharing works via your integrations instead.

​

How this connects

Interactive dashboards and data stories specifically live in Builds, not here. What a coworker remembers about your preferences (separate from the files themselves) is covered in Memory. Every file is tied to a task, and every task is priced and tracked the same way — see Credits & Billing.