Interface issues when using access roles with source access checking

remco

Host: Shared hosting
Collective access version 1.8

We have three collections managed in one collective access installation.
Until now there was no need to restrict access to specific collections to any user.
This has changed, there is now need for access control based on the collection the item belongs to.
I thought collection source and object source could be used to accomplish this
After setting perform_source_access_checking = 1 in app.conf and adapting access in access control --> access roles -->source I have an issue with some of the user interfaces not being accessible.
For entities for instance none of the screens is visible.

How could the visibility of UI screens be related to collection and object source?

remco

Solved.
From the manual:
Each record type must have a source list defined (i.e. "object_sources," "entity_sources," etc.) to use this access control type. The intrinsic bundle "source_id" can be placed on an editor form to allow cataloguers to select the relevant source for a record. When a default source is set for a specific access role, the source_id bundle is optional. The default will automatically set the source for that login.