I’ve been a frequent user of email-to-asana for task creation at work, and it has been working fine for me. The name of my company, for the sake of this example, is Myrealcompany. I tried to train other users and they all receive this error:
"From: Asana no-reply@asana.com
"Sent: Thursday, March 8, 2018 2:09 PM
"To: Person person@myrealcompany.com
"Subject: We couldn’t process your email.
“I couldn’t create your task because you are not in the same workspace as the project you are trying to add it to.”
Keep in mind that all these people are creating and editing tasks (directly in Asana, not via email) in the single instance of Asana that Myrealcompany operates. They all have myrealcompany.com email addresses, as do I. They are presumably all part of the Myrealcompany Organization.
According to Turning emails into Asana tasks | Product guide • Asana Product Guide, “To create tasks in your My Tasks list via email, send an email to x@mail.asana.com. By default, x@mail.asana.com will create a task in the Workspace or Organization associated with your email address.”
My profile settings show “You’re part of 1 Organization and 0 Workspaces.” OK, this is a hint of sorts. Not sure how we have all been operating for years with 0 Workspaces, but what are the right steps for me to take now? Create a Workspace and add everyone to it? But aren’t Organizations and Workspaces parallel entities capable of granting the same email permissions to their members?
We have 70-80 projects, 6 or so teams, all different permissions. I need to give everyone in the org the ability to send emails to asana. If I create a workspace and add everyone to it, will this change anyone’s permissions or visibilities, and if so, is there an easy way for me to see exactly what would change? Thank you!