Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Our Slack bot says it is missing permissions after an update

Short answer

Slack returns missing_scope when the token does not hold a permission the call needs. Scopes are additive: adding one means going through the install flow again, and they cannot be removed from an existing token without revoking it. Check the permissions the feature needs, then have an admin approve the update.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The bot threw missing_scope after a new feature was added.
  • Slack asked an admin to approve something the app now wants.
  • A feature works for some users and not for others.
  • Posting works but reading history, files or users does not.
  • The developer says the app must be reinstalled the app.

Why does this happen?

  1. The feature needs a scope the token never had

    Slack's reference says the token used is not granted the specific scope permissions required, which returns missing_scope. For example, posting needs chat:write, and posting to public channels without joining needs chat:write.public.

  2. Scopes only grow

    Slack documents that going through the install flow again adds new scopes to the existing set, that it is not possible to downgrade a token's scopes, and that scopes cannot be removed from an existing token without revoking it entirely.

  3. Bot and user tokens carry different scopes

    Bot scopes and user scopes are requested separately, and the two token types behave differently. A feature that acts as a person needs user scopes, not bot scopes.

  4. Optional scopes may be missing by design

    Slack says an app can mark scopes as optional, and that it must handle a missing optional scope gracefully, for example by handling missing_scope errors.

  5. The app was updated but not reinstalled

    The scopes on a token are what the install granted at that time. Code that expects a new scope will fail until the app is installed again with it, and the Slack response header x-oauth-scopes lists what the calling token holds today.

What can I do about it today?

  1. Ask what feature changedA new feature or a changed command is usually what asks for a new permission.
  2. Ask the developer for the exact scope nameIt appears in the error, for example missing_scope with the needed scope. Ask them to explain in plain words what it allows.
  3. Let an admin read the approval screenWhen Slack asks for permission, read what it grants. If a scope sounds broader than the feature needs, ask why before approving.
  4. Do not approve on a rushed callA bot with extra scopes can read or write more in your workspace. Take a day to decide if needed.
  5. Keep a list of the app's scopesAsk the maintainer for the current list and the reason for each. It is useful for any later security review.

When should I bring someone in?

  • The error continues after the admin approved the new permissions.
  • Nobody can say why the app needs the scopes it asks for.
  • The app was written by someone who has left and nobody has its code.

How do I handle it?

  1. Map each feature to the least scopeI list the Slack calls the app makes and match each to the narrowest scope Slack documents for it.
  2. Check what the token holds todayI read the scopes the live token has and compare them with what the code now needs.
  3. Request only the gapThe install is re-run with just the missing scopes, and the admin sees a short list with a reason for each.
  4. Handle a missing scope gracefullyThe code reports a clear message instead of failing silently, so the next gap is spotted at once.
  5. Record scopes and ownersI leave a short note of the scopes, why each exists and which admin approved them.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can a scope be removed a scope later?

Slack says scopes cannot be removed from an existing token without revoking it entirely. Plan the list before approving.

Does the app need to be reinstalled the app?

Slack describes scopes as additive when the install flow is run again. Ask your developer which path applies to your app.

Is a new permission request a sign of a problem?

Not by itself. New features need new scopes. Ask what the feature is and whether the scope is the narrowest one that works.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.