Integrations

Atlas reads only from the tools you connect, and only what you choose there. Every tool is connected on the Connections page of your organisation's Atlas workspace. Employees connect their own tools; an organisation admin connects the shared ones. Each guide says what Atlas reads, how to connect and how to stop.

Your own tools

• FirefliesTranscripts of the meetings you recorded or attended.
• GranolaTranscripts of the meetings you recorded with Granola.
• Google Calendar and DriveEvents and attendees of the calendars you choose; names, folders and sharing of the files you choose, and their text when you allow it.
• JiraIssues, epics and status changes in the projects you choose.
• Slack (as you)Lets Atlas post as you when you approve a message; reads nothing.

Your organisation's tools

• SlackMessages in the channels your admin chooses, and the notifications Atlas sends. Installed by an organisation admin.
• NotionPages created and edited wherever the Atlas integration is added, and their text when your admin allows it.

What every connection has in common

• Atlas reads once a day. The first sync reaches back a few months, up to each tool's window; you choose how far when you connect.
• Every fact Atlas shows names the meeting, message or document it came from, with a link when the tool gives one.
• What was said in a private channel or a confidential meeting stays with the people who were in it. Atlas never widens access.
• Disconnect at any time on the Connections page. The stored access is deleted at once, and Atlas stops reading from that moment.

What Atlas keeps out of everything it reads, and where it is kept: Privacy policy. Questions: Support.

Slack, Google Calendar, Google Drive, Notion, Jira, Fireflies and Granola are trademarks of their respective owners; their marks are shown to identify the tools Atlas connects to.