By integrating with Asana, you can pull in Tasks as Dock tasks and sync updates between the two systems.

To start, within a workspace or template, navigate to a checklist.

Click Add task and then Add task from Asana:

You'll be able to tell that something is connected by clicking on the task directly to view its details.

An admin of Dock and Asana must configure this integration in order for it to be used. To do so, follow the steps below:

Step 1: Navigate to your admin panel by clicking Settings on the left hand nav bar.

Step 2: Under Integrations > Collaboration select Asana

Step 3: Click Configure

Step 4: Accept data permissions

Step 5: Login to Asana

Step 6: Click finish

The following data gets synced between the two systems:

Anything that you don't see in the above table will not get synced.

On the Dock side, this means things like start date, custom statuses, and/or internal statuses will not get pushed back to Asana. On the Asana side, any custom fields or additional fields not shown above will not sync to Dock.

Additionally, please note: commenting only supports plain text.

Please note: Due to Asana's API that Dock used to build the integration, there are some nuances to comments that are worth mentioning.

If you don't want to sync comments between the two platforms, simply turn off comment syncing from the integration page.

Comments made in an task in Asana will flow over to the associated Dock task and will display the name of the person who made that comment. Please note though, Dock only supports plain text comments. You cannot attach files.

Comments that are posted in Dock by an internal team member (someone with both a Dock account and a Asana account) will post to the associated Asana task, but they will come from the system integrator. To help clarify who the team member was that actually posted the comment, you'll see a note in brackets:

In this Asana comment above:

Alex has also turned on "email profile visibility" to allow third-party apps (Dock) to view his email address. See below for instructions on how to turn this.

When the user leaving the comment does not have a Asana account (i.e. your client), then here's what the message will look like:

This message came from a user "[email protected]" as denoted by the appended message to this comment.

In this example, Prateek Banga is the system integrator and that's why his name appears as the person leaving the comment and also why it says "posted on behalf of (Prateek Banga)."

Unfortunately, the quirks of this system are determined by Asana and our technical integration provider. There's nothing we can do about the "post on behalf of" situation. While not aesthetically pleasing, we're optimistic this integration still helps surface valuable information in each place.