You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other fields like phone-numbers and enckeys already are lists. Making the email field an "emails" list field would be a good idea as there might be more than one email per organisation (and therefore a reason for multiple enckeys). You could store multiple emails comma separated but then a client has to parse this list if he wants to know which encryption key is used for a specific email address, etc.
The text was updated successfully, but these errors were encountered:
Other fields like phone-numbers and enckeys already are lists. Making the email field an "emails" list field would be a good idea as there might be more than one email per organisation (and therefore a reason for multiple enckeys). You could store multiple emails comma separated but then a client has to parse this list if he wants to know which encryption key is used for a specific email address, etc.
The text was updated successfully, but these errors were encountered: