Search Asana projects and tasks in your AI knowledge base.

The Asana projects you share come into the knowledge base together with their tasks, comments and attached files – with everything that was discussed and decided on a job. Access is read-only; nothing is changed or commented on in Asana.

Request a demo Cost calculator

Asana

One click · included in the set-up

Example question

“What was agreed with the joiner in the comments on the task “Window replacement Top 7”?”

1 Answer with source

Connection

How the connection works

You grant access through Asana itself: you sign in with your Asana account, and only the teams and projects you select together with us are read – read-only; no task is created, moved, ticked off or commented on in Asana. Depending on your plan and settings, your Asana administrator approves the connection once.

Once set up, synchronisation runs automatically: new and changed documents from Asana are added without anyone having to upload anything.

Set-upOne click, included in the set-up: you connect via your Asana account, subject to admin consent in your account. We agree beforehand which teams and projects are read – ideally together with the person who manages your Asana. Completed and archived projects are something we look at separately.

Documents

Typical content: Asana

Projects per building project, property or customer, divided into sections such as planning, execution and handover
Tasks with description, due date and responsibility – and below them the comments where the actual coordination happens
Attached files: quotes, plans, site photos, acceptance reports
Custom fields for order number, trade or status that give each task its context
Defect lists and outstanding work after handover, each task ticked off or still open
Completed projects in which you can still read why a decision was made the way it was

Example questions

Questions you might ask your documents

“What was agreed with the joiner in the comments on the task “Window replacement Top 7”?”
1 Answer with source
“According to Asana, which defects from the handover of the Lindengasse residential complex are still open?”
2 Answer with source
“Who approved the choice of heat pump for the Seiersberg project, and when?”
3 Answer with source

Start

Before a connection is set up

You connect it in one click via your account, and it is included in the set-up, subject to admin consent in your account. Together we agree which folders and areas to include.

You can also upload files, whole folders, emails, photos and voice notes at any time. In the demo you see the answers using sample documents from your industry; you check them against your own documents in the first weeks after go-live.

Preliminary check

What we check in advance

junova reads tasks with their description, comments and attached files, plus project, section and fields as attributes. Beforehand, we look at whether attachments are stored in Asana itself or only as a link to another storage location such as Google Drive, Dropbox or OneDrive – in that case, that storage should be connected directly. Whether the change history of a task is needed, i.e. who changed what and when, is something we discuss. We also clarify how to handle private projects and tasks that sit in several projects at once.

FAQ

Frequently asked questions about this connection

Our important arrangements are in the comments. Are they read as well?

Yes. Comments belong to the task and are read with it – including author and date. That way the answer can name the task and the comment it is based on. Nothing is commented on from junova; access remains read-only. In the first weeks after go-live, we go through how the answers look with your projects using real questions.

What happens to completed tasks and old projects?

They are treated like current ones if you select them – that is often exactly where you find why something was decided the way it was. The status is attached to the task as an attribute, so the answer shows whether something is done or still open. If you do not want older content read in day-to-day use, leave out archived projects or connect them separately.

We create a new project for every job. Do we have to tell you each time?

The selection refers to the teams and projects defined during set-up; new and changed tasks in them come in automatically through the sync. Whether new projects in a selected team should be included automatically is something we discuss during set-up. If a project is deleted or the authorisation withdrawn, the knowledge base stays as of the last sync.

The management team’s Asana contains cost calculations. Will everyone see them?

No. Permissions in junova depend on document types and roles, not on teams or projects in Asana. Cost calculations, contracts or HR matters can thus be reserved for a smaller group, even if they are attached to an ordinary task. Projects that should not be read at all are simply not selected. Your sharing settings in Asana remain untouched; before we start, we agree with you which roles you need.

Industries

Typical for these industries

Request a demo – with examples for Asana

In a 30-minute video call, we use sample documents to show what answers with sources look like. After go-live, you connect Asana in one click via your account.