-
Suggestion
-
Resolution: Unresolved
-
None
At present, there is no option available for customers to delete or cancel Rovo on their own. This limitation results in the following challenges:
- Unable to delete an organization: The "Delete Organization" option remains disabled until Rovo has been deleted.
- Unable to transfer products: Customers cannot transfer products to another organization until Rovo has been deleted.
- Unable to merge organizations (new user management UI): Customers cannot merge organizations until Rovo is deleted.
Suggestion: Introduce a self-service option that allows customers to initiate the deletion or cancellation of Rovo. This feature will empower customers to resolve these blockers independently without the need to contact support, improving their overall experience and reducing their dependency on the support team.
This enhancement will streamline the process for customers and make organizational management more efficient.
- followed by
-
- Gathering Interest
- relates to
-
- Gathering Interest
-
ENT-3198 Failed to load
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[ROVO-144] Enable Self-Service Option for Deleting/Canceling Rovo
This is preventing our team from cleaning up Shadow IT Atlassian orgs. Users create stuff either by mistake or because they're curious and don't realize we can get them sandbox access. Fighting Shadow IT definitely takes admin time and our management watches us to make sure we keep it in check. Now having orgs that we can't remove simply because Rovo got added there (in this specific case to an org where the only Confluence product was already deactivated too!) is not going to look good at first pass for us until we get management to understand that it is a limitation imposed by Atlassian currently.
6e3f201eef6a the problem is that it doesn't stay deactivated even when it's turned off.
Atlassian has sent out a communication yesterday with subject: "Important notice: AI access coming soon".
We understand that your organization may not be ready to activate AI yet. Based on your prior preferences, AI features will remain deactivated on your Standard plan(s) that were set up before July 8, 2025 unless you choose to activate them.
Note that any new apps on Standard, Premium, and Enterprise plans added to your organization will have AI enabled by default and organization admins can change your AI activation settings at any time.
Please, stop activating AI features on our tenant once we turn that off.
Thank you, this will be very important! One thing that would be great is allowing each user to individually enable or disable Rovo and where it shows up. For example, having Rovo results appear at the top of the search results is incredibly intrusive and unhelpful, and it would be amazing to be able to hide Rovo there but still use it when we want to.
We would like to start using Rovo, but at a time that suits us. Need to see how we can use it first, make sure we communicate enough globally and then activate it. We have just activated Atlassian Intelligence and we are not ready to move on just yet. So being able to decide when we activate Rovo ourselves would be great. Now we have to deactive the Atlassian Intelligence features also when deactivating Rovo, which will be a negative experience for our agents.