There are several places in Synapse where a user needs to reference a collaborator who they find are not yet in Synapse.
UI Mockup:
https://docs.google.com/presentation/d/1SKSzfWaOBAPdN87ivTXnLxV3ItuY7VoWANcXWeglxN0/edit?usp=sharing
create an external user token (EUT) (+ various meta data, e.g. first, last, email)
table columns: ID, token, first, last, email, principalId (initially null)
prior to its acceptance (when principalId is null), the EUT can be rescinded
should be able to update with new token (but keeping the same EU ID)
should sending the EUT to the person be a server-side or client-side function?
service to create a team invitation linked to an EU + services for all CRUD on such an object
shall we generalize the existing invitation or create a new object?
service to update an EU record, associating a principal Id
anyone having the EUT can link the EU record to their account
at this point the EUT can't be rescinded by the creator
the client is responsible for the sequence:
1) create or select an account
2) link the EUT to the account
3) retrieve the associated team invitation(s) and accept them (or present them for acceptance)
following link ust log out any user