No, we handle Slack Enterprise Grid migrations automatically. Slack send an event to our application when an Enterprise Grid migration begins and ends, and we use this as a signal to pause user syncing.
Grid migrations can result in user IDs changing, so we pause our user syncing process during the migration. We do this because Slack is often a source of truth for authentication, and these migrations can sometimes result in user IDs changing. By pausing the user syncing, we eliminate the risk of users becoming deactivated during the process and losing access to incident.io.
Do you automatically update user IDs if they change?
Yes. When a Grid migration is taking place, we attempt to exchange the old user ID every time a user signs in. We also run a “bulk exchange” of user IDs every day. For both of these processes, we use Slack’s migration.exchange API endpoint.
Grid migrations should involve a step where the incident.io Slack application is re-installed, either at the Grid level or to the individual workspace. We handle both of these cases transparently: however, if you want to install us at a Grid level and have another workspace already using incident.io, there is some configuration we need to do on our side to map the workspaces to the correct accounts on our side.See this article for details on which plans can install incident.io at the Grid level.
