Resend the SRAM invite whenever a user is removed and added to a group regardless of whether the user accepted a previous existing SRAM invite before or not.
Currently only when a user accepts the SRAM invite, is then removed from that group that the user accepted the invite for, and is then re-added to that group, only then will it trigger sending the SRAM invite again.
Because a user may forget to accept an SRAM invite (they may be on holiday, on some leave, or other reasons for forgetting to accept an SRAM invite), the resending of that SRAM invite is not straightforward from within Yoda. Removing a user from a group and then re-adding them when they did not accept the first SRAM invite, does not trigger the SRAM invite again. This would however be an easy way to resend an SRAM invite so that we as admins can quickly make sure that our users have access to their folders in Yoda.
Describe the solution you'd like
Trigger the SRAM invite whenever a user is removed and re-added to a research group regardless of the status of any previous SRAM invites.
Describe alternatives you've considered
Have the person that made the invitation go to sram.surf.nl and manage the invites from there. But I don't want my users to be bothered with SRAM (and essentially another platform for them to be concerned about). Yoda should be an easy and less complex interface.
The other workaround is to create a new research group in the subcategory in question (that I often name 'research-sram-groupabbreviation') and add the user with the SRAM invite issue to this group so that the SRAM invite triggers.
Resend the SRAM invite whenever a user is removed and added to a group regardless of whether the user accepted a previous existing SRAM invite before or not.
Currently only when a user accepts the SRAM invite, is then removed from that group that the user accepted the invite for, and is then re-added to that group, only then will it trigger sending the SRAM invite again.
Because a user may forget to accept an SRAM invite (they may be on holiday, on some leave, or other reasons for forgetting to accept an SRAM invite), the resending of that SRAM invite is not straightforward from within Yoda. Removing a user from a group and then re-adding them when they did not accept the first SRAM invite, does not trigger the SRAM invite again. This would however be an easy way to resend an SRAM invite so that we as admins can quickly make sure that our users have access to their folders in Yoda.
Describe the solution you'd like
Trigger the SRAM invite whenever a user is removed and re-added to a research group regardless of the status of any previous SRAM invites.
Describe alternatives you've considered
Have the person that made the invitation go to sram.surf.nl and manage the invites from there. But I don't want my users to be bothered with SRAM (and essentially another platform for them to be concerned about). Yoda should be an easy and less complex interface.
The other workaround is to create a new research group in the subcategory in question (that I often name 'research-sram-groupabbreviation') and add the user with the SRAM invite issue to this group so that the SRAM invite triggers.