We have Rovo enabled on our Atlassian account and it had access to Confluence. We added Confluence to our Rovo blocklist but it seems Rovo still has access to the Confluence instance.
We know this is the case as we also have Claude connected to Rovo and Claude can access our Confluence through Rovo even though Rovo should not have any access to Confluence. Does this mean that the blocklist is only a remove the "Ask Rovo" button and that access is actually still there when it shouldn't be?
Hi @J_ Houston
putting Rovo on the Blocklist for an App only removes UI elements in that specific App. It doesn't affect the Teamwork Graph which is the underlying data graph that Rovo as well as MCP/CLI integrations use to access data.
If you block Rovo from all Apps, nobody will be able to use Rovo Chat or Agents.
External AI integrations through Rovo MCP or Teamworkgraph CLI will still be able to access all data.
There are separate access controls for MCP and CLI on admin.atlassian.net where you can block read-access to each Atlassian App separately, that affects all integrations though.
Good to know: If Rovo is blocked from absolutely all Apps, both the Rovo browser extension and Rovo Desktop will stop working for that site as well. The "Chat" App will disappear also.
Thank you for this. I didn't want to go nuclear but had to in turns of shutting all access down.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey. Iāve just had something similar. Adding to the blocked apps list removed rovo icon from Jira and confluence.
but the connectors from Claude / gpt are still connected. I believe this is by design though. So you can still use Claude :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.