Is there a problem with the underlying code that makes it particularly difficult for Asana to offer robust permissions management? It seems like there has been no movement on a core product weakness for a very long time.
At one point Alexis indicated a fundamental conflict between permissions management and transparency. Again, is that a technical issue or a philosophical issue? If it is philosophical, that seems to make little sense. Asana could offer robust permissions, but leave it up to the customer to decide how stringently they want to implement them. Asana could even recommend “permissions lite” settings, but still give the customer the option to ensure the integrity of their own data.
Is there a published product roadmap that shows the priority that Asana had assigned to requested or planned new features and functionality (speaking of transparency…)?