
Atlassian admins can now ask Rovo to fix access problems
Atlassian has put Rovo Chat inside Atlassian Administration, in beta. Its support page, dated November 17, says organization admins can now ask Rovo to do common admin jobs.
The beta is for organizations with at least one paid app and more than 100 paid seats, on Standard, Premium or Enterprise plans. An admin turns it on under AI and Rovo, then Rovo settings, then the Rovo in admin tab. After that, Ask Rovo shows in the top bar.
Type a slash in the chat to see the admin skills. They can invite users and add them to groups, check why someone cannot open a Jira issue, list API tokens not used for 180 days, find empty groups, find users with no recent activity, and walk you through SCIM provisioning and SAML single sign-on problems.
The skills use the admin's own permissions. Some actions ask you to confirm before Rovo changes anything. Atlassian notes limits too. The permission skill may not see settings made inside Jira or Confluence, and Rovo cannot remove old API tokens in bulk.
What it means for your work
If you look after your team's Atlassian accounts, try the inactive users and empty groups skills first. They only read, so they are a safe way to see what Rovo finds.
When someone says they cannot open a page, ask Rovo why before you dig through settings yourself. Read each change it proposes before you confirm it. For how Confluence now labels agent work, see Confluence now shows which agent did the work and for whom.