Qooper leverages only delegated permissions—meaning it acts on behalf of an authenticated user and only within that user’s allowed scope. It does not access data outside what the user can already reach.
These are least‑privilege by design—Qooper only requests what’s needed for sending updates to selected channels by admins. By default, Qooper’s permissions do not include broad access. This limits risk exposure and simplifies compliance.
Below is an overview of each permission scope and why it’s required for the integration to function properly.
Permissions Needed
These permissions allow Qooper to identify channels, groups, and teams in your Slack workspace where program communications can be sent.
channels:read
Description: View basic information about public channels in a workspace.
Request Reason: Allows Qooper to list public channels so admins can connect Qooper to one for sending updates about program events and progress.
groups:read
Description: View basic information about a user’s private channels.
Request Reason: Allows Qooper to list private channels so admins can connect Qooper to private spaces for sharing program updates.
team:read
Description: View the name, email domain, and icon for workspaces a user is connected to.
Request Reason: Enables Qooper to identify the correct Slack workspace for integration and ensure updates are sent to the right organization.
usergroups:read
Description: View user groups in a workspace.
Request Reason: Allows Qooper to list user groups (e.g., mentors, mentees, HR teams) for targeted communication setup and program notifications.
chat:write
Description: Send messages as @Qooper.
Request Reason: Enables Qooper to send updates in private channels as the Qooper bot to inform users about upcoming events, milestones, and progress.
chat:write.public
Description: Send messages to channels @Qooper isn’t a member of.
Request Reason: Allows Qooper to post updates in public channels without needing manual invites, simplifying setup for workspace admins.
im:read
Description: View basic information about direct messages that Qooper has been added to.
Request Reason: Allows Qooper to identify 1:1 message threads and send relevant updates directly to users.
im:write
Description: Start direct messages with people.
Request Reason: Enables Qooper to initiate 1:1 conversations with participants, sending reminders, check-ins, or progress messages.
Why These Permissions Are Needed
Qooper’s Slack integration automates communication for mentoring and employee development programs.
These permissions enable:
-
Automated Notifications: Program updates, event reminders, and engagement nudges are automatically delivered through Slack.
-
Simplified Admin Setup: Admins can select Slack channels or user groups for messaging without manual bot configuration.
-
Seamless User Experience: Participants receive mentoring updates and reminders directly where they collaborate — in Slack.
Next Steps
Once these permissions are authorized in your Slack workspace, Qooper will automatically send relevant updates and reminders directly to your team in Slack — ensuring higher engagement and simpler communication.