When creating content-sources, we don't have the Editors in mind that will have to select the correct one from a list of content-sources, but the technical value they provide.
We usually have several content-sources with the same schema, but not all should be available for the client to select on every feature.
For example (see attachment), we have those 4 content-sources, which are all ans-schema conform and the Editor can pick from all of them, but the only they should ever pick is 'story-with-related-content' and 'content-api-v4'. We want to limit the list to only those they should have access to on a feature-level. Preferably with a new field on a content-source called selectable: false or something along that line.
This excludes Global content selection or resolver or anything. This is just about the day-to-day work of newsroom Editors, to make sure they don't pick something they shouldn't.
Kristina Matheisen
Thanks for the suggestions. We are interested to know more use-cases from other clients as well. Also, are there any other places/ workflows in PageBuilder where using groups for content sources would be helpful?