Currently, we are reusing the roles and permissions of the legacy datasources in the new catalog data source entities for 0.9.2. Now the role permissions for catalog data source entities has to deviate from those of the legacy datasources; effectively eliminating the distinction of the "access summary" and "access details" permissions.
The proper solution would be to create an upgrade action that generates new roles and permissions for the catalog data source model. In the short term we can fix this directly in the code that applies the access control to the JCR model, as it is just a few lines of code.
As time permits we should create new roles and permissions specific for the new model. Otherwise this should be done in the next release after 0.9.2 when we add access control at the data set level.