Changing Group user inheritance doesn't rebuild permissions

When setting Group user inheritance to "No", private subSpaces are still visible for a regular user of the parent Space. Only changing the Group user permission inheritance for the subSpace results in the expected removal of access rights.

Testing visibility and access for private subSpace B

• Create a Space A and a subSpace B
• Set subSpace B to 'private'
• Testuser is regular member of Space A
• Set the Group user inheritance for Space A to "No"
• Result: Testuser can see subSpace B but not it's content (Sections)
• For subSpace B now set Group user permission inheritance to "Child's permissions"
• Result: Testuser can not see subSpace B, nor has access to it's content.

Further testing revealed that changing the Group user permission inheritance triggered the expected removal of access rights.