Invite workflow

[techAPJ (Arpit Jalan)]

@angelim

Invitees shouldn’t have to confirm email address. The only way they got to the forum was reading an undisclosed token in their email.

I believe this has been fixed since after you posted this topic. I just tested the workflow and I was logged in directly without needing to confirm my email.

---

@angelim

email_domains_blacklist should be used to validate invite emails. The inviter should know that email cannot be used.

Implemented:

FIX: invite email should be verified against `email_domains_blacklist`

---

@angelim

We could create a notification when creating invitee accounts to instruct them to define username and password before leaving. That could avoid some confusion later on, when they try to login again.

On it!

---

@angelim

The inviter could provide the invitee name when creating an invite. Starting the email with the inviter’s name may increase the likelihood of the invitees opening the email.

This can be done now by using Disposable Invite Tokens:

Generating lots of Invite Tokens

This plugin is deprecated in favor of Multiple Use Invite Links. You should only use this plugin if you require invited users to land on a specific topic. Summary: Generate multiple invite tokens GitHub: https://github.com/discourse/discourse-invite-tokens Install: Follow the plugin installation guide. Configuration Enable plugin After installing plugin enable site setting invite tokens enabled. Clone Discourse API Gem If you already have Git and Ruby i…

---

@angelim

Use the inviter name instead of username in the email template and address. Invitees may not recognize the inviters username.

Implemented via:

Improve invite email copy

---

@angelim

The private message(Welcome message) sent when the invitee accepts the invitation could be signed by the inviter, instead of the system. Aside from being more personal, the invitee is readily presented with the inviters account, making it easier for them to begin conversations inside discourse.

Not sure if this is the correct approach. Any feedback here @codinghorror.