Skip to main content

​
Slack Account Permissions

Permissions RequiredYou must be an Owner or Admin user in order to install Slack on your Rootly organization account.You must also have admin rights to your Slack account.
Rootly will ask you the following Slack permissions during installation:

​
Bot Scopes (Standard Integration)

Core Permissions:
  • bookmarks:write: Add bookmarks to incident channels for quick access to important resources.
  • channels:manage: Create public dedicated Slack channels for incidents.
  • channels:read: View basic information about public channels in a workspace.
  • chat:write + chat:write.public: Write messages in your dedicated incident Slack channels and respond to different actions.
  • commands: Add /rootly and /incident Slack shortcuts.
  • files:read: Save files associated with pinned or reacted messages to the Rootly timeline.
  • files:write: Upload files (like console output) directly to Slack through workflows. We will never delete files in your Slack workspace.
  • groups:read: View basic information about private channels that Rootly has been added to.
  • groups:write: Create private Slack channels for sensitive incidents (e.g., security).
  • pins:read: Add pinned Slack messages to your incident timeline.
  • pins:write: Pin important messages in incident channels.
  • reactions:read: Add Slack messages to your incident timeline through reactions of your choice.
  • reactions:write: React to your messages when successfully added to your incident timeline.
  • usergroups:read: View user groups in a workspace (e.g., aliases to invite @security people directly).
  • usergroups:write: Manage on-call user groups for scheduling and rotation.
  • users:read + users:read.email: View email addresses of people in a workspace for one-click invitations. We will never invite them on your behalf.
  • users.profile:read: Display user’s full names (Firstname + Lastname) instead of Slack usernames.
AI & Assistant Features:
  • app_mentions:read: View messages that directly mention @rootly in conversations.
  • channels:history: Read message history in public channels for AI-powered features.
  • groups:history: Read message history in private channels for AI-powered features.
  • assistant:write: Enable Rootly AI Assistant capabilities.
  • im:history: Read direct message history for AI Assistant interactions.

​
User Scopes

  • usergroups:write: Required for on-call user group management (user permission).

​
Additional Scopes for Slack Enterprise Grid

​
Additional User Scopes (When Bot Cannot Create Channels)

In some Slack workspace configurations, only workspace admins/owners can create channels. When this restriction is in place, Rootly will request these additional user scopes from admin/owner users to create channels on their behalf:
  • channels:write (user scope): Create and manage public channels on behalf of admin/owner users.
  • groups:write (user scope): Create and manage private channels on behalf of admin/owner users.

​
Installing Slack on Rootly

Locate Slack on on the Integrations catalogue and select Setup.
Document Image
You’ll be presented with the following installation page. Double check that you’re installing the correct workspace (dropdown in the upper right hand corner) before you confirm the installation by selecting Allow.
Document Image

​
Installing Slack Enterprise Grid on Rootly

You will need to be a Slack Workspace Owner to complete the setup.
If you use Slack Enterprise Grid where you have multiple Slack workspaces, your installation instructions will differ slightly. The following video will walk you through the steps to install Slack Enterprise Grid.

​
Re-Claiming /incident Command

During the transition to Rootly, you may experience issues where Rootly’s bot claims the /incident Slack command from your existing bot. When multiple bots use the same command, Slack will always invoke the one that was installed most recently. If this behaviour interrupts your transition, you can follow the following instructions to reclaim the /incident command from Rootly. This is the safest method as it does not result in a blackout period where your old bot is unusable.
  1. Ensure that you already have Rootly installed on your Slack workspace.
  2. Update your old bot’s slack command from /incident to a placeholder (e.g. /incident-1).
  3. Save the change.
  4. Change the command of your old bot back to /incident.
Slack recognizes an update to the command as a new installation. This should make your old bot the “most recently installed bot” that uses the /incident command.

​
Option 2

If Option 1 does not work, you can try this option. There will be a brief blackout period where your old bot will be unusable.
  1. Ensure that you already have Rootly installed on your Slack workspace.
  2. Uninstalling your old bot.
  3. Reinstall your old bot back.
This effectively the same as Option 1 as the reinstallation reclaims the /incident command from Rootly.

​
Enterprise Grid Consideration

If the issue persists after trying the above solutions, check your installation scope. If Rootly is installed at the Slack organization level (Slack Enterprise Grid), then you must also reinstall your old bot at the Slack organization level, not just at the workspace level.

​
Uninstall

You can uninstall this integration in the integrations panel by clicking Configure > Delete.