Rationale / Begründung
In a cross site invitation the invited user's first (in database) site is choosen to build the invite link in the invitation email.
Minimal functionality
Easiest solution could be to use the inviter's site in the link. But that might not be appropriate for all sites.
A better approach could be to list links for all sites the user is registered on and let the user choose on which site they want to see that project.
This list should also contain the names of the sites, not only the link.
The text of the email template should be adjusted accordingly.
Affected
All
Nice-to-have functionality
If users are not yet registered to any site (and are invited via their email address) the inviter's site is used as domain for the link.
If that seems not reasonable maybe a settings entry could name the possible sites that should be listed in this case.
Rationale / Begründung
In a cross site invitation the invited user's first (in database) site is choosen to build the invite link in the invitation email.
Minimal functionality
Easiest solution could be to use the inviter's site in the link. But that might not be appropriate for all sites.
A better approach could be to list links for all sites the user is registered on and let the user choose on which site they want to see that project.
This list should also contain the names of the sites, not only the link.
The text of the email template should be adjusted accordingly.
Affected
All
Nice-to-have functionality
If users are not yet registered to any site (and are invited via their email address) the inviter's site is used as domain for the link.
If that seems not reasonable maybe a settings entry could name the possible sites that should be listed in this case.