Slack, read-only.

Most of what a new hire needs to know is already in Slack, spread across channels nobody reads in order. Firstweek connects read-only and reads only the channels your admin selects: public channels you pick, and private channels only when an admin adds the bot.

What Firstweek reads from Slack

Threads, canvases and pinned messages in the channels you select
Admin-approved private channels, when explicitly granted
Channel and workspace metadata needed to attribute a claim to its source

What shows up in the onboarding artifact

Decisions and context from Slack become cited claims in the onboarding artifact: a statement about how the team works, linked to the thread it came from. Never a dump of raw messages.

Read-only, and the raw content is never stored

Every connection, Slack included, is read-only: Firstweek never writes to, changes or deletes anything in your tools. Slack content is processed in memory and never stored. Only AI-generated summaries persist. A citation can quote up to 200 characters of a summary, and an admin can turn that off.

The Firstweek bot joins the public channels you select so it can read them, and Slack shows that it joined.

Full detail: the security page covers data handling end to end, and the subprocessors list shows exactly which Slack data is processed.

Other read-only connections: HubSpot · Salesforce · Confluence · Google Drive · Microsoft 365 · GitHub · Jira

Run Firstweek on your next real hire. 30 days. Then we talk about whether it's worth keeping.

See a sample artifact →