What Firstweek reads from Slack
- Public channels, threads, canvases, and pinned messages
- Admin-approved private channels, when explicitly granted
- Channel and workspace metadata needed to attribute a claim to its source
What shows up in the briefing
Decisions and context surfaced in Slack become inline citations in the new hire's briefing - a claim about how the team works, linked back to the thread it came from, not a raw message dump.
Read-only, and nothing raw is ever stored
Every integration - Slack included - connects read-only. Firstweek can never write to, modify, or delete anything in your tools. Slack content is processed in memory and never persisted; only AI-generated summaries, and opt-in source snippets up to 200 characters, are saved.
Full detail: read the trust & security page for the complete data-handling policy, or the subprocessors list for exactly what Slack data category is disclosed.
See what a real briefing built from sources like Slack actually looks like.
See a sample briefing →