Issue Summary

When a user performs a "Copy Space Permissions" operation in Confluence Cloud, the operation is destructive to the existing permissions on the target space. While the Audit Log correctly captures the addition of new permissions and some individual user/app removals, it fails to record the removal of groups that were previously authorized for the space.

Steps to Reproduce

1. In Confluence Cloud, identify a target space (Space A) with several groups assigned to its permissions.

1. Identify a source space (Space B) with a different set of permissions.

1. Use the "Copy Space Permissions" feature to copy permissions from Space B to Space A.

1. Navigate to Settings > Audit Log.

1. Filter for the "Space" or "Permissions" category.

Expected Results

The Audit Log should contain entries for every permission change, including:

• Space permissions copied (Summary event)

• Group permission removed (For every group that lost access during the overwrite)

• Group permission added (For every group that gained access)

Actual Results

The Audit Log captures the "Space permissions copied" event and individual user/app removals, but no entries are generated for the removal of groups. This creates a significant blind spot for administrators attempting to audit or recover from accidental permission overwrites.

Impact:
This auditability gap complicates recovery efforts for enterprise customers, where an accidental overwrite affected thousands of users. Without a record of which groups were removed, administrators must rely on manual cross-referencing or backend database restores to identify the lost access.

Workaround

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