Join the Rovo skills for admins early access program to simplify admin tasks

[#1]

Hi organization admins!

Are you interested in simplifying admin tasks? We're developing Rovo skills to handle specific repetitive admin tasks so you can focus on strategic initiatives. If you'd like to test Rovo skills for admins in Atlassian Administration, we welcome you to join our early access program (EAP).

Rovo skills are purpose‑built actions in Rovo Chat that help you perform specific, repetitive admin tasks like:

• Inviting users and granting access

• Troubleshooting SCIM/SSO setup and resolving common errors

• Quickly diagnosing user access issues

• Reviewing and cleaning up stale API tokens and keys

Learn more about Rovo skills

Why should you participate?

• Save time on repetitive admin work and find answers via Rovo instead of raising support tickets.

• Get precise answers to your user access and security questions, tailored to your organization.

• Share direct feedback with the Atlassian product team to help shape the admin AI experience.

What’s expected of the participants?

This EAP is open to organization admins and will start in early March and run for approximately 6 weeks. To help us understand your experience, we ask our participants to:

• Use Rovo skills in Atlassian Administration regularly (minimum once per week).

• Test out provided prompts and admin scenarios.

• Participate in three 30-minute calls to share your feedback with the Atlassian Product team.

• Submit feedback—and, if helpful, your conversation history—using the feedback collector in Rovo Chat.

How to join the EAP

If you’re an organization admin and are interested in participating, apply via the link below. After determining your eligibility, we’ll reach out to coordinate next steps.

Sign up now

Thank you for your interest! Leave a comment below if you have questions.

[David Cowley]

Does using Rovo skills for Admin require that Rovo otherwise be available within a given Site/Product, or is it enabled within Guard only?

From a privacy perspective the content within our work items and spaces is more sensitive than the information within Guard, so if they were separate things I believe it would be easier for us to get approval to use it.

If they are not separate things, then we still would fall into the group unable or unwilling to enable Rovo at this time.

That said, I feel as though this use of AI would have the easiest to measure ROI, as admins we have a reasonable sense of how much time we spend doing repetitive/administrative tasks, so providing additional automation or streamlining there would allow for easy calculations as to savings from AI or at least increased productivity, which is otherwise hard to quantify.

[Kelvin Russell]

Hi, Once this is live will this count towards the Rovo Credits limit?