Diagnose team permissions
Use the diagnose team permissions skill to self-serve answers to common access questions, reducing the time spent troubleshooting or waiting for support.
What is the diagnose team permissions skill?
The diagnose team permissions skill is a read-only Rovo skill that helps you understand why you might be having trouble accessing or managing an Atlassian team. It investigates team visibility, membership, and permissions to provide an evidence-based explanation and recommended next steps. Because it is read-only, it will never change your team settings, memberships, or permissions.
For example, if you can't find a specific team in the directory, you can use this skill to determine if the membership settings are private, if you lack the necessary permissions, or if there is a specific membership restriction in place.
The scope of this skill is limited to Atlassian teams. You can’t diagnose access issues for other apps such as Jira or Confluence.
How to use this skill
The skill analyzes specific signals from your Atlassian organization to explain access failures. You can invoke it by asking Rovo natural-language questions or by using the /diagnose-team-permissions slash command.
When you ask a question like "Why can't I see the Payments team?", the skill checks:
Team visibility: Whether the team is private or if your directory permissions are missing.
Membership policies: Who has the authority to add members and why a specific user might be blocked.
Effective permissions: What actions you are currently authorized to perform on a team.
Creation restrictions: Why you might receive an error (such as a
403 Forbidden) when trying to create a new team.
To use the skill:
Open Rovo Chat.
Chat with Rovo using natural-language questions or type
/diagnose-team-permissionsfollowed by your question (for example, "Why can't I see the Payments team?").Review the diagnosis and recommended next steps.
The skill returns an evidence-based explanation of the issue, identifying the specific cause (such as a private team setting or a membership restriction), and provides recommended next steps to resolve it.
The skill also appears as a Rovo nudge in the Teams directory when a search returns no results, allowing you to start an investigation immediately from the search page.
Diagnose team permissions triggers
Here’s some natural language phrases you can use to trigger diagnosis.
"Why can't I see [Team Name]?"
"Who can add members to [Team Name]?"
"Why am I getting a 403 when creating a team?"
"What permissions do I have on [Team Name]?"
Examples
If you want to specifically call this skill, you can use the command as shown in the examples below:
To investigate access issues:
/diagnose-team-permissions why can't I see the Payments teamTo find who has permissions:
/diagnose-team-permissions who can add members to the Payments team
Was this helpful?