Connect Asana to EngLedger
Authorise EngLedger with Asana OAuth, choose projects, pick a time-tracking source per project and understand what task data is imported.
Updated 12 July 2026
EngLedger connects to Asana with OAuth 2.0, requesting read-only access to users, workspaces, projects, tasks, time-tracking entries and custom fields. EngLedger never writes to your Asana.
Authorise Asana
Open Integrations in EngLedger and choose Connect on the Asana card. You're redirected to Asana's consent screen.
Review the requested access and approve. You're returned to the Asana setup wizard with the connection confirmed. Your Asana workspace is detected automatically from the connected account.
Choose projects
The setup wizard lists every non-archived project in the workspace. Unlike Jira, nothing is selected by default. Tick the projects you want measured (a select-all toggle is provided) and continue. You can return to the wizard later via Configure on the Asana card.
Choose a time source per project
Asana doesn't have worklogs the way Jira does, so the second step asks where logged time should come from, per project:
| Time source | Behaviour |
|---|---|
| Native time tracking | Uses Asana's built-in time-tracking entries. Each entry becomes a worklog with its author attributed |
| Custom numeric field | Reads a numeric field you choose; increases in the field are recorded as logged time (no per-person attribution) |
| None | Tasks sync without effort hours |
Native time tracking is the default when the workspace has it enabled and the strongest option. Entries carry who logged the time, which is what attributes effort to a person. The custom-field option suits teams that record hours in a field, but the resulting time has no author. Finish the wizard and the first sync starts; it backfills history, so it takes longer than the routine incremental syncs that follow.
What gets synced
From each selected project, EngLedger imports:
| Entity | Used for |
|---|---|
| Projects | Grouping and filtering reports |
| Tasks and subtasks | The unit that classification, linking and effort attach to |
| Time entries (or custom-field hours) | Logged time: the basis of worklog-derived effort |
| Task completions | Cycle time reporting (open → completed) |
| Estimate fields | Estimation-accuracy reporting, where configured |
Workspace users and task assignees are recorded as provider identities; those with an email matching a person's are linked automatically (see people and identities). Asana has no sprint concept, and status history is limited to completion. Cycle-time reporting from Asana is coarser than from Jira.
Token expiry and reauthorisation
Access tokens refresh automatically in the background. If the grant expires or is revoked, EngLedger stops syncing and marks the integration Needs reauth on the Integrations page rather than retrying silently. Run the Connect flow again to reauthorise. Your project selection and time-source choices are preserved.
Sync cadence
Scheduled sync runs every 30 minutes by default. Asana signals pressure with rate-limit responses; EngLedger backs off and resumes rather than failing the sync.
Disconnecting
Disconnect pauses the integration; synced data is retained and syncing stops. Reconnect at any time with the same flow.
Next steps
- Understand how logged time becomes effort
- Map Asana accounts to people: people and identities
- Everything EngLedger integrates with