The Slack integration brings conversation metadata into Leanmote — who interacted with whom, in which conversation, and when. It feeds the Team Collaboration Network and interaction signals across other dashboards. Leanmote never reads or stores what people write.
What Leanmote pulls from Slack
For every message, Leanmote records a single interaction made of four things:
Who sent it.
The other participants of that conversation, recorded as the receivers of the interaction.
Which conversation it happened in.
When it happened.
It also reads user profile information — name and email — so Slack identities can be matched to Leanmote teammates.
Message content is never read and never stored. Text, files, attachments, link previews and reactions are discarded while messages are processed. None of it is written to Leanmote, and none of it appears on any screen.
Which conversations are measured
When someone connects Slack, they authorize Leanmote with their own Slack account. Leanmote then discovers every conversation that person can see — public channels, private channels they belong to, group DMs and direct messages — and newly discovered conversations start out being measured.
Admins control this from Administration → Discoveries → Channels. Every discovered conversation is listed there with its type (Public, Private, Group DM or Direct), and turning one off stops it from being measured. Direct and group messages are listed under the generic name Internal message — the names of the people in them are not stored.
Because only the interaction is measured, a direct message contributes exactly what a public channel message does: a sender, one or more receivers, and a timestamp.
Connect Slack
Open
Administration → Integrations.Find Slack under Communication and click Connect.
Sign in to your Slack workspace and authorize the Leanmote app.
Open
Administration → Discoveries → Channelsand review what was discovered. Turn off any conversation you do not want measured.
Permissions
Leanmote requests read-only scopes. There is no write access to Slack, and Leanmote never posts anything.
The authorization is granted against the connecting user's own Slack account, so its reach matches what that person can see — direct messages included:
channels:read,channels:history— public channels.groups:read,groups:history— private channels the user belongs to.mpim:read,mpim:history— group direct messages.im:read,im:history— direct messages.users:read,users:read.email,users.profile:read— identity matching.
The history scopes are what allow Leanmote to count messages. They would also permit reading message text — Leanmote does not, as described above.
What it powers
Cross-team interaction patterns visible on Team Collaboration Network.
Volume signals that pair with code-review activity to spot collaboration gaps.
Privacy and access
Message content is never read, stored or displayed anywhere in Leanmote.
Discovery reaches every conversation the connecting user can see, including direct and group messages. Admins turn off whatever should not be measured from Discoveries → Channels.
Private channels require the connecting user to be a member — Leanmote cannot reach a channel that person is not in.
Direct and group messages are stored as "Internal message", without participant names.
Dashboards show how much people interact and with whom, never what was said.
Token storage and access controls follow the same rules as other integrations — encrypted at rest, accessed only during scheduled syncs.
Related articles
Integrations overview
Discoveries — Channels tab
Team Collaboration Network — overview