There is a large number of out of the box Rovo Agents. If I wanted to not overwhelm my end users, and instead only have 1 or 2 OOTB Rovo Agents, is that possible?
Another use case is where there's an OOTB Agent to do xyz, but my end users are not permitted to do xyz, so I don't want them to see or use an Agent that tells them they can.
actually - contrary to what @Hari Krishna said, as Site Admin you can delete OOTB Agents:
Go into Studio and "search" agents. Then click ... on the OOTB Agent to delete it.
You could always create a free Test site to replicate the OOTB Agents but the Atlassian support is probably also able to re-introduce the agents. To be completely sure, copy the instructions into a file first. That way, you can re-create them as custom agents any time.
I cannot garantuee that Atlassian doesn't publish new Agents at some point, but you could always delete those as well.
Hi @Heidi Hendry ,
No — OOTB Rovo Agents can’t be disabled, deleted, or hidden individually right now. They’re always visible to users who have access to Rovo.
What you can do is create custom Rovo Agents for your use cases and guide users to use those. Even if an OOTB agent is visible, actual actions are still blocked by Jira/Confluence permissions, so users can’t do anything they’re not allowed to.
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.