Remove/improve email authentication for forms with Request Tracking

English Forum Product Feedback
,
1

I’m interested in enabling request tracking on a few forms we use internally, but in testing I discovered that users must authenticate their email either using Google or have a code sent to their email before they can even see the form. This is a deal-breaker for this feature for us because:

  • It’s unexpected. The user expects to see a form (as they have been used to) but instead gets taken to a login screen with an Asana logo. They likely have no idea what Asana is or why they are being asked to authenticate. If I didn’t know/care what Asana was I would be very unlikely to authenticate into an unknown service using my Google account.
  • It’s confusing. They are asked to login before even being sure they want/need to because they can’t see the form. The authentication prompt is generic and doesn’t reference what the form is or what organization the user is required to be a part of. I was thoroughly confused, and I’m the Asana expert that was setting it up!
  • It’s burdensome. Adding in an extra step to see/complete the form means users are more likely to just fire off an email or Teams message rather than use the desired workflow. It also believe it would also lead to lots of people pinging me with questions and create a negative impression of Asana for non-users which would be counterproductive to our goal to further grow and integrate our work in Asana.

I had originally expected that the form would simply validate that the users email domain matched the domain for our Asana account. I’m sure there are reasons why it wasn’t done this way, but I hope the team can revisit this part of the feature in future updates because the current user experience makes it unworkable, at least in my organization.

3 Likes
2

Welcome to the forum @Alicia_DiRago1!

Thanks for the feedback. I agree it might be made more intutitive, so I added my vote.

I don’t think it’s possible to completely skip the email verification though, as I don’t see another way to verify that the person accessing the link is the one associated with that domain email.

Or am I missing something?

PS: To be clear, I’m a volunteer Forum Leader, so I don’t speak for Asana. :wink:

2 Likes
3

Thanks, appreciate your vote!
From my perspective I’m not overly concerned with the form submitter verifying their email as the use case is strictly internal. If they accidentally or intentionally enter the wrong email address, it’s not much different than if they did so on a form we are already using without request tracking. From Asana’s perspective I know they need to worry about spam/undeliverable emails so I respect that it’s more nuanced.
Ultimately, I just don’t think that Asana request tracking works with this current design.

2 Likes
4

Request Tracking is frustratingly close to useful. Requiring authentication for internal, non-Asana members is definitely a roadblock. I’d also like to shout into the void about this. Additionally, request tracking features ought to be enabled for email-created tasks, as this would create a more well-rounded IT service management component of Asana.

3 Likes