Problem

Currently, Confluence automation only supports triggers and actions with Groups, not Atlassian Teams.

• Groups are managed by admins and facilitate permissions, automation rules, project roles, and notifications. However, Teams, which are user-managed and enhance collaboration and visibility, can't be utilized in automation rules, CQLs, or space permissions.
• This limitation causes confusion and frustration for users who wish to leverage Teams similarly to Groups for automation and notifications.

Suggested Solution

Enhance Confluence automation to support Atlassian Teams, allowing them to be used in automation rules, CQLs, and project permissions, similar to Groups.

This would streamline user experience and expand functionality to better support collaborative efforts.

Why This Is Important

Integrating Teams into automation and permissions functionalities is crucial as it aligns with user needs for a more seamless and cohesive experience.

It reduces confusion and frustration, allowing users to fully utilize Teams for automation and notifications, thus enhancing collaboration and operational efficiency.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available.