I realised when setting up a new Pod (something I haven't done in a while) that we don't really have an "Invite" System.
Currently Pod Owners can:
- Disable Open Registrations
- Setup accounts for Users
- New Users do not get notified of their new account
We should flresh out a better flow.
Just want to add in my 2c.
In my previous projects this is what I did for an invite workflow:
Have a poderator generate a four-word passcode (diceware if you will) with an optional timeout (usually 12hr) and an optional use count (usually 3).
The new user goes to register and has to put in the four-word passcode along with the username and password etc.
Doesn't have to get more complicated than that for an invite!
What if we go one simpler?
- Generate an invite token / link (we have the code for this)
- Track no. of uses/expiry/etc
Users just hit the link and it bypasses the "Closed Registration" flow if valid/etc.
Yes, that's perfect.
Deleting a branch is permanent. It CANNOT be undone. Continue?