Prevent over-writing of user rights when using the collaborate function

Hi all, we're currently facing an issue with our set-up of users, and I'm hoping someone of you might have had a similar problem and found a workaround. In our organization, we have different user types and based on the user type, certain functionalities are enabled or disabled. For example: we have a "general user" who can do survey programming, analysis and reporting. And then we have an "analysis user" who cannot program/change/distribute surveys but can only use the tool for analysis and reporting. The problem we are facing is that, as soon as a "general user" is sharing a survey with an "analysis user" through collaborating, the original user rights of the analysis user are overwritten and that person is suddenly allowed to do everything on that project. Technically, when collaborating, some boxes can be ticked off in terms of rights, but it doesn't seem very practical to do this every time and for all the different user types you're sharing with. Additionally, we will also have user groups in our system (e.g. a group for a certain department) , which can contain different user types (e.g. general user, analysis user) so if we then want to collaborate the survey with an entire group, everyone in that group will have the same rights (even though they have different user types). From a logal point of view, I find it a bit strange that individual user rights don't prevail when collaborating. But maybe there is a way around? If anyone has had a similar experience or has an idea of how we could solve this, I'd gladly hear about it! Thanks in advance! Best, Kim