šŸ¦„ Asana Docs | Scribe

    šŸ¦„ Asana Docs

    • |
    • 0 step |
    • 42 seconds
    Asana Release notes Last updated 8.12.24.
    external-screenshot
    āš ļø This feature doesn't exist right now in Asana - In this guide, we have documented here how we do it and highlight how we use it.
    In the meantime, we wait for: āš” Portfolio template [https://scribehow.com/shared/_Set_up_Portfolio_Template_guide__oBNZ8fBkSzCoft89Xi51AA](https://scribehow.com/shared/_Set_up_Portfolio_Template_guide__oBNZ8fBkSzCoft89Xi51AA) āš” Automation rules in portfolios, āš” Asana Docs. And so much more, to #workbetterwithasana.
    external-screenshot

    (1) Create a "šŸ“docs" project.

    Navigate in Asana and "+Create" a project, that you'll named "šŸ“docs". Is important that you have a well structured Asana Hierarchy, so in our case we have a "virtual office" as a team in Asana (I think the name says it all right!?).

    (2) Customise your project.

    If you have a free plan this will only be possible with tags - what I'll show you is possible with a paid plan in Asana.
    Create the following custom fields in your library: [multi-select] docs privacy (1) ā—½shared with the team ā—½private to team members (*) ā—½shared with the clients [single-select] type of content (3) šŸ”½ sop/checklist šŸ”½ guideline šŸ”½ brainstorming šŸ”½ canned email Observations: (1)there may be cases when we have a document shared with both the team and the client (with the use of the client portal. Listen here to how we do it [https://podcasts.apple.com/us/podcast/deliver-wow-client-experiences/id1698626779?i=1000621850473](https://podcasts.apple.com/us/podcast/deliver-wow-client-experiences/id1698626779?i=1000621850473) (2)we have private documents that are only visible to the people we share them with. (3)this is just an example, you should create your own "type of content" you'll need in docs.
    Add the following meta-data fields to your project: ā€¢ Created by ā€¢ Created on ā€¢ Last modified on ā€¢ Projects ā€¢ Collaborators
    You don't want your documents to be "completed" since this is mean to be a collaborative space, so you should create the following rule (run only on tasks - do not select run on tasks/subtasks): šŸŸ” trigger: task is marked as complete šŸŸ¢ action: mark task incomplete
    Bonus tip: We have a section named "šŸ“docs" in some projects so that is easier to create these documents and make sure they are in the docs library - The reason we do this is because we want to simplify the fact of using Asana and Google Docs for so many things.

    (3) Watch how simple it is.

    šŸ“ŗIn this video, I explain the purpose of our docs project, which is to organize and track our own documents. [https://www.loom.com/share/6196ee0239144d6b86e4deeff3135d8e?sid=58dddfd0-c69c-4d97-9c1e-c39d3422888b](https://www.loom.com/share/6196ee0239144d6b86e4deeff3135d8e?sid=58dddfd0-c69c-4d97-9c1e-c39d3422888b)
    We don't use Google Docs for this because we want to maintain order in all the content we create, and it was becoming time-consuming (and the automation was running out of zaps) to make sure our documents are added to the "library" of content.
    We like having them in Asana, because is easier to track the actions that follow the document.

    Vote in the Forum page for Asana to consider our Request!!!

    external-screenshot
    Now, navigate to [https://forum.asana.com/t/asana-docs/488855](https://forum.asana.com/t/asana-docs/488855) and click "Vote", because we all want this.
    Work Better with Asana is a branch of My Virtual Partnr LLC Learn about our services: [https://portal.dubsado.com/public/form/view/61ca1e1daa4e7442528fa0a0](https://portal.dubsado.com/public/form/view/61ca1e1daa4e7442528fa0a0)
    Was this Scribe helpful?
    Save this document for future reference.
    click-target-circles-background
    This Scribe is in tip-top shape!Leave feedback if there are any issues with this Scribe