We have an app called BuzzSpot (App ID: 3418978) which our end users are testing.
What we found is that even though the users are enabled for the scopes the app requires, they are unable to connect to the app and receive the following error message:
“Authorization failed because you don’t have permissions to authorize the scopes required by the app. Please contact your super admin to get the necessary permissions.”
If the user is giving Super Admin access then they are able to install the app. Once installed, it continues to work even if they are removed as Super Admin.
Since the users have permission to access the scopes required the app, why do they need to be made Super Admins before they can install the app?
Hey, @SShah91 Looking at support tickets for similar errors, I see that there are some scopes that are only available to Super Admins. This includes things like file-manager-hidden-files-read, properties-settings-write, and crm-public-export, for example.
If you have a moment, you can spin up an App Test account from your dev portal, set up to record a HAR file, and then walk through the installation process until the error appears. You can take your saved HAR file and analyze it. You can also share the result here or with me via DM. It typically looks lie this:
{
“status”: “error”,
“message”: “Authorization failed because you don’t have permissions to authorize the scopes required by the app. Please contact your super admin to get the necessary permissions.”,
“correlationId”: “XXXXXXXXXXXX”,
“category”: “MISSING_PERMISSIONS”,
“subCategory”: “AuthorizationErrorType.USER_MISSING_PERMISSION”
}
Additionally, I can try to track down what the correlationId is telling us.
Lastly, you can try removing scopes or making some `optional` as part of your testing to see if you can narrow down the offending scope group.