Rebekka Heilmann (viadee) Community Champion

Where does the Automation button move to? I can't see the familiar "zap" icon.

Hi @Christopher Yen currently, nothing Rovo related is exposed via API endpoints. We are all waiting impatiently for Rovo Agent endpoints so we can retrieve information on Agent configs as well as invocations. Only if the Agent is acting with its own account. This is a new option now that Agents are becoming autonomous.…

I agree with you, Laura. Rovo views are especially a problem for open-by-default Confluence setups. Rovo may surface content that has the right keywords but is completely irrelevant. If that happens quite a lot, these pages seem to be active even though they may be a candidate for archiving. Currently there is no way of…

MCP and CLI can be blocked from Cloud Administration. Manage Atlassian MCP server | Atlassian Support Rovo Mobile App can be blocked through mobile policies. Mobile App Management for Atlassian mobile apps | Atlassian Support Browser Extension and Desktop apps need to be managed through Device/Asset management. The Apps…

Great feature request @Martina Guth I am managing an Atlassian Knowledgebase and people using Rovo in that space will - per default - get answers from Atlassian's support docs rather than my knowledgebase. That is fine for some cases, but there is a reason why I have a whole Confluence space on company specifics :D

@Gisela da Silva Rodrigues there is not and announcements - as always - weren't super clear (unless you read this whole article). I was also surprised on one site. It was part of the bundled release this week. No permissions have changed with the switch but it is recommended to update the roles to your liking asap so…

I know that the Atlassian Team is working on cross-site Rovo features. Units (https://www.atlassian.com/roadmap/cloud/create-organizational-structure-to-enforce-data-boundaries?search=unit&p=7a6ee076-60) will each have their own Teamwork Graph that spans across all sites in a Unit. Not sure if that capability will be added…

I second @Tomislav Tobijas here! I've just discussed the use case of: Everyone should see the space but only be able to edit very specific pages, where they've been added to. Currently, they need Edit-Permissions everywhere (and we need to create an Edit-only role in between Viewer and Collaborator) and all other pages…

Es gibt keinen Menüpunkt "löschen". Die UI hat sich seit dem Artikel aber auch schon mehrfach geändert. Unter admin.atlassian.com > Rovo > Rovo access kann der Zugriff auf Rovo in den verschiedenen Apps gesteuert werden. Siehe What does blocking Rovo access actually do and not... - Atlassian Community

@Darryl Lee I agree that the user flow isn't ideal (but when is it ever). Users are getting pushed to add a connection, even though the connection isn't setup by the admin. On the other hand they are not notified to connect once the connection is established in the Org. I do like that Atlassian is quite conservative with…

I've been saying this for months and months... but now it's really time to get your governance in order. Both Rovo Governance & Data governance. As TWG access costs credits too, old & irrelevant data now costs real money.

I'd like to try and clarify some of these answers 1. All Teamwork Graph Data (which is In-App data and its connections) respect the Data residency settings, so yes 2. LLMs vary, check List of Data Subprocessors | Atlassian for the full list. Most LLMs are hosted in the US! So no, they are not UK based and Data in…

@Hector Vazquez Permissions for Rovo Agents and Creating Apps in Rovo Studio are already managed in the Studio permissions today! they are separate from AI access settings. Rovo agent permissions and governance | Rovo | Atlassian Support You can remove Rovo Studio App access all together or adjust the Studio permission…

I hope next up are some insights for each individual users: How many credits did my request just use? How many credits have I used this month? And then some admin controls related to that: set a max. credit limit per user (group).

There used to be different wording: Rovo connector and Teamwork Graph connector. Are they one and the same (now)? 

Fantastic to see Luna in the selection now! by far my favorite model currently.

Hi @Alice Brissman assuming you are working on a Data Center environment, there is no distinction between deleting own content and deleting any content in the space. You need the "delete page" permission in order to do so. Space Permissions Overview | Confluence Data Center 10.2 | Atlassian Documentation If the "Delete"…

Hi @Louise Harker Guest Accounts only work for external users. On a technical level, it's limited to non-managed accounts, but the license agreement specifies that as well. Confluence and Jira licenses do not distinguish between read/write access, so there is no licensing loophole or feature that Atlassian offers directly.…

Looks like it's resolved and all back to normal

Hi @Amy Hargreaves - welcome to the Community, I've noticed this too and opened a Support request on friday. There is an incident (not visible on status page) and the Atlassian team is working on it. The option should re-appear where you've found it before and I'll update you here as soon as I hear back.

In my experience, a lot of content is kept alive to explain decisions or look up something for future projects working on similar things. Rather than keeping all these documents in an "archive" folder so regular users still find it, have Rovo manage a decision record, lessons learned etc. where all the relevant information…

For the web search part it's important to distinguish, especially with recent reports around prompt injection. The Web search toggle enables Rovo to send search request to the www. Regardless of that toggle, Rovo can always access websites that a user explicitly names and pull the data from that one url directly. It's…

Yes! To clarify: Almost all new features will have some form of feedback button (mostly a small megaphone icon) built into the product itself. The feedback there will be sent to the correct product team. Feature requests on here rarely reach the correct person as not a lot of Atlassians are reading Q&A on here, sometimes…

@Greg D totally agree! Unfortunately, we all know how most feature requests end and I don't have a direct Atlassian contact to anyone working on Service Accounts.

@Karin_Gleichauf does the pdf has a full text layer? If there is no text layer (so basically image only) I've seen Rovo hallucinate the content as well. Not tested docx but could be that that's not supported yet.

Thanks @__ Jimi Wikman Someone at the Freiburg ACE mentioned this and I was very confused at first and annoyed that blocking Rovo would not block the data access. So I've digged into it and if you separate Rovo from the TWG is sort of makes sense.

if you are * are logged in with the correct email * sure that you have an active Jira license * sure that you are Admin of the space * AND that the Admin role gives you actual Admin permissions and permission to browse work (which it should in team managed spaces) I wouldn't know whereelse to look to be honest. I'd suggest…

Hi @Dmytro Admin_test thanks for confirming. I'd lean on @Gabriela - LeanZero 's explanation. [JSDCLOUD-18831] Customers cannot connect to sharepoint via JSM Customer Portal - Create and track feature requests for Atlassian products. already describes the problem outside of Rovo Agents.

The space in the first screenshot is a team managed Software space, not a JPD space

that's not the expected behaviour for sure. you could either open up a question here in the forum so we can troubleshoot there or open a support request and the Atlassian team can look into it.