Approvals and background tasks

Why BORO asks for approval

BORO works with real project data: prices, contracts, payment applications, the schedule. A wrong change can reach a client or a subcontractor. So reading and looking things up happens at once, but every change stops for your decision. You stay responsible for what is approved, exactly as if you clicked the button on the screen yourself.

The approval card

When BORO wants to change data, the tool row in the conversation shows "Awaiting approval" (Изчаква одобрение) and a card appears:

• The title Requires approval (Изисква одобрение). For a tool of a connected external service, the service's name follows, for example "Requires approval · Gmail".
• The details of the action as BORO will send it: for example the BoQ, the positions and the new prices, the partners an offer request goes to, or the folder a file will be created in.
• The buttons Approve (Одобри) and Decline (Откажи).

1. The tool row (here "Creating task "Order cable trays"") with the state Awaiting approval.
2. The card title Requires approval.
3. The details BORO will send: the board, the task title and the due date.
4. Approve carries out the action.
5. Decline cancels it; BORO is told that you declined.

How to approve or decline a change

1. Read the card. Check that the object (project, BoQ, contract, file) and the values are what you expect. If BORO described the change in words before the card, compare the two.
2. Click Approve to carry it out, or Decline to refuse. "Sending…" (Изпращане…) shows while your decision is sent.
3. BORO continues: after Approve the tool runs and its row shows the result; after Decline BORO knows you refused and usually asks what to change.

• An approval card waits 5 minutes. If you do not decide in time, the change is not made and BORO continues without it. Ask again if you still want it.
• If "Failed to send decision" (Неуспешно изпращане на решението) appears, click the button again.
• Several changes can be bundled into one card, for example 40 new positions or 15 positions priced from history. Approving the card approves all of them.
• An approved change is the same as one you make on screen: colleagues see it at once, the screens refresh, and the usual e-mails and notifications go out.

When BORO asks you a question

When BORO needs a decision, for example which of two templates to use, whether to carry over the notes of a historical analysis, or before taking you to another screen, it shows a card Question from BORO (Въпрос от BORO).

1. Read the question. It may come with up to 6 suggested answers as buttons.
2. Click a suggested answer, or type your own in Free answer… (Свободен отговор…) and click Reply (Отговори) or press Enter.
3. "Answer sent — BORO continues." (Отговорът е изпратен — BORO продължава.) confirms it. Your answer stays visible under the question.

In a chat, a question also waits 5 minutes. In a background task, it waits until you answer.

How to change when approval is needed

Each tool has one of three modes, set in BORO Settings → Tools (Инструменти):

1. Open BORO Settings (gear button in the BORO panel header) → Tools.
2. The tools are grouped in sections: BuildColab (the built-in tools) and one section per connected external service. Expand a section with its arrow to see each tool and its description.
3. Click a mode icon on a section's row to set the rule for the whole section; the rule also applies to tools added to that section later.
4. Click a mode icon on a single tool to override the section. A tool with its own rule shows inherit (наследи); click it to go back to the section rule.
5. To set all tools at once, use the row All tools (Всички инструменти).
6. If you choose No approval for tools that normally ask, a warning asks you to confirm: "The agent will perform these actions without approval. Are you sure?" Click Confirm (Потвърди) or Cancel.

1. Tools in the left menu of BORO Settings.
2. The row All tools sets one mode for everything.
3. The section BuildColab with its mode icons: No approval, With approval, Blocked.
4. A single tool with its own mode.

The rules apply to the whole company. A section for a personal connection (marked Personal) applies only to you. Even with No approval, BORO acts only within the permissions of the person it works for.

Background tasks

A background task is longer, multi-step work that BORO runs on its own, outside the normal back-and-forth of the chat: for example reviewing an incoming offer request and preparing a draft offer, pricing a whole category from history, or matching a large BoQ to a schedule. It does not block the chat, keeps running if you close the panel or the browser, and reports the result when it is done. All changes inside it still go through approval cards and your permissions.

How a background task starts

• From a conversation. When a request needs many steps, BORO starts a background task itself, or you ask for one ("do this in the background"). The task belongs to the conversation: a bar above the message field shows "1 background task running" (фонова задача в процес) or "{n} background tasks running", and the result comes back into the conversation as a short note "Background task completed" (Фонова задача приключи), followed by BORO's summary.
• By hand. Open History → Tasks (Задачи). In the field "Describe a task for BORO — e.g. Review request X and draft an offer" describe the goal and click Start (Стартирай). Such a task is not tied to a conversation.

Statuses of a background task

How to follow, answer and cancel a background task

1. Click the bar above the message field to expand the conversation's tasks, or open History → Tasks for all your tasks ("No background tasks yet." when there are none). Each task shows its goal, status, start date and the credits it used.
2. Click a task to open Background task (Фонова задача): the goal, then every step, tool call and result in chat form, and at the end the Result (Резултат). While it runs, "BORO is working on the task" shows. "No activity on this task yet." means it has not started.
3. When a task waits for you, its card appears in the task view and above the message field, marked "Background task approval" (Одобрение за фонова задача) or "Background task question" (Въпрос от фонова задача). Answering in either place is enough. The bar shows Awaiting approval while a task needs you.
4. To stop a task that is queued, running or waiting, click Cancel (Прекрати). Changes already approved stay done.
5. To continue a finished or failed task, ask in its conversation ("continue the task and also price category 5"). BORO resumes it with everything it already found.

Each step of a background task uses credits like a chat reply. The cost appears as "Background task · −{n} credits" and in the credit movements as BORO background task and BORO task summary. See Credits (BORO, file processing).

1. The field Describe a task for BORO — e.g. … and the Start button.
2. A running task: the status Running, the goal, the start time and the Cancel button.
3. A finished task: the status Completed, the start time and the credits it used. Click a task to open its steps and result.

Approvals for connected AI tools

Approval cards exist only in the BORO panel. Claude, ChatGPT and other AI tools connected through MCP never show a BuildColab approval card: if your company has write access over MCP, their changes happen immediately. Tools set to Blocked are not available to them. See Connecting Claude, ChatGPT and others (MCP).

Common questions

Related

• What BORO can do
• Chatting and attachments
• Settings, models and credits
• Credits (BORO, file processing)