# Invite workflow

**URL:** <https://meta.discourse.org/t/invite-workflow/14460>\
**Category:** Feature\
**Created:** [April 4, 2014, 2:36pm UTC](https://meta.discourse.org/t/invite-workflow/14460 "2014-04-04T14:36:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\
**Post date:** [April 4, 2014, 6:31pm UTC](https://meta.discourse.org/t/invite-workflow/14460/2 "2014-04-04T18:31:08Z")

</div>

> [@angelim](#):
>
> I’ve been thinking about the invite workflow and I have the following suggestions. Let me know what you think.
> 
> Invited people shouldn’t have to confirm email address. The only way they got to the forum was reading an undisclosed token in their email.  
> email\_domains\_blacklist should be used to validate invite emails. The inviter should know that email cannot be used.  
> We could create a notification when creating invite accounts to instruct them to define username and password before leaving. That could avoid some confusion later on, when they try to login again.  
> Maybe we could send a different welcome message to invited accounts, adding some information related to their condition. The password definition being one of them. Stating that they were referred and that is reflected in our trust and that their actions would also affect the inviter’s reputation.  
> The inviter should be able to invite more than one person at once. Maybe a email list separated by commas with a clear limit.  
> Ask for the invited name when creating an invite. Starting the email with the inviter’s name may increase the likelihood of them open the email. (conflicts with 5)
> 
> Use the inviter name instead of username in the email template and address. Invited people may not recognize the username.

All this only my opinion of course

1. Good idea as long as that’s the email address they want to use, or if they can change it.
2. Good idea, no point in sending an invite to someone only to have them not get in.
3. Excellent point 👍 When I invited some test accounts for the SitePoint site I didn’t understand how it worked and missing this led to some confusion. Once I knew what to do it was easy enough that it seemed obvious, but before I knew …
4. I was surprised when I learned my invitees were jumped straight to TL 2. I’m not sure the info is important as they’ll simply see more features. First I’ve heard about invitee misbehavior affecting the inviter.
5. While having a TL does imply a certain errmm level of trust, my “introduces potential abuse problems” flag gets raised.
6. That would be more “personable” and friendly.
7. I can’t say, I use the same for both.

---

_[View the full topic](https://meta.discourse.org/t/invite-workflow/14460)._
