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
{{ message }}
This repository has been archived by the owner on Jun 4, 2024. It is now read-only.
API needs to have an endpoint to generate an invitation. It will need to build an invitation object and log who created it, and have a unique link generated and associated. The link is the important thing to return in the response payload (in addition to invitation ID). Other criteria (like expiration and revocation) will come later.
We'll also need a "send invite" endpoint that takes in a list of contact information. I'm going to make it difficult on you and say it'd be easiest to just have an array of strings that could either be e-mail addresses or phone numbers. The API then tries to format and send the invitation to each given recipient.
Each send attempt should update metadata entries for the invitation that will basically say something like "invite ID XXXX recipient soAndSo@whatever.com status success" and "invite ID XXXX recipient 555-123-45678 status failed", the latter ideally having a reason or response code from the downstream delivery mechanism.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The organization ui calls for an "invite by email" workflow. We either need to re evaluate the ui workflow or implement this option in the server.
The text was updated successfully, but these errors were encountered: