Search Asanaprojects and tasks in your AI knowledge base.

The plan is that 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 designed to be read-only; nothing is changed or commented on in Asana.

Asana

One click · included in the setup

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 is designed

The plan is to 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. Whether your plan and the settings of your Asana administrator allow such a connection is something we check with you beforehand.

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

Set-upThe connection is made with a click through your Asana account and is included in the setup. 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

Which documents may be stored in 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, task by 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

Examples of questions to 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

The connection is made in one click via the account and is included in the setup. Every source comes with its own logins, permissions and folder logic — we check the prerequisites at your company together beforehand.

Until then, and independently of it, you can upload files, whole folders, emails, photos and voice memos. Before we start, we go through real questions with you to see how the answers look.

Preliminary check

What we check in advance

The plan covers 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 itself. Whether the change history of a task is needed, i.e. who changed what and when, is something we discuss. We also clarify how private projects are handled 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?

The plan is that 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. Before we start, we go through how the answers look with your projects on real questions.

What happens to completed tasks and old projects?

The plan is that 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 report it each time?

The selection refers to the teams and projects defined during setup; 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 setup. 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?

The plan is that 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 you do not select. Your sharing settings in Asana remain untouched; we decide together before we start which roles you need.

Request a demo — and clarify how Asana fits in

In thirty minutes by video we show what answers with sources look like, and clarify whether and how Asana can be connected at your company.