Atlassian Team members are employees working across the company in a wide variety of roles.
October 3, 2025 edited
My guess is that it has to do with the bot account you created when setting up the Rovo Slack app:
When you add Rovo to your Slack, you’ll need to create a bot account that determines the permissions Rovo uses in public channels. Make sure you only give the bot access to information or pages that you are comfortable with anyone in your organization accessing.
Make sure you have the permissions for that bot account configured such that it has access to a subset of data that you are comfortable with all Slack users querying.
The account used to setup Rovo in Slack has access to the Confluence workspaces but still the same.
We decided to individually add the Confluence pages to the instruction. But I do not think this is feasible if we have quite a number of pages in the Confluence workspaces.
Would you have other suggestions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @noreen_magsumbol — I know from our accelerator that you got this working! For anyone following along, this behavior is expected for now. Rovo’s Slack app still can’t tap into your full Confluence knowledge base the way it can inside Jira, Confluence, or the Chrome extension. Even with the right bot permissions, Slack-triggered agents won’t reliably read indexed KB content. Until Atlassian expands support, the best workaround is adding the key pages or spaces directly into your agent’s instructions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.