Hi @Michalis Motis, on the admin side there is exactly one OAuth revoke, and it isn't surgical. You uninstall the app from the Connected apps screen, and for a 3LO app like this one "the Uninstall button revokes all users". All of them, at once. No admin control drops a single person's grant. Atlassian's line is that "a user can revoke their app grants at any time using their own connected apps screen", so they can drop it themselves. You can't do it for them. Either an org admin or a site admin can run the uninstall, though an app admin can't, since app admins have no access to Atlassian Administration.
To cut OAuth 2.1 connections without removing the app, use the domain controls. Atlassian is explicit that they only bite on OAuth: "You can only block domains for AI tools that use OAuth 2.1, but not when they use API tokens to access your organization." Go to Atlassian Administration, Rovo, Rovo MCP server, then deselect Allow Atlassian supported domains, or delete whichever ones you added yourself.
OAuth 2.1 is the default, but an org can additionally switch on API token auth, and a token is a separate credential none of that touches. Those get revoked under Insights, API token activity. Org admin only for that one, and the delete is permanent. Given you're on JSM, check whether yours is on, because the JSM tools only run over API tokens.
Control Atlassian Rovo MCP server settings
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.