Hi @PaulKalvelage I think for this specific use-case a workaround might help.
In general, if you limit the linked selections based on view in Airtable, Softr will show only the options that are available in the limited Airtable view.
Keeping that in mind, here is what I would personally do:
- I would create different views in Airtable for the original table that is used for the linked records and I would filter those views based on the user groups.
So let’s say I have User 1 who should only see option 1,2 and I have User 2 who should only see options 3 and 4. I would create one view for User 1 and filter the data based on the user. Then I would create view 2 and filter the data based on his/her info. So that each view shows only the options related to the corresponding user. - Then I would create new linked fields for each view in the table where you would like the end users to edit them.
- Afterward, I would create corresponding user groups in Softr (User 1, User 2) and set up Action buttons with corresponding visibility settings. So that User 1 sees only the action button 1, User 2 - Action button 2
- Each action button should be mapped to the field that is limited by the corresponding view.
As a result, when editing, each user group will be able to see only the options that are available for them in the limited view.
Hope it makes sense and was helpful 