Issue Summary

When a custom space role is edited to add or remove permissions, Confluence runs a background process to apply these changes to all assigned users. For certain users, typically those with older Atlassian accounts, the synchronization fails.

In this state, the User Interface (UI) correctly shows the user has the role and the role has the new permissions, but the user is functionally blocked from using the features associated with those permissions. This is due to a mismatch in how internal account identifiers are handled during the background update process.

Steps to Reproduce

1. Create a custom space role and assign it to users
2. Edit the role to add a new permission
3. Ask the user to test the new added permission

Expected Results

The new permission should be active for all members assigned to that role.

Actual Results

Affected users are unable to access features granted by the update, even though the UI indicates they have the correct role.

Workaround

Remove the affected user from the space and re-add them with the same role. This forces a fresh synchronization of the user's permissions.