Skip to main content
There are just 3 steps :
  1. Sign Up (via Slack)
  2. Select your integrations
  3. Add incident.io to Slack
A couple of notes You will need a Slack admin to install us due to Slack’s permissioning model. The app uses /inc and /incident as slash commands. If you already have an app installed or install one after ours that uses either of these commands, then just note that Slack will default to using the most recently installed app when that command is run.

​
1. Sign Up (via Slack)

From the sign-up page, you’ll be asked to ’ Sign in with Slack ’. Get started with incident.io onboarding step 01 with a Sign in with Slack button We’ll create an account for you and store some basic information, like your name and avatar. We’ll also ask for a restricted set of permissions in order for incident.io to work. Read more in our Security FAQs. Slack permission screen listing what incident.io can view and do, with Allow and Cancel

​
2. Select your integrations

This is just so we get a sense of the most-used tools in our user base. We explain how to set up your integrations → here. Onboarding step 02, Tell us about your organisation, with integration tiles to select

​
3. Add incident.io to Slack

Last step: ’ Add incident.io to Slack ’. Onboarding step 03, Add incident.io to Slack, with an Add to Slack button When you’ve done this, we’ll create you an #incidents channel, and install the incident.io app into your workspace. …all done! Everyone in your Slack workspace can now use incident.io — they simply need to go through the same ‘Login with Slack’ flow. They will not be asked to ‘Add incident.io to Slack’ - that step only happens once. Let’s go declare some incidents!
Having issues installing? Email our support team directly or jump on a 1:1 call and we’ll get it sorted in no time!

​
Troubleshooting

Signing up to incident.io is restricted to those using a corporate or company email address. Our product is designed for companies rather than individuals, and this helps us avoid abuse.If you see a sign-up error, try again using your company email address. If you’re still having trouble, get in touch.
incident.io has two slash commands: /inc and /incident. Slack only lets one application listen to a particular command, so if you have an existing app that uses either of these, incident.io will take over those commands when installed (the most recently installed app wins).Installing incident.io won’t remove the other application. If you’re migrating from an app that uses /inc and want to avoid disruption, re-install that application after installing incident.io.You can find a cheatsheet of all /inc commands here.
incident.io needs to create channels in your Slack workspace — a main #incidents announcement channel during install, and individual #inc-... channels for each incident. If your workspace restricts channel creation, installation will be blocked.You’ll need a workspace admin to fix this.Option 1: Allow all members to create channelsGo to your Slack workspace settings and set People who can create public channels to Everyone except guests. Then select “I’ve changed channel creation permissions” and complete the installation.Slack workspace menu with Settings & administration expanded and Workspace settings highlightedSlack Permissions tab, Channel Management section, with People who can create public channels highlightedLet's add incident.io to Slack screen with I've changed channel creation permissions selectedOption 2: Use a Slack admin accountIf you’d prefer to keep your channel management settings, you can connect a Slack admin user for incident.io to use when creating and managing incident channels. We recommend creating a dedicated user account for incident.io, as this user will appear as the channel creator and will appear to archive channels.Once you’ve created the user, log in to Slack as that user in your browser, then select “I’d like to use a Slack admin user” and click “Continue”.Let's add incident.io to Slack screen with I'd like to use a Slack admin user selected
This error appears when you try to sign in with a Slack Enterprise (organization) instead of a Slack Workspace.To fix it, click the dropdown in the top right of the Slack sign-in screen and select a Workspace rather than an Organization.Slack error page showing Something went wrong when authorizing incident.io and error details no_bot_scopes_requestedSlack sign-in dropdown open, listing organizations above Other workspacesIf you don’t see any Workspaces, log in to Slack in your browser first, then try again.
This usually means the incident’s Slack channel has been archived. There are two ways to resolve it:Option 1: Unarchive the channelIn Slack, click the channel name and select “Unarchive channel” in the Settings tab. Then refresh the incident page.Slack channel panel for #inc-112-merlot-grouse on the Settings tab, showing Unarchive this channelOption 2: Store incident channel messages in incident.ioUnder Settings > Security, enable “Store incident channel messages”. This keeps a copy of pinned messages in incident.io so you can review the timeline even after a channel is archived.To import messages from already-archived channels, enable privileged Slack access. incident.io will temporarily unarchive those channels to import the messages, then re-archive them.