Hi everyone!
I’m excited to announce that AI Studio now allows you to reference additional Asana Work Graph objects in your rules, making AI actions more powerful and contextually aware!
With this update, you can now:
- Reference goals: Check if tasks are related to specific goals and access goal details
- Reference portfolios: Multi-home tasks to the right projects
- Reference workloads: Assign tasks based on team member capacity and workload
This powerful enhancement enables you to create more intelligent workflows by giving AI access to broader Work Graph context. Simply @mention goals and portfolios in your AI instructions, or paste a workload URL to give AI access to these objects.
Let us know if you have any questions or feedback in the comments below!
Follow the AI Studio category: Discover smart workflows, explore new features and keep up to date!
10 Likes
AI Studio keeps getting better and better! 
2 Likes
Hey @Emily_Roman 
I have a couple of questions about how AI Studio generates its workload recommendations:
-
Is the recommendation based on the estimated time or the number of tasks within the workload? or something else?
-
What is the “context”?
Does the person creating the rule need to have access to all the projects & tasks that compose the workload of each user? Or does AI Studio have access to 100% of the workload?
Subject: AI Studio Rule Can’t Access Fields Inside Portfolios Within a Portfolio
Hi @Emily_Roman
I’m running into a limitation with an AI Studio rule that would add collaborators to a task based on a field value in a referenced portfolio. Specifically, the rule needs to reference a portfolio that contains a long list of individual portfolios. Each of those individual portfolios includes a key library field that identifies the assignee I want AI Studio to add as a collaborator.
The issue is that while the AI can identify the correct individual portfolio within the main portfolio, it can’t access the library field inside that individual portfolio. That field contains the assignee I need it to pull into the task as a collaborator.
I’d prefer not to manually reference each individual portfolio in the AI prompt, since the list changes frequently and would require constant updates.
Is there a way to structure this so AI Studio can dynamically access fields across multiple portfolios? Or is there a better approach to handle this kind of setup?
Appreciate any ideas or suggestions!
Many thanks,
Kylie
@Arthur_BEGOU It’s based on whatever unit you set in their workload:
The AI will access whatever the rule creator can see when they look at the workload view 
@Kylie_Burke My first impression is that you’ll need to reference the portfolios directly in the AI prompt. Alternatively, you could create a single “master” portfolio that contains links to all the other portfolios you need, and then reference that master portfolio in the AI prompt.
@ambforumleader @pforumleader in case anyone has any other tips!
2 Likes
@Emily_Roman
Thanks a lot !
Another quick questions, please :
Do you know the maximum number of projects a portfolio can take in account when mentioned in AI Studio, ensuring it remains compatible with the context size?
Is it the same limit as the maximum numbers of projects within a Portfolio (=1500 projects)?
Please answer a few simple questions.
Is the following method possible?
Prerequisites
- You have multiple similar projects (less than 100).
- You have a portfolio with multiple projects registered for management.
How to implement
- You want to track the progress of tasks in your portfolio from the previous week at the beginning of the week.
- Run a rule on Monday morning. Within that rule, specify the portfolio to track task progress in AI-STUDIO.
1 Like
I agree with @Ka_Nishiyama, if in follow up or next post we can get the gist on practical implementation of this feature on same data, it would be helpful! 
Thank you, Emily! I am referencing the single “master” portfolio that contains links to all the other portfolios I need in the AI prompt. It seems like AI Studio can currently match a portfolio by name, but it cannot pull or act on portfolio-level fields (e.g. people assignments or custom fields shown in the portfolio grid). This makes portfolio referencing only half-useful, since the data needed to drive collaborator logic or assignments usually lives in those fields.
For example, in our workflows we track ‘Concierge’ and ‘Social Media Specialist’ in portfolios. AI Studio can find the portfolio, but it cannot use those fields to add the right collaborators. As a result, the rule fails at the step where it should apply the field values.
It would be much more powerful if AI Studio could read and act on portfolio fields the same way it can with project/task custom fields.
