What Firstweek reads from Confluence
- Architecture decisions, runbooks, and space-level docs
- Project tickets and documentation content, where Confluence and Jira share a workspace
- Page structure and metadata needed to attribute a claim to its source page
What shows up in the briefing
Confluence content typically shows up in the "institutional knowledge" and "how we work" sections - the decisions and norms that are technically written down somewhere, just not anywhere a new hire would think to look on day one.
Read-only, and nothing raw is ever stored
Every integration - Confluence included - connects read-only. Firstweek can never write to, modify, or delete anything in your tools. Confluence 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 Confluence data category is disclosed.
See what a real briefing built from sources like Confluence actually looks like.
See a sample briefing →