I don’t think we have a policy about this specifically, but I asked the team what they thought about it and we sort of built an impromptu set of guideines We think that this is probably OK if you ensure a couple of things:
- Make sure the email comes from a clear and non-spammy app email address, such as "firstname.lastname@example.org" or similar, so that people know that it’s a real thing and don’t get emails from "email@example.com" or some other scary sounding address.
- Ensure folks that you’re not going to sell their information on with something like “Templana will never share your email with an outside party” to assuage fears that spam will flood their inbox / indicate that if and when spam inevitably does show up, it wasn’t from Templana or Asana.
- And, you know, actually stick to that - don’t sell their contact info.
- Send the email in response to a specific user action on behalf of an existing user in the organization. The idea of a button click is totally fine, but don’t auto-mail all users in the organization.
- Indicate that a specific user action was involved; say, language in the email to Bob saying “Your colleague Brian has invited you to use Templana with Asana”, so people know that Brian triggered the email and you’re just sending it for that person. (You don’t strictly have to say that the invite involves Asana, but if it makes sense and is clearer to what tools the invite is for, it’s probably a good idea).
We may come up with more guidelines if apps end up abusing this (worst-case scenario is someone builds a spam app specifically for this, but we can always ban such apps) In the end, though, a polite invite sounds like a great idea for Asana (to increase platform adoption) and apps built on Asana!