Can't Revoke a Connected App's Access on X

Is this your situation?

The short answer

What you see, and why

Check these first

• Check the connected apps list again.Verify: Check whether the app you revoked still appears in the list.
• Check for a confirmation message.Verify: Check whether the screen showed a message after you selected revoke.
• Check whether you revoked the correct app.Verify: Check the app name against the one with the access problem.
• Check which account you were signed into.Verify: Check that the account shown in settings is the one with the access problem.

How X handles this

• No bound claim describes how X processes a revoke request for a connected app.
• You attempt to revoke an app and want to know whether it still appears afterward.
• You want to know whether a third-party app can still read or post after you revoke it.
• You want to know whether the access you see comes from a connected app or from delegate access.

Which path applies to you?

1. Does the app still appear in your connected apps list after revoking? No bound claim states what this means for the app's access.
2. Can the app still read or post after the revoke attempt? No bound claim confirms whether this indicates the revoke did not take effect.
3. Did you revoke access for the correct app? Check the app name in the list against the one causing the problem.
4. You are unsure whether the access you see is from an app connection or from someone with delegate access. Check the listing against delegate access to see which kind of access applies.
5. Is a former employee's access the underlying concern rather than an app connection? Check your connected apps and sessions list for the employee's name or device.

Step by step: finding the cause

1. Locate the app you want to remove. Find the specific app connection you intend to revoke.Confirm: Check that the app name matches the one causing the problem.
2. Select the revoke option for that app. You want to remove this app's connection to your account.Confirm: Check whether a confirmation message appears on screen.
3. Reload the connected apps list. Refresh the page to see the current state of the list.Confirm: Check whether the app still appears in the list.
4. Test whether the app can still act on the account. Check if the app can still read or post after the revoke attempt.Confirm: Check the app's own interface for a connection error.
5. Select revoke again for the same app. You want to see whether the list changes this time.Confirm: Check the list again for the app's presence.
6. Compare the entry against a delegate listing. You want to see whether the entry sits under app connections or under delegates.Confirm: Check whether the name appears under app connections or under delegates.
7. Note the account you were signed into during the attempt. Confirm you worked from the account that has the access problem.Confirm: Check the account name shown in the settings header.

Common mistakes

• Revoking the wrong app. You select a similarly named app instead of the one with the access problem.Why it happens: No bound claim explains why app names might be confused in the list.
• Expecting an immediate visible change. You expect the list to update the instant you select revoke.Why it happens: No bound claim states how the list behaves after a revoke action.
• Assuming the app lost all access. You assume revoking removes every form of access the app had.Why it happens: No bound claim distinguishes between delegate access and app connection access.
• Checking the wrong account. You review the connected apps list on an account other than the one with the access problem.Why it happens: No bound claim explains why the wrong account might be checked.

Quick reference

Keeping track of who has access