Chat is where decisions get made informally and documents are where they get written down, sometimes. Fivo reads both so that a decision taken in a thread and the page that describes it end up linked to the same project.
Chat tools
Fivo connects to Slack, Microsoft Teams, Discord and Telegram.
When you connect a chat tool, Fivo lists the channels or chats it can read and you choose which ones feed the graph. Messages are grouped into episodes by thread and time window, so a week of conversation in a channel becomes a handful of facts with context, not thousands of isolated lines.
What the graph gets from chat:
- Decisions and who took them, with the message they came from.
- Commitments made in passing ("I'll have it ready Thursday").
- People and how they relate to projects and companies.
- Incidents and their timeline, next to the code change that caused or fixed them when GitHub is connected too.
Who sees what
With organization scope, a channel's facts are visible to the channel's members. If someone joins the channel later, they see its facts immediately; if they leave, they stop seeing them. Slack and Teams can tell Fivo who is in a channel. Discord and Telegram cannot, so material from them is visible to the organization owner and to the people who took part in the conversation.
A private channel the Fivo bot was not invited to is listed as a source Fivo cannot access, so you know it is missing.
Telegram and Discord specifics
A Telegram bot cannot read what was said before it joined, so a chat starts feeding the graph from the moment you link it. In Discord, Fivo reads only the servers where you installed the bot, and only the channels the bot can see.
Documents
Fivo connects to Notion, Confluence, Google Drive and Google Docs.
Pages and documents become sources for decisions, specs and plans. When a spec is written and then parked, the graph remembers both facts, and a question like "who asked for SSO" can point at the ticket, the spec page and the call where it came up.
Google Drive is not read whole. You pick the files that feed the graph.
Who sees documents
Notion cannot tell Fivo who can read a page. Material from such tools, when brought in with organization scope, is read by the organization owner and by the people recorded as authors or editors of the page. Confluence and Drive can report membership, so their pages follow the same rule as a chat channel: visible to those who can open them in the original tool.
Choosing a scope
Chat and document tools can be connected with personal or organization scope. Personal keeps everything to you. Organization makes it available to colleagues according to the rules above, and only the organization owner can connect a source that way. See Connect your tools for the full explanation.
Keeping it current
Connected channels and pages are re-read on a regular schedule, and tools with webhooks push changes as they happen. The AI Brain view shows each source's last sync. Renaming or archiving a channel in the original tool does not delete its history from the graph; removing the source from Fivo does.
Good first choices
For most teams, one or two busy Slack or Teams channels plus the Notion or Confluence space where decisions are documented give the graph a strong backbone. Add project tools next: see Connect code and project tools.
Step-by-step guides
Each integration has its own guide with permissions, steps and troubleshooting.
Chat:
Documents:
- Connect Notion
- Connect Confluence
- Connect Google Drive
- Connect Google Docs
- Connect OneNote
- Connect Airtable
- integrations
- slack
- teams
- notion