Asana Data Processing

Zluri fetches the list of users from Asana. This article explains how to validate the user & license data presented in Zluri for Asana.

 

How Zluri fetches the data:

Zluri calls the following api to fetch user data.

 

 

If there are multiple workspaces Zluri combines the member data fetches from all workspaces to identify the list of users.

 

Status & License Mapping:

 

Zluri identifies a user is active if the user's 'is_active' key is 'True' in any of the one workspaces and marks its User Application Status = 'Active'

 

If any users 'is_active' key is 'false' in all the workspaces he is present, then the 'User Application Status' is marked as 'False'.

 

If any user who was coming from the API response in any of the previous syncs with 'is_active' = true in any of the workspaces, and not coming in the latest sync, Its 'User Application Status' is marked as 'False'.

 

A license is assigned to any user who is a member (not guest) in any of the workspaces he is_active = true and is_guest = false. If a user is present in all workspaces with is_guest = true, then the license is not assigned.

 

 

How to validate the data?

 

You can visit the Asana Admin console at: https://app.asana.com/admin/1188606260300797/members

 

 

The sum of Members + Guests + Pending Invites will be equal to the total count of active users in Zluri which can be fetched by applying the source = 'Asana' and User Application Status = True, Filter.

 

The license count would be sum of members + pending invites.

 

Note: Asana API does not provide the users with pending invite status separately. Hence event users in Pending Invite status is presented as active users. This is a limitation from Asana API and not an error in Zluri data processing.

Can’t find what you are looking for? Let us help you!

Asana Data Processing

Modified on Wed, 15 Mar 2023 at 02:19 AM

Zluri fetches the list of users from Asana. This article explains how to validate the user & license data presented in Zluri for Asana.

 

How Zluri fetches the data:

Zluri calls the following api to fetch user data.

 

 

If there are multiple workspaces Zluri combines the member data fetches from all workspaces to identify the list of users.

 

Status & License Mapping:

 

Zluri identifies a user is active if the user's 'is_active' key is 'True' in any of the one workspaces and marks its User Application Status = 'Active'

 

If any users 'is_active' key is 'false' in all the workspaces he is present, then the 'User Application Status' is marked as 'False'.

 

If any user who was coming from the API response in any of the previous syncs with 'is_active' = true in any of the workspaces, and not coming in the latest sync, Its 'User Application Status' is marked as 'False'.

 

A license is assigned to any user who is a member (not guest) in any of the workspaces he is_active = true and is_guest = false. If a user is present in all workspaces with is_guest = true, then the license is not assigned.

 

 

How to validate the data?

 

You can visit the Asana Admin console at: https://app.asana.com/admin/1188606260300797/members

 

 

The sum of Members + Guests + Pending Invites will be equal to the total count of active users in Zluri which can be fetched by applying the source = 'Asana' and User Application Status = True, Filter.

 

The license count would be sum of members + pending invites.

 

Note: Asana API does not provide the users with pending invite status separately. Hence event users in Pending Invite status is presented as active users. This is a limitation from Asana API and not an error in Zluri data processing.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article