“Should I make this a Project or a Team?” This question, and others like it, comes up often when starting something new in Asana, for both novices and experts alike. And it’s really just the tip of the iceberg.
How can you envision the structural, big-picture view of what you want to accomplish and translate that into an architectural framework in Asana that will enable your workflows, processes and information repository needs durably and flexibly, now and as they scale?
Asana often provides more than one way to accomplish something. This is good: we can do more with Asana as a result. But there’s a downside too: How can we avoid less-desirable solutions, and especially ones that even may lead to dead ends?
This chapter helps you decide how to set up your work in Asana.
Hello @lpb , thanks again for sharing your helpful chapter on creating a good structure within Asana that meets work needs while remaining flexible and scalable. Thanks also for the tip on creating a “Teams Archive”.
As I read your chapter, a quick question came up. How do you create Subsections? All the other “blocks” you mention I understand and know how to create, but I have not figured out how create a Subsection - my apologies for this basic question.
Also is there a way to make a Project “Viewable Only” to a Team? Thank you
Thanks for your nice comments on my book chapter tips, @EmmanuelY.
This is a very understandable question; in fact, I don’t really understand why Asana has not done something about this confusing situation for so long–the feature is completely hidden, yet available. @LEGGO answered, but I’d encourage you both to vote to improve this at:
Did Jerod answer your other question? Is that what you meant by “Viewable Only” or were you referring to limiting access rights to the project entirely?
Hello @LEGGO thank you for your helpful reply. It works! It’s nice to have the option to create Subsections within a Task. I did encounter some strange behavior regarding where my mouse cursor was placed during the Tab+N. When at the bottom of the list of sub-tasks, it would create a Section in the main project window. When the cursor was at the top of my subtasks it created a subsection within the task. I am not sure if this is normal behavior or just something quirky on my side…
Thanks also for the link regarding a Public Project being “Comment Only” – I will read through the link you gave and test it out with our team on Monday.
If you are able to provide a screen recording Monday to demonstrate this behavior it will be easier to determine what is expected or not. I, too, noticed that if all I did was open a task, I have to first click somewhere within the task detail section for Tab+N to work as expected. Otherwise, it does seem to create a new Section instead.
Hello @LEGGO, thank you for your reply. Yes, I think you are right. One has to be careful where the mouse cursor is located to ensure that the new section appears within the task and not in the main project. I will have to do some trial & error to get a better feel for where the sub-section “hot spots” are.
Regarding the project viewing we discussed earlier: I had the chance to read through the article on Comment-only Projects and discovered (unfortunately) that this is a paid feature. I guess I will not be testing this with our team today. However, after reading the article you shared and checking the project permissions table, I believe that this would indeed achieve the “view-only” project I had asked about.