Summary

With the ongoing expansion of Confluence Automation capabilities, a wide range of integration actions (e.g., Azure, AWS, Splunk, Datadog, Google, Jenkins) are now available to end users. However, not all customers use or want these integrations enabled in their environment.

Currently, there is no central control for administrators to limit which automation actions are available. This can lead to:

• Users unintentionally using integrations that are not officially adopted or approved.

• Increased risk of misconfigurations or unforeseen side effects.

• A cluttered and confusing automation action catalog for users.

Suggestion

This feature request proposes a configuration option for site/product admins to enable or disable specific automation actions so that only relevant, approved actions are visible and usable in Confluence Automation.