Rovo can not be installed on Slack: Unapproved permissions requested: links:read

[Rojahn Ahmadi]

Hi, 

I'm an admin both for Slack and for Atlassian, but simply can not get Rovo installed on Slack, following the instructions (https://rovo-integrations.atlassian.com/slack/onboard/welcome as referenced in https://support.atlassian.com/rovo/docs/using-the-atlassian-rovo-slack-app/).

I was on that screen:

"Install the Rovo App for Slack
Before you connect your site, you’ll need to install the app. We’ll redirect you to Slack.
> Add to Slack"

which, when clicking on that button, leads to that screen:

"Atlassian Rovo
Atlassian Rovo could not be installed.
It looks like something has gone awry. Don’t worry it’s not your fault, but you won’t be able to install Atlassian Rovo at the moment.

Error details
Unapproved permissions requested
links:read"

I don't see how I can change such permissions. How are you able to install Rovo?

Adding / removing the Rovo app from the Slack market place separately did not change anything, other than getting Rovo on Slack which is not able to reply to any message.

Best,

Rojahn

[Dr Valeri Colon _Connect Centric_]

Welcome to the community @Rojahn Ahmadi This error is typically caused by Slack's app approval policies rather than a Rovo configuration issue. The links:read permission is a Slack scope that some organizations restrict through app governance or admin approval workflows. Verify in Slack Admin → App Management whether unapproved scopes require review and whether Atlassian Rovo is allowed under your organization's app policies. If the workspace is part of an Enterprise Grid, an Org Admin may also need to approve the app. Atlassian Support may need to investigate if the scope request is not being properly recognized.

[Rojahn Ahmadi]

Thank you @Dr Valeri Colon _Connect Centric_  for checking that!

However, look at the permissions actually officially listed below. This indicates to me that there is a bug as it’s requesting a permission it did not officially declare for the app:

[Rojahn Ahmadi]

And I don’t see anything relevant to set in settings. I would approve it anyway, but even when disabling app approval the error would stay.

[Dr Valeri Colon _Connect Centric_]

At this point @Rojahn Ahmadi I’d recommend opening an Atlassian support ticket and including the exact error, screenshots, and your Slack workspace type (Enterprise Grid vs. standalone workspace). This looks like something Atlassian’s Rovo team will likely need to investigate. I’d also be interested to hear if anyone else can reproduce the same links:read error.

[Thomas Henney]

@Dr Valeri Colon _Connect Centric_ Just to echo that I am getting the exact same results as @Rojahn Ahmadi (link:read error and app not having requested that permission)

[Dr Valeri Colon _Connect Centric_]

Thanks @Thomas Henney — that helps confirm this is reproducible and the screenshots were helpful as well @Rojahn Ahmadi . Since links:read isn’t showing in the published permission list but Slack blocks the install for that scope, this looks less like workspace configuration and more like a mismatch in the Rovo Slack app/OAuth install flow. Thomas would you mind opening an Atlassian Support ticket as well so they can route it to the Rovo Slack integration team.

Unfortunately, I still haven't found a reliable workaround if the install itself is failing with the links:read scope. You could try the good ole 'unplug it and plug it back in'.

[Arkadiusz Wroblewski]

Hello and Welcome to Atlassian Community @Rojahn Ahmadi 

Is app aproval enabled in your Workspace ?

You can check it here: Slack Admin → Apps and workflows → App requests / Approved apps

I found some old ancient similiar problem Solved: Error when connecting to slack

Best,

Arkadiusz🤠

[Rojahn Ahmadi]

Hi Arkadiusz,

Thank you very much checking! 

If you mean the setting "Require approved apps": Yes, it is enabled to require admin approval. I'm one of the admins and would have permission to approve. However, even if I disable that setting temporarily, the error stays.

The link you've posted: Unfortunately, it does seem like it was a bug back then that was fixed by Atlassian. It does look to me like another bug, but then I should not be the only one who has that issue - nobody would be able to get started with Rovo on Slack.

Best,

Rojahn

[Arkadiusz Wroblewski]

@Rojahn Ahmadi 

Did you have Enterpise by chance ?

[Rojahn Ahmadi]

No, we are on Slack Pro.