Manage deactivated members' apps and integrations

When member accounts are deactivated, some apps they've installed (whether third-party or custom) will automatically disable. Some features may remain active (bot users, slash commands, incoming webhooks, etc.), but apps that require member-specific permissions will disable entirely.

However, we preserve certain apps regardless of the installing member's account status — as we know losing access to an essential app your team relies on is a bad experience.

Tip: When member accounts are deactivated, API tokens are revoked as well. Any user-specific permissions granted by a member will no longer be available.


Reactivate apps and integrations

Workspace Owners (and other members with permission to manage apps) can reactivate disabled apps:

  1. Open the list of deactivated apps and integrations.
  2. Find the uninstalled app/integration in the list and click View.
  3. For disabled apps, select Install and configure the app to restore service.
    For disabled integrations, click Enable.

Internal integrations: Deactivated members will lose the ability to collaborate. If the sole app collaborator has lost access, a Primary Owner can contact us to request a transfer for the internal integration(s).

Bot integrations: When they're re-enabled, their corresponding tokens are automatically regenerated. Once re-enabled, you'll need to update any code that references the old bot token.

 

Preserved apps built by Slack

We plan to add more apps to this list over time, so be sure to check back periodically for new additions.

  • Airbrake
  • Bitbucket Cloud
  • CircleCI
  • Datadog
  • Email
  • Giphy
  • Google+ Hangouts
  • Jenkins CI
  • Jira Server Alerts (Legacy)
  • Logentries
  • New Relic
  • Papertrail
  • Pingdom
  • RSS
  • Runscope
  • Semaphore
  • Skype
  • Statuspage
  • Travis CI
  • Visual Studio Team Services
  • Whereby

Who can use this feature?

  • Workspace Owners (default)
  • FreeStandard, and Plus plans