I see this was discussed as of most recently in this thread, specially this comment. Please reconsider this change. In sum:
- I want to be able to set my own color system for projects in Asana, without affecting my coworkers’ system that vary based on roles, responsibilities, and needs.
- The “set for everyone” check mark option is now gone, which means any project color change will set for everyone… which does not work for everyone in my company. We each have different minds, needs, structures, and workflows… and removing an option to respect that is limiting, not freeing.
- This does not work and is confusing for me because of how I use Asana is different from how my coworkers use Asana… and both are correct. Taking away an option for work flow personalization for a service that is all about accommodating different users’ workflow I would argue is not progress, it is regression.
I can follow up with more details if needed as to why this is negative for me and my company, but I will keep this short for now.
Thank you for your attention.
18 Likes
Hi! We noticed this change at our agency’s Asana this morning, and it has caused chaos for us. I would love an option to opt in or out of this! It’s been a very frustrating morning for us.
8 Likes
Agreed. This is such a bad update and had totally disrupted workflow at our org. The OP has excellent points…we all have different ways of organizing our work and they’re all right. By removing the option to set project color individually, Asana is limiting the value of project colors all together.
6 Likes
Hi all, sorry to hear this has affected your workflows.
Don’t forget to hit the vote button at the top of this thread!
Hello all!
We appreciate your feedback. Although we don’t have immediate plans to reimplement the option to set project icon colors per user, our product team will consider it in the future.
Thanks for flagging this, and welcome to the new folks jumping in 
I’ve shared this thread with our product team for review. Your feedback is genuinely helpful and appreciated. Any examples of how this impacts your workflow really help us understand scope and priority. Thanks for taking the time to share.
2 Likes
@Alex_Christensen this is very upsetting. Our team uses their own color coding to organize their work. We have multiple people in the same project working in different capacities, so being able to customize this helps us optimize our individual workflows.
9 Likes
This is very upsetting & I do hope you reconsider, this change has caused chaos within our team this last few days. Everyone on our team is in a different combination of projects at different capacities so the inability to set personal colors creates additional logistical barriers to many team members being able to effectively complete their work.
9 Likes
@Alex_Christensen - I’m writing to strongly advocate for the return of the individual project color-coding feature.
Our team manages a high volume of projects within Asana, and many rely heavily on the Calendar View to stay organized. The ability to assign unique colors to projects—per user—was critical for distinguishing between overlapping initiatives. Without this functionality, multiple projects now appear with identical colors, leading to confusion and inefficiencies. What’s more, since color changes apply globally, users are inadvertently overwriting each other’s preferences, further complicating workflows.
Removing this feature seems counterintuitive. Can you please clarify the reasoning behind its removal? Additionally, what benefits—if any—were intended by eliminating this level of personalization?
From our perspective, this change has significantly reduced usability. It’s not just a preference—it was a practical feature that supported clarity and individual productivity. We would appreciate a detailed explanation and, ideally, the reinstatement of this functionality.
13 Likes
I share the opinions of the folks above. This feature allowed our team to use customization that worked the best for them, their workflows, and their minds. One of my favorite things about Asana has always been how you can cater it based on how you think and work best. This certainly feels like a step backwards and one that’s hard to see the benefit in. Sincerely hope Asana reverses this!
7 Likes
Adding to the chorus. Our team also used personalized colors as part of our workflow, not just an aesthetic nice-to-have. This update reduced Asana’s ease of use.
6 Likes
I echo the same sentiment as my peers. Managing a large internal marketing agency for a corporate business means we have a variety of working styles, personal preferences and individualisation that needs to be catered to.
Whilst Asana proves to be a valuable tool this update has been raised raised multiple times since it’s deployment and my team is struggling to find a solution that everyone appreciates. Individual views and personalisation is very important to our team! Please consider reinstating the functionality.
4 Likes
Just want to join in with everyone saying that I need this option back. I am autistic and color coding is critical for me, but my boss uses color coding completely differently than I do. Her system is horrible for my brain. Please bring back the “set for everyone” box so that I can return to my system that has been working for me for years!
6 Likes
Hopping in to say this is a disappointing change for our org as well. I’ve received a few comments from team members about this (who don’t normally care about anything Asana-related!)
2 Likes
Why “fix” or “remove” an option that wasn’t broken? Your users are speaking loudly - bring the option back so each Asana user can set their own project color. If it isn’t broken, don’t “fix” it!
3 Likes
I’m autistic also and feel the exact same way about this change. I manage a lot of projects in Asana. Most of the time I’m just managing the project, but sometimes I’m also doing tasks within the project. I need different colors to differentiate between what I’m managing versus what I’m actually working on so that I can immediately tell what I’m doing for each project. My coworker uses entirely different color coding.
2 Likes
Hi @Barbara_Broyles , thank you for your feedback.
I understand and share the frustration when a personal customization option is removed. However, the decision to make project colors org-wide was in fact customer-driven. We received significant feedback from users who were highly frustrated that their color changes didn’t apply to their teammates, leading to inconsistency in shared workflows.
This change was implemented to resolve that user dissatisfaction by establishing color as a reliable, shared communication signal across the team.
I want to assure you that both sides are heard and your input is extremely valued. The product team reviewing this is actively looking at how to best accommodate both approaches.
2 Likes
The default was already that the color changed for the team? We’re just asking for the “set for myself” option to be added back in?
4 Likes
Thank you, Miklhail - it seems like the frustration for users goes both ways - hoping there can be some meeting in the middle - there sure doesn’t seem to be enough of that these days. Be well!
3 Likes
Reiterating what Corinne mentioned. Users already had the ability to change the color of the project for the full team, but this change removes necessary personalization of workflows. Me and my coworkers’ frustration grows more and more each day.
4 Likes