If youāre using Asana Starter and starting to feel the limitsāprojects living in silos, too many manual updates, or goals that live in a separate place from your actual workāthis oneās for you.
In this short and practical video, we walk through the key features of the Advanced plan and show how it can help your team move from task-by-task execution to true strategic work management.
Weāll cover:
How Portfolios give you clear oversight across multiple projects How to tie real work to company goalsāwithout switching tools And how automation and control help you work smarter, not harder
Whether youāre actively considering an upgrade or just curious what comes next after Starter, we hope this gives you a helpful and inspiring overview. Give it a watch and let us know what resonates with youāweād love to hear your thoughts!
PS: Weāre also testing out new colours - Iām sure youāve spotted that! What do you think?
Please feel free to share your thoughts or questions in the comments below!
Hi @Laurence_Easeman
Teams and Portfolios serve very different purposes in Asana and are both still relevant. Teams are the structural backbone of your Asana workspace ā they organize people, projects, and permissions, typically by department or function. Portfolios, on the other hand, are a reporting layer that helps you group and monitor projects (or other portfolios) across teams, based on strategic goals, programs, or workflows. I usually recommend using Teams to manage access and collaboration, while Portfolios give leadership and cross-functional stakeholders the visibility they need ā they complement each other, not replace.
Hope that helps!
Hey @Sonja_Gusenbauer Iām looking to upgrade to Advanced Plan but not sure if it will solve the problem Iām having with Starter or not⦠Any advice, guidance, or explanation will definitely help my decision.
Iāve been using projects in 2 ways - 1) as to manage the work/tasks weāre doing for each and 2) to manage build/setup workflows for my team (by linking projects to the workflow projects and facilitating subtask creation rules as each stage/section gets completed). An example of the āsetup projectā would be [onboarding] [content] [design] [build] [qa] [launch]. Once all of thatās done, we remove the from the setup project and continue working through our other setup projects.
The issue Iām running into is that I cannot rotate subtask assignees based on project role (i.e. I take all the design subtasks on one project, you take all the design subtasks on next project and so on) each time we create a new project.
Is this something that is achievable in the āproject roleā feature with advanced?
Hi @Vincent_Watkins !
Thanks for reaching out and for sharing so much detail about how youāre currently working in Asana ā thatās super helpful context.
The Advanced plan does give you access to Project Roles, which makes it easier to assign ownership across projects consistently (e.g. automatically assigning a āDesignerā role whenever you spin up a new project from a template). However, it wonāt dynamically rotate roles or automatically alternate subtask assignees from project to project ā that level of rotation logic isnāt available today.
That said, many teams solve this by:
Setting up clear project roles in their templates, so assignees are pre-populated consistently, and
Using rules to automate subtask creation and assignments within a project.
If rotating ownership is really key for your workflow, you might need a lightweight manual step to decide āwhoās on designā before launching a new project. From there, the Advanced features can handle the rest of the automation smoothly.