Repository navigation
Replies: 3 comments 2 replies
|
Makes sense. Cleared for a design PR. |
0 replies
|
Design PR #4851 proposes |
0 replies
|
Thanks Matt, draft design PR added. Not planning to implement it, so it's open to any other contributor. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
After sending an invite from Users, the admin shows the fleeting "Invitation sent to {email}" confirmation toast and then nothing. The invited person doesn't appear anywhere until they accept, so there's no way to see who is pending, when an invite expires, or whether it was already sent.
In 1.5.0 the invite routes are create, accept and complete only. Pending invites sit in
auth_tokens(typeinvite) with no list, resend or revoke in the admin or the API. Nothing stops a second invite to the same address either: pressing Invite 3x stored 3 tokens and sent 3 emails.A "Pending" section on the Users screen, listing email, role, invited by and expiry, with Resend and Revoke, would cover it. Inviting an address that already has a pending invite could offer to resend instead of creating another.
Use case
An agency setting up a client's site invites the owner as Editor. The toast confirms, the Users list doesn't change, and with no sign of the invite the agency assumes it failed and sends it again. The owner then gets 3 identical emails, and the agency has to check the database or the Worker logs to learn that all 3 went out. Anyone who invites users meets this: agencies handing a site to a client, and site owners adding editors.
Current workarounds
Query
auth_tokensin D1 and search Workers Observability for the email provider's delivery log line. A plugin could add a read-only admin page overauth_tokens, but revoke and resend belong next to Invite on the Users screen.Your involvement
All reactions