We are all used to file systems where you can create folders hierarchy; and sometimes in Asana we want to do the same to organize projects.
Here are 4 ways to group projects together in Asana!
Teams: don’t hesitate to create a team with the only purpose of grouping projects together!
Fake project as a separator: a project named « ———« can act as a perfect separator in the sidenav!
Portfolios: they are a way to group projects in various ways, and could be your entry point to finding any project.
Colors: project color as a grouping key, like red for high priority projects, or green for HR projects etc
Acronyms: if you define acronyms for clients, initiatives, departments… using that acronym in the project name will make it easier to find them by using the search. It kinda works as a way to group projects together, doesn’t it?
Any other ideas?
Andrew Parkes also suggested to me 
and 
: use emojis or a naming conventions (which is a variation of the ). Thanks!
Version française
15 Likes
I use templates to define my projects and have them automatically update a ‘master’ project. Each time I use the template and my tasks are assigned, my master project updates at the same time. Still the same about of overhead in terms of managing tasks but the benefit of the master view also being updated. I just take key tasks (milestones even perhaps) through to my master project to have a simpler holistic view. I had hoped the new reporting feature would give me something similar but it doesn’t
Thanks for the tips! If only we could create folders in Teams by default.
11 Likes
Just use the search, you’ll never have to group projects again 
I have a template “team” specifically for this reason! One day maybe templates won’t be in there as projects, but until that day…
@Mandy_Fordham looks like you should create a brand new topic for your question, it is slightly off-topic here.
Hi! thank you this is helpful. I already use an acronym (5) at the begining of the project name (similar to 2) and a specific color (4) for a set of 10 projects that I need grouped together. But still, I would like to see them inside a folder or a different section. I am on a premium team so it look like I cannot use the Portfolios feature (3).
Then, can you explain how would option 1 work for me?
- If I create a new team and put the projects there, will I loose the premium features?
- Would I need to pay for me and other two users to be on that team despite we are already in the other premium team?
Thank you,
Lara
Hi,
If you pay for a Premium team, you won’t indeed have the Premium features in projects outside this team. Why not pay for the org instead?