Confluence Cloud for Slack is presented as a system-installed app in Connected Apps, but does not provide a clear self-service lifecycle model comparable to other system-installed apps that expose an Uninstall option.

Administrators cannot easily determine:

•  why the app cannot be removed from Connected Apps;
•  whether it is enabled, disabled, or connected to a Slack workspace;
•  how to disable it;
•  what happens to existing Slack connections, tokens, user mappings, page previews, notifications, access-request flows, and data exchange after disablement; or
•  how to request complete removal when required by an organization’s security policy.

Expected behavior
Provide a clear and auditable administration experience for Confluence Cloud for Slack, including:

 1.  Visible enabled/disabled and workspace-connection status.
 2.  A clear explanation when Uninstall is unavailable.
 3.  A direct link to the supported configuration/disablement experience.
 4.  Documentation of the effect of disablement on existing connections, credentials, data flows, notifications, previews, and access-request functionality.
 5.  Administrator audit events for enablement and disablement.
 6.  A supported full-removal path for security and compliance use cases.

Impact
This gives Enterprise administrators consistent controls and evidence for governance reviews, especially where Slack is prohibited, restricted, or subject to formal data-transfer controls.