As Guide expands AI-powered scheduling coordination inside Slack, additional Slack permissions are required to support conversational workflows between recruiters, coordinators and interviewers.
Why Is Guide Requesting Additional Slack Permissions?
Guide is introducing new Slack-based coordination workflows designed to reduce manual scheduling work for recruiting coordinators and recruiters.
These updates enable more intelligent scheduling conflict resolution directly inside Slack, including AI-assisted coordination powered by Aria.
New Features Enabled by This Update:
Slack-Based Conflict Resolution
When calendar conflicts occur during interview scheduling, Guide can coordinate directly with interviewers inside Slack to help resolve conflicts faster.
Instead of recruiters or coordinators manually tracking down interviewers, Guide and Aria can assist directly within existing Slack workflows.
Aria-Drafted Slack Messages
Aria can draft Slack messages for recruiting coordinators to send to interviewers when scheduling conflicts arise.
Examples include:
Requesting interview availability changes
Asking interviewers to move interviews
Coordinating alternative scheduling options
Clarifying interviewer availability constraints
Organizations can choose whether:
Messages are sent by the Guide bot, or
Messages are attributed to the coordinator using Slack attribution
(via Guide)
Note: A human will always review these options with Guide's human-in-the-loop workflow.
Conversational Scheduling Coordination
Aria can process interviewer responses directly inside Slack conversations.
This allows Guide to:
Read interviewer replies
Understand availability updates
Detect agreement or conflicts
Update interview panel proposals automatically based on responses
For example:
Aria detects a scheduling conflict
Guide drafts a Slack message to the interviewer
The interviewer replies with updated availability
Aria processes the response
Guide updates the interview panel proposal automatically
This significantly reduces manual back-and-forth coordination work for recruiting teams.
Requested Slack Permissions
channels:history
What this permission allows
Allows Guide to receive notifications and read messages in public channels where the app is participating.
Why Guide requires it
Guide must be able to process interviewer and coordinator responses in Slack conversations in order to support conversational scheduling coordination workflows.
Without this permission, Aria cannot understand or act upon freeform Slack replies.
Example use cases
An interviewer replies with updated availability
A recruiter asks Aria to modify a proposed panel
A coordinator responds to a scheduling conflict thread
channels:join
What this permission allows
Allows Guide to join public Slack channels when requested by users.
Why Guide requires it
Some organizations choose to coordinate scheduling workflows in shared recruiting or hiring channels.
This permission allows Guide to participate in those channels when explicitly configured by users.
channels:read
What this permission allows
Allows Guide to view basic metadata about public channels.
Why Guide requires it
Guide uses this permission to provide user-friendly channel selection during workflow setup and Slack configuration.
chat:write.customize
What this permission allows
Allows Guide to send messages:
As the Guide bot (default), or
On behalf of a user with attribution
(via Guide)
Why Guide requires it
Scheduling coordination often works best when interviewers can clearly see which recruiter or coordinator initiated the request.
This permission enables more human and context-aware coordination workflows.
Important note
This functionality is optional. By default, Guide sends messages as the Guide bot.
chat:write.public
What this permission allows
Allows Guide to send messages into public channels where the app has access.
Why Guide requires it
This enables Slack-based scheduling coordination workflows in public recruiting or hiring channels selected by users.
groups:history
What this permission allows
Allows Guide to receive notifications and read messages in private channels where the app is installed.
Why Guide requires it
Guide must be able to process interviewer and coordinator replies inside private scheduling coordination channels.
im:history
What this permission allows
Allows Guide to receive and process messages in direct messages (DMs) between users and Guide.
Why Guide requires it
Many scheduling coordination workflows occur directly between coordinators and interviewers in DMs.
Guide requires this permission so Aria can process responses and continue coordinating scheduling workflows intelligently.
mpim:history
What this permission allows
Allows Guide to receive and process messages in group direct message conversations.
Why Guide requires it
Some organizations prefer scheduling coordination to happen inside shared group conversations involving:
The recruiter or coordinator
The interviewer
Guide
Guide must be able to process replies in these conversations to support conversational automation.
mpim:read
What this permission allows
Allows Guide to access metadata about multi-person direct message conversations.
Why Guide requires it
Guide uses this permission to support group DM-based coordination workflows initiated by users.
mpim:write
What this permission allows
Allows Guide to create and participate in group direct message conversations.
Why Guide requires it
This enables collaborative scheduling coordination workflows where users can:
Monitor scheduling conversations
Intervene manually if needed
Collaborate directly with Guide and interviewers
Security & Privacy Notes
Guide only uses these permissions to support interview scheduling and recruiting coordination workflows.
Guide only processes messages in conversations where the app is participating.
Organizations control where and how Guide is used within Slack.
Public channel and group DM workflows are optional and configurable.
User-attributed messages are clearly labeled
(via Guide).Guide does not use these permissions for unrelated Slack monitoring or general employee communications.
Frequently Asked Questions
Does Guide read all Slack messages?
No. Guide only processes messages relevant to scheduling coordination workflows and conversations where the app is participating.
Why does Aria need message history permissions?
Aria must be able to process interviewer and coordinator responses in order to:
Understand availability updates
Resolve scheduling conflicts
Modify interview panel proposals
Continue conversational scheduling workflows
Without message history access in participating conversations, Aria would not be able to respond intelligently to Slack replies.
Can our organization restrict how Guide uses Slack?
Yes. Organizations control:
Which channels Guide can access
Whether public-channel workflows are enabled
Whether group DM workflows are used
Whether user-attributed messaging is enabled
Is user-attributed messaging optional?
Yes. By default, Guide communicates as the Guide bot. Messaging attributed to users via chat:write.customize is optional and configurable.