Hi everyone, Ren here! Thanks for joining today’s Managing Workflows in Asana training! 
I wanted to share an insightful question that came up during the session:
Q: Can files and attachments added to the Key Resources section in the Overview tab be made private?
A: Yes. Files or attachments added to the Overview → Key Resources section can remain private.
- Adding them to the Overview does not automatically share them with others.
- Only people who already have access to the original file, project, or document can open it.
- If the project is set to Private to members, only project members can access the files inside it.
So the item can appear in the Overview, but visibility still depends on the project’s privacy settings.
Feel free to continue the conversation by sharing any questions you have in this thread.
1 Like
Hi everyone 
Thanks again for attending today’s session!
Here are a couple of questions I wasn’t able to answer live:
Q: How does Asana compare to other tools like Jira or MS Project?
A: One of Asana’s biggest strengths is that it combines project management and cross-functional collaboration in a way that’s easy for both technical and non-technical teams to adopt. Rather than replacing every tool, Asana also integrates with many popular platforms, allowing teams to connect their existing workflows in one place.
Jira + Asana integration
Q: Can we integrate Asana with Claude AI to populate tasks?
A: Yes. Claude can be connected to Asana through the Asana API or integration platforms such as Zapier, Make, or custom workflows. This allows Claude-generated content to create, update, or populate tasks in Asana automatically.
Feel free to continue the discussion below if you have additional questions!
Hi everyone
Thanks for attending today’s session in APAC! I wanted to share a couple of questions from the discussion:
Q1: Can we say deadline-bound is only for product-based work and ongoing is only for service-based projects? Any hybrid use case?
A: Not exactly. Both can be used in either scenario.
“Deadline-bound” vs “ongoing” is more about how the work is structured rather than the type of business. Many teams actually use a hybrid approach—some projects have fixed deadlines, while others run continuously (like operations or customer support workflows).
Q2: If we add someone as CC for a one-time status update, will they get full access to the project?
A: No. CC’ing someone on a task or update does not give them full project access.
They will only see what is shared with them (e.g. that specific task or update), not the entire project—unless they are explicitly added as a project member.
Hope this helps! Feel free to drop more questions below 
Hi everyone, Ren here! Thanks for being part of the Managing Projects in Asana training. It was great connecting with you all! 
I’m sharing one of the questions we discussed during the session:
Q: I wanted to check if it’s possible for me to create a saved tab for my own use. I’d like to have a personalized view where I can easily access the information or items I frequently use without affecting the setup for other users. Is this something I can configure on my end?
A: Yes. You can create a saved tab for your own use. These personal views allow you to customize how you see information without changing the setup or experience for other users.
Option 1: In a project
- Apply the filters or sorting you want.
- Click Save view.
- Select + Save as a new tab and name it.
This creates a custom tab with your preferred view.
Option 2: In My Tasks
- Click the + icon next to your tabs.
- Choose a layout and name the tab.
- Set your filters, sort, or group options.
The view saves automatically as your personal tab.
Have more questions? Feel free to share them below. We’d love to keep the conversation going! 
Hi everyone!
Thanks for attending today’s APAC training!
If you’d like to dive deeper into reporting and tracking progress in Asana, check out our Gaining Insights in Asana on-demand course. You’ll learn how to:
-
Build and customize dashboards
-
Track project progress and key metrics
-
Create charts and reports to visualize your work
-
Share insights with stakeholders
It’s a great next step if you’re looking to get more value from your project data. Happy learning!
Hello. I missed the last 15 minutes of the live training yesterday. Where can I see the recording from yesterday, and where do I sign up for the next training in the series?
Hi @Kaitlin_Dalton! Welcome to the community!
Will send you a DM for Ren’s recording. You can also watch the on-demand version at the top of this thread.
Register for Automating Projects in Asana here: Automating workflows in Asana (live)
1 Like
When you add a task to another project, can you pick what section in that new project something is added to? For example, if you have a project that is your 1:1 meeting with a supervisor, it would be great if I could add a task from an existing project to my 1:1 meeting so i remember to discuss it, but also would be great to be able to put it in a section within my 1:1 meeting, such as “Updates” or “Questions”
1 Like
Is there a specific training on adapting this to track service calls?
Question 1: Sections are used to group tasks and organize. Currently, on some projects, we have the sections as dates (ex: July 1-7). On some projects, they are deliverables (ex: full web redesign). What would you suggest be the norm for the most efficiency?
Question 2: Right now our web designer is listed as his own project. Would portfolios be a better place to have a web designer? He does not like to go into each project and find his assigned tasks. He likes them all in one place.
Hi @Christina_Benton! Welcome to the community!
Yes, you can. When you add a task to another project (also known as multi-homing), you can choose which section within that project you’d like the task to be placed in.
To do this:
- Open the task details pane.
- In the Projects section, click the + icon to add another project.
- Select the project where you’d like the task to live.
- Once the project is added, click the dropdown next to the project name and choose the specific section where you want the task to appear.
I’ve attached a sample screenshot below for reference.
Hi @Melissa_Bernardine, welcome to the community! 
There isn’t a dedicated training specifically for tracking service calls, but the same Asana features used for general task management work well for that workflow.
You can structure it like this:
- Create a project for your service calls (for example: “Service Calls” or “Customer Support”).
- Use tasks for each call and include details like the customer name, issue, and follow‑up steps.
- Add sections such as “New Requests,” “In Progress,” and “Completed” to track status.
- Use custom fields to capture things like call type, priority, or customer tier.
You can also multi-home tasks so the same call task appears in multiple projects (for example, a team meeting agenda) while staying synced across them.
This approach lets you keep one task but organize it across different projects and sections depending on how you want to track the work. You may also find our Creating Basic Workflows on-demand training helpful for setting up this type of workflow.
Hi @Sarah_Armstrong2, welcome to the community!
Portfolios are for monitoring projects, not collecting an individual’s tasks in one place. They give a high‑level view of project status, progress, and owners across multiple projects.
For your web designer, a better approach is:
- Keep tasks assigned to him in the normal projects where the work lives.
- Have him use My Tasks to see everything assigned to him in one place.
- Optionally create a private portfolio to group the projects he works in for easier navigation.
So:
- Projects → where the work happens
- My Tasks → where an individual sees all their assigned work in one place
- Portfolios → project-level visibility, not task aggregation
Hope this helps!
Great question @Sarah_Armstrong2! 
The best approach depends on how your team works, but as a general rule, use sections based on how you naturally organize and track work.
Both approaches can work, but for most teams, using sections for workflow stages tends to be the most efficient because it makes it easier to see where work stands.
A recommended structure:
- Use sections like Intake → In Progress → Review → Done to show how work moves.
- Keep the project focused on one body of work (for example, a website redesign).
- Use due dates on tasks to track timing instead of date-based sections.
- Use custom fields if you need extra categorization (team, type, priority).
Date-based sections (like “July 1–7”) are okay for short-term planning, but stage-based sections usually make projects easier to track and manage over time.
The key is to choose a structure that matches your team’s process and keep it consistent across similar projects.
Hi everyone!
Thanks for attending today’s APAC training!
Here are a couple of questions from today’s session that may be helpful for others:
Q: Can we see the critical path on the Gantt chart?
A: Yes! Asana’s Gantt view allows you to highlight the critical path, making it easy to identify the sequence of tasks that directly impact your project’s completion date.
Q: What happens if I multi-home a task into projects that have different sections or rules?
A: A multi-homed task is still one shared task. Each project can place it in a different section and apply its own project-specific rules. Any updates to the task itself—such as the title, description, assignee, or due date are reflected across all projects where the task is multi-homed.
Thanks again for joining today’s session! Feel free to share any additional questions below.
