This data model is a major problem for us, has prevented other parts of our organization from adopting Asana. Our division is a small department in a university. Every client we work with shares our email suffix and so for Asana’s purpose is considered part of our organization. This extends to every person who has ever taken a course at the university - all students and alumni, tens of thousands of people.
As a result for collaboration purposes, Asana has become an anti-collaboration tool beyond our internal task management and we have to have other systems for dealing with our clients, stakeholders, and for transparency. I’m sorry to say it’s only a matter of time before one of these other systems replaces Asana and we, unfortunately, have to advise against other units adopting it despite loving the UX and other functionality.
If anyone knows of a way we can work around this, I’d be very grateful for any tips. Asana is a fantastic tool, it’s just clearly not built for small groups inside large organizations. What would be ideal is some kind of limited access similar to “guest” passes.