Help/Slack permissions, explained
Slack permissions, explained
When you add asyncmate to Slack, the install screen lists everything the bot can do. This page explains each permission in plain language, and what asyncmate cannot see.
1The short version
- asyncmate cannot read your channels. It does not ask for channel message history, public or private.
- In direct messages it reads only what you type to the bot itself, like
statusorhours yesterday, to run that command. It never sees DMs between people. Check-in answers come in through a form that opens from the DM. - It always posts as itself, never as a person.
2Every permission on the install screen
| Permission | Slack scope | Why asyncmate needs it |
|---|---|---|
| Send messages | chat:write |
Check-in DMs, digests, reminders, poll cards and kudos. |
| Post in public channels | chat:write.public |
Deliver the digest to the channel you pick without an invite step. |
| Custom name and icon | chat:write.customize |
Not used today: every message posts under the asyncmate name and icon. It is kept for a planned feature. |
| List channels | channels:read, groups:read |
Fill the channel picker for digests, polls and reminders. Private channels appear only where the bot was invited. |
| Join public channels | channels:join |
Join a public channel you picked for a digest, reminder or poll, so the post arrives even if nobody invited the bot. It never joins private channels. |
| Direct messages | im:write, im:history |
Open a DM to send your check-in questions, and read what you type to the bot there, so commands like status or help work in that DM. Both cover only the bot's own DMs, nothing between people. |
| People | users:read |
Names, avatars and timezones, so a 9:00 check-in lands at 9:00 in everyone's own timezone. asyncmate doesn't ask for members' email addresses. |
| Workspace details | team:read |
Your workspace name and icon in the dashboard. |
| Slash command | commands |
The /asyncmate command. |
3What asyncmate cannot do
- Read messages in any channel, public or private.
- Read direct messages between people.
- Post, edit or delete anything as another user.
- See files shared in your workspace.
4Signing in is separate
The dashboard sign-in uses Sign in with Slack (OpenID Connect). It reads your name, email and avatar to create your account, and grants no workspace permissions. Google and Microsoft sign-in and email magic links work the same way.
5How credentials and answers are stored
The bot token Slack issues on install is encrypted at rest and never written to logs. Check-in answers and logged hours are stored so digests, history and reports work; the Privacy Policy covers retention, export and erasure. If you uninstall asyncmate, sending stops immediately and workspace data is erased after the retention window.
Tip: sharing this with your Slack admin? The admin approval guide has a ready-to-send summary.